macOS 27 Golden Gate shipped on September 14, 2026, and the first Microsoft breakage is already in: OneDrive losing its sync folder after the upgrade. Behind that bug sit three deadlines that matter more to a small office than any single crash: Intel Macs cannot install Golden Gate at all, Microsoft's support window moves up a version, and on October 1 Exchange Online starts blocking the protocol legacy Outlook and Apple Mail use.
Symptom, cause, and the exact steps for each, with a source and a date on every claim. Current versions as of this update: macOS 27.0, Microsoft 365 for Mac 16.112.
Reported on Microsoft Q&A from September 19, 2026, five days after Golden Gate shipped. After the upgrade OneDrive stops syncing and shows a dialog saying it couldn't find your "OneDrive (2026-09-13 05:36:04 +0000)" folder, with Try Again and Stop Sync buttons that do nothing useful. The menu bar icon offers only Close OneDrive and Stop Sync, and the folder it names, timestamp and all, does not exist. Your real OneDrive folder is still there, which is what makes the dialog so confusing.
The upgrade left OneDrive's File Provider registration pointing at a sync location that no longer exists. On current macOS, OneDrive syncs through Apple's File Provider framework and keeps its actual folder under ~/Library/CloudStorage/, with the OneDrive folder you see in Finder acting as a pointer to it.
Every report in the thread involves the Mac App Store build of OneDrive (bundle ID com.microsoft.OneDrive-mac); one user hit it on an M1 iMac but not on an M3 MacBook Air running the same App Store build. Two users resolved it by replacing the App Store build with Microsoft's standalone download. Reinstalling the App Store build did not help, and OneDrive's own reset script returned "Operation not permitted" errors on the container folders and did not clear it either.
~/Library/CloudStorage, and copy anything in the OneDrive folders that changed recently to a folder outside OneDrive, ideally an external drive. Microsoft's reset guidance warns that a reset can discard local changes that never uploaded./usr/libexec/PlistBuddy -c 'Print CFBundleIdentifier' /Applications/OneDrive.app/Contents/Info.plist. A result of com.microsoft.OneDrive-mac is the App Store build; com.microsoft.OneDrive is the standalone build.ResetOneDriveAppStandalone.command (the App Store build ships ResetOneDriveApp.command). Open OneDrive and sign in again.The reports so far are personal accounts, but the File Provider mechanism is the same for work accounts, so treat a work Mac that shows this dialog the same way. Copy first, swap builds second, delete nothing until sync is green and verified online.
Your files are still on the Mac, Maya. That dialog is macOS 27 dropping OneDrive’s File Provider registration during the upgrade; OneDrive then created a fresh folder and lost track of the old one.
Quick check: in Finder, under your home folder, do you see two OneDrive folders, one with a date in the name?
That’s the one to protect. I can fix this through Vision in about 6 minutes: copy the dated folder somewhere safe, replace the App Store build with Microsoft’s standalone OneDrive, and point it at your existing folder so nothing re-downloads.
Click the Anthony AI icon in your menu bar and paste the code here.

✅ Remote session on Mayas-MacBook-Air completed successfully. Duration: 5m 52s (0m 0s paused)
📋 Session Report
| Action | Result |
| Copied “OneDrive (2026-09-13 …)” to Desktop | 4.8 GB, verified |
| Removed App Store OneDrive | Uninstalled |
| Installed Microsoft’s standalone OneDrive | Set to your existing folder, no re-download |
| Verified sync | Client files present, syncing |
⚠️ Additional finding: Automatic macOS installs were on, which is how 27 landed overnight. I turned off “Install macOS updates” under Automatic Updates so the next major version waits for you; security updates still install on their own.
Open your client folder now. Everything should be there and syncing.
Free to start: 25 chats and 10 Vision minutes, no card. Works inside Microsoft Teams on Windows and Mac.
Golden Gate dropped every Intel Mac; Apple has said Tahoe 26 is the final macOS for them. Microsoft supports Microsoft 365 for Mac, Office 2024, and Office 2021 on the three most recent major macOS versions and removes the oldest when a new one goes generally available. Golden Gate's release therefore moves the window to 27, 26, and 15, and pushes Sonoma 14 out.
Last year the cut landed in the same month Tahoe shipped: the September 2025 build, 16.101, was the last to support Ventura. As of September 23, 2026, Microsoft's lifecycle page still carries the 2025 wording, so the exact last-Sonoma build is not published yet.
Intune is moving in step: the Company Portal and the MDM agent support macOS 15 and later shortly after the macOS 27 release, so a Sonoma Mac already enrolled stays enrolled, but a new one cannot enroll.
| macOS version | Intel Macs | Microsoft 365 and Teams status, September 23, 2026 |
|---|---|---|
| Golden Gate 27 (September 14, 2026) | Cannot install | Supported, current release. Last macOS with full Rosetta 2; Apple has said Intel-only software stops launching in macOS 28. Microsoft 365 is Universal, so it is unaffected; Intel-only Office 2016 and 2019 installs are not. |
| Tahoe 26 | Final version for Intel | Supported. Under the three-version policy it stays in the window until the fall 2028 release. |
| Sequoia 15 | Yes | Supported. Drops when macOS 28 ships, expected fall 2027. |
| Sonoma 14 | Yes | Being dropped now. Expect the last Sonoma build in a fall 2026 Office update. Apps keep running but stop receiving updates, including security updates. New Intune enrollments blocked. |
| Ventura 13 and older | Yes | Out of support since build 16.101 (September 2025). Current Teams builds fail to launch. Below macOS 12, or with an Office build older than 16.83, the apps have been in reduced functionality mode since July 13, 2026: they open and print files but will not edit or save. |
Microsoft starts blocking Exchange Web Services (EWS) requests to Exchange Online on October 1, 2026, in a phased, admin-controllable rollout that ends with a complete shutdown in 2027. Two Mac mail clients depend on EWS. Legacy Outlook for Mac connects through it and stops working with Exchange Online mailboxes beginning October 2026.
Apple Mail on the Mac also uses EWS for Exchange accounts; Apple is working with Microsoft to move Mail, Calendar, Contacts, Notes, and Reminders to Microsoft Graph in a future update to macOS 27, which means the fix, when it ships, lands on Golden Gate and not on the Tahoe Macs that cannot upgrade. Universities that manage thousands of Macs are already warning staff that Apple's update may not arrive before October 1.
Nine days in, there is no Microsoft-confirmed Golden Gate incident for the Office apps, and the reports so far follow the pattern of every macOS launch: apps that were out of date before the upgrade, or helper components the upgrade relocated. Microsoft ships macOS compatibility fixes through app updates and does not support its apps on beta or preview builds, so the current builds matter more than anything else on this list.
~/Library/Preferences, and move the matching com.microsoft.* files to your Desktop. Relaunch; macOS rebuilds fresh ones.~/Library/Group Containers remove the folders that begin with UBF8T346G9, empty the Trash, restart, and reinstall from office.com. Warning: this signs you out of Office on this Mac and clears local caches and settings.Teams is supported on 27, 26, and 15. If the location permission loop (Microsoft incident TM1315837) comes back after the upgrade, the toggle-off-and-on workaround in our Tahoe guide still applies.
Yes. The current Microsoft 365 for Mac apps support Golden Gate under Microsoft's three-version policy, which now covers 27, 26, and 15. Update the apps before you upgrade the OS. The one confirmed breakage so far is the App Store build of OneDrive losing its sync folder; the standalone build fixes it.
The upgrade left OneDrive's File Provider registration pointing at a timestamped sync location that no longer exists. Back up any unsynced files, remove the App Store build, install the standalone OneDrive from Microsoft, and choose your existing folder during setup.
No. Golden Gate runs on Apple silicon only, and Tahoe 26 is the last release for Intel Macs. Under Microsoft's policy an Intel Mac on Tahoe keeps receiving Microsoft 365 updates until macOS 29 ships, expected in fall 2028.
It can. Microsoft begins blocking EWS on October 1 in a phased rollout, and Apple Mail on the Mac still uses EWS for Exchange accounts. Apple's Graph-based update is planned for macOS 27. Until it ships, use Outlook for Mac or Outlook on the web, or have your admin keep EWS enabled temporarily.
No. It connects through EWS and stops working with Exchange Online mailboxes beginning October 2026. Uncheck Legacy Outlook in the Outlook menu to move to the current client.
Three honest exclusions. If the same account fails on every device, it is a Microsoft 365 service or account issue, not the Mac, so check whether Microsoft 365 is down before touching the machine. If mail stops on or after October 1 and the client is legacy Outlook or Apple Mail, the cause is the EWS retirement above, and the fix is a client change, not a reinstall. And failing hardware, a dying SSD or bad RAM, can masquerade as app crashes; frequent crashes across non-Microsoft apps too point there.
Everything on this page is work Anthony AI does through Vision remote support, inside the Microsoft Teams chat your company already uses. You paste a one-time code from your own Mac, you watch every click live, every action is logged back to the chat, and a session caps at 20 minutes. Full macOS and Windows parity.
Then it’s Word’s own files after the upgrade, not macOS 27 itself, which is the usual pattern on a new release. I can fix this through Vision in about 4 minutes: update Office through Microsoft AutoUpdate, check Relocated Items for helper files the upgrade moved, and reset Word’s preferences if it still quits.
Click the Anthony AI icon in your menu bar and paste the code here.

✅ Remote session on Mayas-MacBook-Air completed successfully. Duration: 3m 41s (0m 0s paused)
📋 Session Report
| Action | Result |
| Updated Office 16.109 to 16.112 | All apps current |
| Checked Relocated Items | Nothing from Microsoft |
| Reset Word preferences | com.microsoft.Word.plist rebuilt |
| Verified | Word opens, recent documents intact |
Open Word now. It should launch straight to your recent files.
Free to start: 25 chats and 10 Vision minutes, no card. Works inside Microsoft Teams on Windows and Mac.
More fixes in the fix library · On Windows? See every known issue in the September 2026 updates · Still on Tahoe? See every known macOS Tahoe Microsoft app issue · Not sure if Microsoft 365 is down or it's just you · See what IT support costs in 2026 · How Vision remote support works