Forum Discussion
AutoSave disabled when opening SharePoint-synced files from Finder after macOS Tahoe 26.6 update
Files stored in SharePoint Online and synchronized locally through OneDrive are opened as local documents when launched from Finder. Office applications display "Saved to my Mac" and AutoSave is turned off by default.
However, opening the exact same files through Word/Excel > Open > Sites, or via SharePoint "Open in Desktop App", correctly identifies them as cloud documents. In that scenario, AutoSave is enabled and collaboration/version history features work as expected.
Troubleshooting already performed:
- OneDrive reset and re-linked
- SharePoint library re-synced
- Signed out and back into both Office and OneDrive
- Removed Microsoft credentials from macOS Keychain and re-authenticated
- Recreated local OneDrive sync relationships
- Verified OneDrive File Provider extensions are enabled
- Verified Office applications and OneDrive are fully up to date
- Tested with newly created files and existing files
- Tested "Always Keep on This Device" with no change in behavior
The issue appears to be specific to the Finder-to-Office launch path after upgrading to macOS Tahoe 26.6.
Before upgrading to macOS Tahoe 26.6, opening the same SharePoint-synchronized files directly from Finder correctly preserved cloud document identity and AutoSave was enabled as expected.
I discussed this issue in detail with Apple Support, but they quickly dismissed it, saying that the problem is not on Apple's side and that I should contact Microsoft instead.
2 Replies
You’ve isolated this to the Finder launch path: the same SharePoint files retain cloud identity and AutoSave when opened through Office or SharePoint, but Finder hands them to Office as local files after the Tahoe update. Microsoft’s AutoSave guidance says files opened from Finder may need reopening from within Word, Excel, or PowerPoint, so “Saved to my Mac” does not indicate a SharePoint permission or sync failure. Use Open > Sites or SharePoint’s Open in Desktop App as the workaround; avoid Finder for collaborative editing while it reports a local location. Capture the macOS build, Office build, OneDrive version, affected library, and reproducible test file. Send feedback from the Office app and open a Microsoft 365 admin support case with those details and timestamps. Since reset, relink, Keychain cleanup, and File Provider checks made no difference, further local resets are unlikely to help; Microsoft needs to investigate the Finder-to-Office handoff.
Hi Jamony, thanks a lot. I did send a feedback but didn't open up a case with MS. I'll do that now.
Just wanted to see if anyone else had this same issue.
Using that workaround for now. Thanks.
