A family of Microsoft word processing software products for creating web, email, and print documents.
Office for Mac Reduced Functionality - Reports involving Version 16.114.1
Tracking multiple reports from Oct 22, 2026 involving Office for Mac entering a reduced-functionality/read-only state or failing to recognize a valid Office license. e.g.
- https://learn.microsoft.com/en-us/answers/questions/6046865/
- https://learn.microsoft.com/en-us/answers/questions/6047123/
You may have this problem if your Mac is running macOS 12 Monterey or later and your Office version is 16.114.1 (26102031) or later.
How to see what versions you have:
- macOS: Apple menu → About This Mac
- Office: Word → About Word (or Excel → About Microsoft Excel)
How to submit a Problem Report for this issue:
Submitting a Problem Report sends information directly to Microsoft and is generally a more effective way to help Microsoft assess the scope of this issue, than adding comments, answers, or questions in this forum.
From an Office App do Help → Feedback → Report a Problem
Include in the Report your:
- macOS version
- Office version
- Office edition (Home & Student 2021, Home & Business 2021, etc.)
Copilot suggests this for a concise description to use in your Report (feel free to improvise).
Office for Mac perpetual license no longer recognized after update to the reported version 16.114.1. Office enters a read-only/reduced-functionality state. Unable to create, edit, or save documents. Office displays activation prompts and/or reports that the Office License is not supported.
Possible Workaround - Rollback to an earlier Office build and disable automatic updates.
See the Answer by EmilyS_726 Oct 2026
at https://learn.microsoft.com/en-us/answers/a/13014842
I am also tracking a Reddit post on what appears to be a similar problem:
[External Non-Microsoft Site] https://www.reddit.com/r/Office365/comments/1xd3acb/fix_mac_office_update_falsely_demanding_microsoft/
Reddit is a third-party site, not affiliated with Microsoft. I can't verify the accuracy of the information posted there or endorse the proposed workaround. The root cause described there has not been verified by Microsoft.
Thanks to Reddit user TortelliniTort who first reported the problem and a potential workaround.
Updates
2026-10-23 05:00 UTC - No official response from Microsoft (that I have seen).