Cloud/Microsoft 365 Best Practices

Word 97-2003 Files Are Being Retired. Is Your Business Ready?

2026 Intune security baselines increasingly block legacy .doc and .xls files. Here is why the 97-2003 formats are ending, and how to modernize without breaking work.

By COMNEXIA
#Word 97-2003#deprecated file formats#Intune security baseline#Protected View#Microsoft 365 hardening#managed IT Atlanta#Roswell IT support

If you have opened an old Word document lately and seen a warning that the file is blocked, or found that you could view a document but not edit it, you are running into one of the clearest signals in modern IT: the Word and Excel 97-2003 file formats are being retired. Microsoft has spent years nudging these legacy formats toward the exit, and in 2026 the security baselines that hardened businesses rely on are turning that nudge into a firm boundary.

At COMNEXIA, we manage and harden Microsoft 365 environments across metro Atlanta, and we see this play out in real support cases. The interesting part is not that Microsoft is phasing out old formats. It is how many major, well-known software platforms are still producing those old formats in 2026, forcing everyday users into friction they should not have to deal with.

What Are the 97-2003 File Formats?

When most people think of a Word or Excel file, they picture the modern extensions: .docx, .xlsx, and .pptx. Those are OpenXML formats, introduced with Office 2007. They are open, structured, and far safer than what came before them.

The 97-2003 formats are the older binary formats: .doc for Word, .xls for Excel, and .ppt for PowerPoint. These were the default in Office 2003 and earlier. They are proprietary binary containers, and that design is exactly why they have become a security liability.

Why the Old Formats Are a Security Risk

The 97-2003 binary formats carry two big problems that modern formats largely solved.

First, they are a favorite vehicle for macros and embedded exploits. Because the binary structure is opaque and hard to inspect, attackers have used .doc and .xls files for decades to smuggle malicious macros and trigger vulnerabilities. Security tooling has a much easier time reasoning about the modern OpenXML formats.

Second, the legacy formats do not play well with modern data protection. Microsoft Purview data loss prevention, for example, does not fully support the old 97-2003 formats, which means sensitive information in a legacy .doc or .xls can slip past protections that would catch it in a .docx or .xlsx. Put simply, every .doc and .xls in your environment is a small, unnecessary piece of attack surface.

The 2026 Signal: Intune Baselines and Office Hardening

Here is the hook that matters for business owners. Microsoft is not just recommending you move on. Through modern Office security defaults and the baselines that tools like Microsoft Intune push to managed devices, the 97-2003 formats are increasingly blocked or restricted by default.

The two mechanisms most businesses run into are:

  • File Block settings. Modern Office and hardened baselines can block opening or saving legacy 97-2003 files outright, or force them into a read-only state.
  • Protected View. Legacy files that do open are frequently routed into Protected View, a sandboxed, read-only mode. That is why you can look at a document but not edit it.

Layer in Microsoft Defender Attack Surface Reduction rules, which further restrict risky Office behaviors, and the message from the industry is unmistakable. The 97-2003 formats are end-of-road. A well-configured 2026 baseline treats them as something to contain, not something to work with. For a managed business, this is a feature, not a bug. The baseline is protecting you, and the trick is keeping that protection in place while making sure legitimate work does not grind to a halt.

The Real-World Gap: Vendors Still Emitting Legacy Formats

This is where 2026 gets frustrating for end users. Microsoft has effectively drawn the line, but a surprising number of large, widely used enterprise platforms are only now catching up, and many are still generating documents in the old 97-2003 format.

Across recent COMNEXIA support cases, we have observed several major platforms still producing legacy .doc and .xls files, including widely used systems such as ADP, RealPage, and Empower. These are not small or obscure tools. They are mainstream platforms that businesses depend on every day for payroll, property management, and HR.

The result is a mismatch. A user downloads a document from one of these platforms, tries to edit it, and the hardened Office environment does exactly what it is supposed to do: it blocks or sandboxes the legacy file. The user is stuck through no fault of their own, caught between a vendor that has not modernized and a security baseline that has. This is precisely the kind of edge case a good managed IT partner is built to handle.

What To Do About Legacy Files

The good news is that modernizing a legacy file is quick, and it makes the security warning go away for good.

Convert a single file in seconds

If you need to edit a blocked .doc or .xls right now, the fastest fix is the browser:

  1. Upload the file to OneDrive or SharePoint.
  2. Open it in the Word or Excel web app (Word Online or Excel Online).
  3. Use Save As and choose the modern format: .docx for Word, .xlsx for Excel.
  4. Download the modern copy and edit it normally.

If you have the desktop app and can open the file, you can also use File, then Info, then Convert to upgrade it in place. For a folder full of legacy documents, the conversion can be scripted in batch so your team is not touching files one at a time, a common cleanup project we run for clients.

Push your vendors, keep the baseline

If a platform your business relies on is still handing you .doc or .xls files, say something. The long-term fix is on the vendor’s side, so ask their support team when modern .docx and .xlsx output will be available. The more customers raise it, the faster these platforms catch up.

And resist the temptation to simply turn off File Block or disable Protected View to make the pain go away. Weakening the baseline reopens the exact attack surface the hardening was designed to close. The right approach is a managed baseline that stays strong, paired with clean, modern files.

How COMNEXIA Handles This for Clients

Managing legacy file formats well takes both sides of the coin: strong security and smooth day-to-day work. At COMNEXIA, we harden Microsoft 365 and endpoint environments with modern baselines, we spot the vendor and format edge cases before they turn into help desk tickets, and we have practical workarounds ready when a user needs to get unstuck fast. When a legacy .doc from a payroll or property platform lands on someone’s desk, our team converts it, gets the user moving, and keeps the security baseline exactly where it should be. With 35 years serving businesses across Atlanta, Roswell, and the Southeast, we have modernized hundreds of environments without breaking the workflows people rely on.

Ready to Modernize Safely?

If your team is running into blocked files, editing warnings, or vendors still shipping 97-2003 formats, let us take it off your plate. COMNEXIA can harden your Microsoft 365 environment, clean up legacy files, and keep your business secure without the friction. Call us at (877) 600-6550, email info@comnexia.com, or reach out through our website. COMNEXIA is based in Roswell, Georgia, and proudly supports businesses across metro Atlanta and the Southeast.

Need Expert Technology Guidance?

Don't navigate complex technology decisions alone. Our consulting team provides the strategic guidance you need to make informed technology investments.