Office for Mac no longer recognizes OneDrive files for AutoSave – “Saved on My Mac”

Question

Office for Mac no longer recognizes OneDrive files for AutoSave – “Saved on My Mac”

Carina 10

Since a few days, Word and PowerPoint on my Mac no longer automatically save files to OneDrive.

My files are stored in my company's OneDrive folder and OneDrive itself appears to be working normally. The files sync correctly between my Mac and OneDrive.

However, when I open a Word or PowerPoint file, Office shows “Saved on My Mac” and the AutoSave toggle is OFF.

If I manually switch AutoSave on, Office tells me that I need to save/upload the file to OneDrive. I can do this successfully, but after I close the file and open it again, AutoSave is OFF again and the file once again shows “Saved on My Mac.”

Details

macOS

Microsoft Office/PowerPoint version: 16.111

OneDrive version: 26.134.0713

OneDrive is a business/company account

Files are stored under: ~/Library/CloudStorage/OneDrive-BUSINESSNAME/

Example file: ~/Library/CloudStorage/OneDrive-BUSINESSNAME/FILENAME.pptx

Troubleshooting already tried

OneDrive appears to be syncing normally; there are no general sync problems.

I always open the files directly from the OneDrive folder in Finder.

I also tried opening the same files through PowerPoint → File → Open → OneDrive. AutoSave is still OFF.

I tested with a newly created presentation, not just existing files. After saving it to OneDrive, closing and reopening it also results in AutoSave being OFF.

I signed out of my business Microsoft account in Office and signed in again. The problem persists.

I checked for Office updates, but Office reports that 16.111 is up to date.

This makes it seem like Office is no longer recognizing files in my OneDrive folder as OneDrive/cloud files, even though OneDrive itself is syncing them correctly.

Is there a known issue or a way to reset the Office ↔ OneDrive integration without reinstalling/resetting the entire OneDrive setup?

Josef Horyna 5 Reputation points

2026-08-11T08:58:31.3833333+00:00

Hi,
The same problem has started occurring on my Mac.
I have 1 personal and 2 work profiles signed in. The issue is only on 1 work profile, other work works well and also my personal works well now.

Microsoft’s product reliability is showing itself once again… This is exactly why I switched to a Mac recently, and typically, the only products that repeatedly do not work properly on it are Microsoft’s. Thank you once again for wasting so many hours of my working time. If Microsoft had to compensate me for all the time their products fail to work and I have to spend troubleshooting them, I would deserve a free lifetime licence.
Franck 0 Reputation points

2026-08-12T13:38:10.6933333+00:00

Hi, I've had the same problem since Monday, August 10th.
Steve Hirst 0 Reputation points

2026-08-25T17:19:45.5033333+00:00

Same issue here. No chance to get this self-fixed.

We need to wait for either a fix or rollback.
Steve Hirst 0 Reputation points

2026-09-05T07:29:24.62+00:00

The only way I have multiple times managed to get it work again for some time - is reseting (ResetOneDriveAppStandalone.command) OneDrive as explained here:
https://support.microsoft.com/en-us/onedrive/reset-onedrive

However; after a restart of your Mac you are back to the same problem again.

I have:
MacOS: 26.6.2 (25G83)
OneDrive: Version: 26.158 through MS Site not App Store
MS Office 16.114 through MS Site not App Store

10 answers

Your answer

Josef Horyna 5 Reputation points

2026-08-11T08:58:31.3833333+00:00

Hi,
The same problem has started occurring on my Mac.
I have 1 personal and 2 work profiles signed in. The issue is only on 1 work profile, other work works well and also my personal works well now.

Microsoft’s product reliability is showing itself once again… This is exactly why I switched to a Mac recently, and typically, the only products that repeatedly do not work properly on it are Microsoft’s. Thank you once again for wasting so many hours of my working time. If Microsoft had to compensate me for all the time their products fail to work and I have to spend troubleshooting them, I would deserve a free lifetime licence.
Franck 0 Reputation points

2026-08-12T13:38:10.6933333+00:00

Hi, I've had the same problem since Monday, August 10th.
Steve Hirst 0 Reputation points

2026-08-25T17:19:45.5033333+00:00

Same issue here. No chance to get this self-fixed.

We need to wait for either a fix or rollback.
Steve Hirst 0 Reputation points

2026-09-05T07:29:24.62+00:00

The only way I have multiple times managed to get it work again for some time - is reseting (ResetOneDriveAppStandalone.command) OneDrive as explained here:
https://support.microsoft.com/en-us/onedrive/reset-onedrive

However; after a restart of your Mac you are back to the same problem again.

I have:
MacOS: 26.6.2 (25G83)
OneDrive: Version: 26.158 through MS Site not App Store
MS Office 16.114 through MS Site not App Store

Answer 1

Hi everyone,

I have been experiencing this issue on several Macs for the past few weeks.

The following versions are currently installed:

macOS Tahoe 26.6.2

OneDrive 26.153.0809

Office 16.112.3

I noticed that the user's OneDrive folders (Desktop and Documents) were working correctly. However, SharePoint libraries are affected by the issue described in this discussion.

As a temporary workaround, I removed all SharePoint libraries from OneDrive. I then went to the Documents section of each SharePoint library and selected "Add shortcut to OneDrive."

You can choose between adding the library as a folder or as a shortcut. In my case, I preferred using the shortcut, but both options worked.

Once added, the SharePoint libraries will be available in OneDrive either directly as folders or, if you choose the shortcut option, under the "Shortcuts" folder in OneDrive.

This workaround has been working reliably for me so far.

My current assumption is that this issue may be related to the rollout of Azure regions or changes on the backend, rather than being a problem with the OneDrive client itself. However, this is only a hypothesis and would need to be confirmed.

Answer 2

Steve Hirst 0

I can also confirm the findings reported by **Antonio Valle
**Changing OneDrive from a localized folder name (OneDrive-Persönlich) to the English folder name (OneDrive-Personal) appears to resolve the issue in my environment as well.

What helped temporarily:

Unlink OneDrive
Run ResetOneDriveAppStandalone.command
Re-link OneDrive

Result:

AutoSave worked again
Files synchronized correctly again

However, after a reboot the issue returned:

Office showed "Saved on My Mac"
AutoSave was disabled

What finally appears to make a difference:

I changed the OneDrive application language from German to English. This changed the synchronized root folder name from:

OneDrive-Persönlich

to:

OneDrive-Personal

After re-linking OneDrive with the English configuration:

AutoSave remained enabled
Files were recognized as stored in OneDrive
Synchronization worked correctly
Most importantly, the behavior persisted after reboot

DO 0 Reputation points

2026-09-10T08:02:42.8966667+00:00

For our whole organization ´of around 30 people, the problem also occurred on different Macs (M1 to M5-generation). Since our company name has the letter Ü in its name and you Steve are reporting of a fix, in which you changed the folder name from a name containing an Ö to one without it, maybe those letters or other special characters could be part of the problem. 🤔

I hope I am wrong about this and this issue can be fixed in the next couple of days. OneDrive is painful to use the way it is right now.
Steve Hirst 0 Reputation points

2026-09-11T15:18:18.72+00:00

Hi DO
I did not change the name of folder directly.
I just change my OneDrive from English to German. And then "Persönlich" gets translated by Microsoft to "Personal".
But in your case it seems like you have you Company name in the "OneDrive - Corporateü" name.
Changing OneDrive to English would not fix this, as it will not translate your company name.
But if you are the Admin, you could potentially change your Corporate name somewhere?
Steve Hirst 0 Reputation points

2026-09-11T15:20:57.34+00:00

An update...
An issue that it still have after changing OneDrive to English.
When changing a name of a file locally, you cannot open it anymore on OneDrive.
You have to drag a file out of OneDrive. Rename and drag back to OneDrive, or rename the file online.

For some reason renaming a file does not trigger the upload to online.
DO 0 Reputation points

2026-09-11T15:23:26.0833333+00:00

Hi Steve,

Thanks for your reply.

I could give that a try, but to be honest, I'm concerned it might open a whole new can of worms, such as break all links to shared SharePoint files. 🙈

Therefore I still hope for a fix by an official update 🤷‍♂️

Answer 3

Confirming this issue — additional technical detail that may help narrow down the root cause

I'm experiencing the exact same behavior described in this thread, and wanted to share some additional diagnostic detail that might be useful, since it points to a possible contributing factor beyond a generic sync failure.

Environment:

macOS Tahoe 26.6.2 (25G83)
Mac mini
OneDrive standalone install, version 26.153.0809.0004
Microsoft Word, Version 16.112.3 (26090417) — issue persists after updating from 16.112.3 (26083020)

Symptoms (identical to those already reported):

AutoSave toggle OFF when opening any .docx/.xlsx/.pptx file via double-click from Finder, even though the file is correctly synced (folder shows the cloud icon, manual save uploads correctly, sharing links work fine).
Word reports "Saved on My Mac" instead of the OneDrive/SharePoint location.
Manually enabling AutoSave prompts to "upload" the file, as if it had never been in the cloud.
After that upload completes, closing and reopening the same file resets AutoSave to OFF again.
Opening the same file via Word > File > Open > Online Locations correctly recognizes it as a cloud document and AutoSave works normally — this is consistent with what others have reported.
Reproduced this with brand-new files created and saved directly from Word into the OneDrive folder, not just pre-existing files.

Ruled out (verified via terminal diagnostics):

OneDrive File Provider extension is registered and enabled (pluginkit -m -A -p com.apple.fileprovider-nonui shows it active).
The File Provider domain for the account is alive and healthy (fileproviderctl dump), with the affected file showing ul:uploaded status and no error counters.
The UBF8T346G9.OfficeOneDriveSyncIntegration shared plist (the mechanism OneDrive uses to publish synced folder metadata to Office) is correctly populated with all my synced libraries, including the personal OneDrive root, updated same-day.

Possible contributing factor — Unicode normalization mismatch: My organization's OneDrive folder name contains an accented character ("Gestión"). Comparing the on-disk path (as returned by Finder/the filesystem) against the MountPoint value stored in the OfficeOneDriveSyncIntegration plist, I found:

On-disk path: NFD-normalized (decomposed: "o" + combining acute accent, \xcc\x81)
Plist MountPoint value: NFC-normalized (precomposed "ó", \xc3\xb3)

Both strings are visually identical and normalize to the same value under NFC or NFD, but differ byte-for-byte. If Office performs a literal/byte-exact comparison rather than a Unicode-normalized one when matching a local path against known cloud-synced locations, this would explain why the cloud identity fails to resolve — while the underlying OneDrive sync engine (which doesn't need to do this comparison) keeps working normally.

I want to flag that I have not found confirmation that this is a necessary condition — other reports in this thread and the related Tech Community thread describe the same symptoms without mentioning accented folder names, so this appears to be, at most, a contributing factor in some environments (possibly organization/tenant names with non-ASCII characters), layered on top of whatever broader regression was introduced around the macOS Tahoe 26.6 update.

Happy to provide further diagnostic output (fileproviderctl dump, log traces) if useful for triage.Confirming this issue — additional technical detail that may help narrow down the root cause

I'm experiencing the exact same behavior described in this thread, and wanted to share some additional diagnostic detail that might be useful, since it points to a possible contributing factor beyond a generic sync failure.

Environment:

macOS Tahoe 26.6.2 (25G83)
Mac mini
OneDrive standalone install, version 26.153.0809.0004
Microsoft Word, Version 16.112.3 (26090417) — issue persists after updating from 16.112.3 (26083020)

Symptoms (identical to those already reported):

AutoSave toggle OFF when opening any .docx/.xlsx/.pptx file via double-click from Finder, even though the file is correctly synced (folder shows the cloud icon, manual save uploads correctly, sharing links work fine).
Word reports "Saved on My Mac" instead of the OneDrive/SharePoint location.
Manually enabling AutoSave prompts to "upload" the file, as if it had never been in the cloud.
After that upload completes, closing and reopening the same file resets AutoSave to OFF again.
Opening the same file via Word > File > Open > Online Locations correctly recognizes it as a cloud document and AutoSave works normally — this is consistent with what others have reported.
Reproduced this with brand-new files created and saved directly from Word into the OneDrive folder, not just pre-existing files.

Ruled out (verified via terminal diagnostics):

OneDrive File Provider extension is registered and enabled (pluginkit -m -A -p com.apple.fileprovider-nonui shows it active).
The File Provider domain for the account is alive and healthy (fileproviderctl dump), with the affected file showing ul:uploaded status and no error counters.
The UBF8T346G9.OfficeOneDriveSyncIntegration shared plist (the mechanism OneDrive uses to publish synced folder metadata to Office) is correctly populated with all my synced libraries, including the personal OneDrive root, updated same-day.

Possible contributing factor — Unicode normalization mismatch:
My organization's OneDrive folder name contains an accented character ("Gestión"). Comparing the on-disk path (as returned by Finder/the filesystem) against the MountPoint value stored in the OfficeOneDriveSyncIntegration plist, I found:

On-disk path: NFD-normalized (decomposed: "o" + combining acute accent, \xcc\x81)
Plist MountPoint value: NFC-normalized (precomposed "ó", \xc3\xb3)

Both strings are visually identical and normalize to the same value under NFC or NFD, but differ byte-for-byte. If Office performs a literal/byte-exact comparison rather than a Unicode-normalized one when matching a local path against known cloud-synced locations, this would explain why the cloud identity fails to resolve — while the underlying OneDrive sync engine (which doesn't need to do this comparison) keeps working normally.

I want to flag that I have not found confirmation that this is a necessary condition — other reports in this thread and the related Tech Community thread describe the same symptoms without mentioning accented folder names, so this appears to be, at most, a contributing factor in some environments (possibly organization/tenant names with non-ASCII characters), layered on top of whatever broader regression was introduced around the macOS Tahoe 26.6 update.

Happy to provide further diagnostic output (fileproviderctl dump, log traces) if useful for triage.

Answer 4

Andrea Confalonieri 5

Hi,

I'm facing the same issue. This is my configuration:

macOS 26.6.2

OneDrive 26.150.0804.0011

Office 16.112

I tried all the solutions that I found here and on other Microsoft relate sites. These can solve the problem for a limited time (hours), then it appears again.

In addition to all these troubleshooting, I also did a complete reset of my MacBook, with disk initialization and a clean install of macOS. At first boot I only installed OneDrive and Office. As it did before, it all worked for a couple of hours and then the problem appeared again. So, don't waste your time in trying a macOS reset.

I can't think of a more thorough and deeper attempt at a full system reset, so I think the problem should be solved by Microsoft. I hope that they could fix it soon because this is a HUGE problem in everyday workflow.

A.

Steve Hirst 0 Reputation points

2026-09-04T16:41:47.9433333+00:00

Thanks Andrea

I was thinking to setup my Mac as well. But hearing that this does not solve the issue I will wait for an official fix.

Regards
Andrea Confalonieri 5 Reputation points

2026-09-04T18:24:32.2066667+00:00

My reasoning has been: if these solutions work temporarily, surely formatting and doing a clean reinstall for everything, the issue will be solved. It wasn't like that.

I thought it would be useful to share it so that other users don't waste further time.

It would be interesting to understand whether the problem is actually just OneDrive or whether it also affects the MacOS filesystem. Colleagues using Windows don't have this problem.

Anyway I hope that a fix could be provided soon, because working with this issue is really really struggling

Answer 5

Scott 0

I have the same issue. Was on PTO during summer, so i did not notice until early september. I tried uninstalling both ONe drive and Office 365, resetting completely One drive, disconnect/reconnect, the whoe package. Nothing worked.

Interestingly, a roll back to a previous version from June 2026 did not solve the issue.

0 comments