Word retires legacy compatibility settings: check old documents first

Microsoft announced in Message Center post MC1551147 (published November 13, 2026) that Word will retire some legacy compatibility options for documents in Compatibility Mode. On Windows the rollout begins in early December 2026 and is expected to finish by late December 2026; Word for Mac follows in early 2027. No action is required, but if a document's exact layout matters, open it, check it, and consider exporting a PDF copy before the change reaches your users.

What the Word compatibility settings retirement is

Word shows Compatibility Mode in the title bar when your version of Word is newer than the version that created the document. Microsoft's support page describes the mode this way: it turns off newer Word features so earlier versions can still edit the file, and it keeps the document's layout.

According to MC1551147, Microsoft will retire some legacy compatibility options in Word for documents in Compatibility Mode. The post says the change is being phased in "to simplify document layout handling and create a more consistent experience across platforms." The consequence for readers is that a document that was held in an old layout by one of those options may now be laid out the way current Word lays it out.

The post lists the possible visible effects:

• Text reflow.
• Changed spacing or page count.
• Images or shapes moving to another page.

What the post does not say, and what we could not find on the other Microsoft pages we opened, is which individual compatibility options are being retired. Treat any list of "affected options" from a third-party site as unverified until Microsoft publishes one.

Who it affects and availability

The post says the affected organizations are those with documents created or last saved in Word 2010 or earlier that use the affected legacy compatibility settings. Documents created in current Word and saved as normal .docx files are not what the post describes.

Other points from the post:

• Service: Microsoft 365 apps. Tags: User impact, Retirement.
• No update date is listed on the post as of November 14, 2026.
• The post says no compliance considerations were identified.
• It applies to users in the US and in India alike; the post does not describe any regional exclusion other than the separate GCC, GCC High and DoD timeline.
• It does not mention Word for the web or the mobile apps. As of November 14, 2026 we found no official statement about them, so do not assume either way.

Requirements

You need nothing new to be affected: the change rolls out to Word by itself. To check or protect documents you need:

• The Word desktop app on Windows or Mac, because the Compatibility Mode controls described below are desktop features. Microsoft states you can't turn off Compatibility Mode in Word for the web.
• Permission to save a copy of each document in the location where it lives (a shared library, for example).
• For admins, access to the Microsoft 365 admin center to read the Message Center post. The post's own link is https://admin.microsoft.com/#/MessageCenter/:/messages/MC1551147.

How to check whether you're affected

The post gives no scanning tool, so the check is manual and based on the two conditions it names: the document is in Compatibility Mode, and it was created or last saved in Word 2010 or earlier.

1. Open the document in the Word desktop app.
2. Look at the title bar. Microsoft's support page says Word shows Compatibility Mode there when your version is newer than the one that created the document. If the words are absent, the document is not in Compatibility Mode.
3. To see which compatibility mode you are in, select File > Info. In the Inspect Document section, select Check for Issues > Check Compatibility.
4. Select Select versions to show. A check mark appears next to the current mode.
5. If the mode is Word 2010 or earlier, treat the document as potentially affected.

One documented exception helps you triage: if you open a Word 2013 document in Word 2016, Compatibility Mode doesn't appear, because the two versions are already compatible.

For a shared folder, start with the documents where layout is contractual or printed: forms, templates, contracts, price lists, letterhead and anything with a fixed page count. Open each in the desktop app and note the page count and where images and shapes sit.

How to keep your layout, step by step

The post gives two practical routes. Use PDF when you only need a record of today's appearance; convert the file when people still need to edit it. Both sets of steps below come from Microsoft support pages.

Option 1: Export a PDF copy before the change (Windows)

The post says that to keep a copy of a document's current appearance you can export it to PDF before the change. On Windows, Microsoft's page gives these steps:

1. If the document is already saved, go to File and choose Save a Copy. If it is unsaved, choose File, then Save As or Save a Copy.
2. Click Browse and pick the folder where you want the PDF.
3. In the file type dropdown, choose PDF.
4. Click Save.

Before saving you can select More Options, then Options. The page lists Page range, Publish what (choose Document showing markup to include tracked changes), Create bookmarks using (Headings or Word Bookmarks), ISO 19005-1 compliant (PDF/A) and Encrypt the document with a password.

Microsoft's page also warns: "Simply sharing something as a PDF is not sufficient to guarantee the recipient can't edit the file." A PDF is a record of appearance, not a way to lock content.

Option 1 on Mac

1. Open the File menu and choose Save As, or select the Save icon in the ribbon.
2. In the Save As box, enter a new name so you keep both the editable Word file and the PDF.
3. Open the File Format list and select PDF.
4. Select Export.

Option 2: Convert the document to a current format

Converting moves the document out of Compatibility Mode, so it no longer depends on the legacy options. Be aware that converting is itself a layout event: Word 2016 mode enables newer features, and the file may paginate differently from the old one. Convert a copy first and compare.

Without saving a copy (desktop): select File > Info, then Convert.

As a new copy (Windows): select File > Save As, choose a location, type a file name, and set Save as type to Word Document. Clear the box next to Maintain compatibility with previous versions of Word.

As a new copy (the other Microsoft page, Windows or Mac): on the File tab (on Mac, the File menu), select Save a Copy, choose where to save, then select the file drop-down at the top of the page and choose Word Document (.docx).

Microsoft's note on the trade-off: converting gives you newer features, but people using earlier versions may be unable to work with some parts of the document.

Word for the web

Microsoft says you can't turn off Compatibility Mode in Word for the web. Select Editing > Open in Desktop App at the top of the ribbon, then follow the desktop steps above. A separate Microsoft page for Word for the web says conversion is needed only for files saved in the Word 97-2003 format, and that a .doc file opens in view-only mode in the browser; selecting Convert creates a .docx copy.

Limitations, testing and rollback

• No published option list. The post and the support pages we opened do not name the retiring options, so you cannot predict which documents will move. Test real files.
• No documented opt-out. The post says no action is required for the change to take effect and offers no setting to delay or block it. We did not find an admin control for this in the pages we opened.
• Dates can move. The post shows no update date as of November 14, 2026. If Microsoft changes the dates, plan against the later official update and re-read the post.
• Rollback. Nothing in the pages we opened describes reverting the change after it reaches an account. The safe rollback is the one you create now: keep the original file and a PDF copy.

A practical test routine for an admin or a team lead:

1. Pick 5 to 10 representative old documents, including the ones where page count matters.
2. Record each page count and note where images and shapes sit.
3. Export a PDF of each one now, and store the PDF with the original.
4. After the rollout reaches your Word build (early to late December 2026 on Windows), reopen the originals and compare page count, spacing and image positions against your notes.
5. For documents that changed, decide whether to fix the layout in Word or to circulate the PDF as the reference copy.

Privacy and admin notes

The change affects document layout handling, not data collection. The post lists no compliance considerations and mentions no new data processing, and we found nothing else on the pages we opened about privacy.

For admins:

• Read MC1551147 in the Message Center and pass it to the people who own templates and archives.
• Tell helpdesk the likely symptoms: reflowed text, changed spacing or page count, and images or shapes on a different page.
• If you manage GCC, GCC High or DoD tenants, note the later start: late December 2026, finishing by early January 2027.
• Mac users start later, in early 2027, so a mixed Windows and Mac team may see the same file render differently for a period. The post does not say how Word on the two platforms will compare while the rollout is in progress; verify on both before you rely on a file.
• Archive and compliance teams that keep Word files as the record may prefer to keep a PDF alongside the original, as the post suggests.

What we checked

• Opened Message Center post MC1551147 on mc.merill.net on November 14, 2026. It is a community mirror of the Message Center, so we used it as a pointer, and it shows published November 13, 2026 with no update date. The dates, the affected-document description and the actions in this article come from it.
• Opened Microsoft's "Converting documents to a newer format" page on November 14, 2026 and confirmed the File > Info > Check for Issues > Check Compatibility path, the Convert step and the Save As option Maintain compatibility with previous versions of Word.
• Opened Microsoft's "Turn off compatibility mode" page and cross-checked it against the previous page: both end at a .docx copy, and the page adds that Word for the web cannot turn the mode off.
• Opened the Word for the web compatibility page and the Windows, Mac and Word for the web PDF pages on the same day to confirm the exact export labels.
• Cross-checked the date pairs: the post's Windows window (early to late December 2026) and the GCC window (late December 2026 to early January 2027) are what the table shows.
• Did not find the retirement on Microsoft Learn, the Microsoft 365 roadmap or a Tech Community post in a search run today, and the Learn page on managing Compatibility Mode did not open as an article in our fetch, so we did not use it. The rollout dates therefore rest on the Message Center post alone.
• Not tested in a live tenant or on a document: the rollout had not reached any account on November 14, 2026, so we cannot show a before-and-after layout.

Last tested: 2026-11-14

Sources

• MC1551147: Microsoft Word: Retirement of legacy compatibility settings (mc.merill.net)
• Converting documents to a newer format (Microsoft Support)
• Turn off compatibility mode (Microsoft Support)
• Using compatibility mode in Word for the web (Microsoft Support)
• Save or convert to PDF or XPS in Office desktop apps (Microsoft Support)
• Save or convert to PDF on your Mac (Microsoft Support)
• Export Word document as PDF, Word for the web (Microsoft Support)