AutoSave disabled when opening SharePoint-synced files from Finder after macOS Tahoe 26.6 update

Batuhan Köklüçınar 35 Reputation points
2026-07-31T09:33:48.7366667+00:00

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'm just out of ideas now how to fix this since Apple won't let me return to previous MacOS version in an easy way. That's just too much work. :(

Microsoft 365 and Office | OneDrive | For business | Windows

2 answers

Sort by: Most helpful
  1. Eddy 30 Reputation points
    2026-10-01T04:19:57.6233333+00:00

    Sharing what fixed this for us (so far), in case it helps others.

    We had the exact same symptom on several Macs in our organization: Office files in synced SharePoint libraries, opened from Finder, showed "Saved to my Mac" with AutoSave off, while opening them via File > Open > Sites worked fine.

    We were already using the standalone OneDrive (not the App Store version). What resolved it was a complete removal and clean reinstall of OneDrive:

    1. Quit OneDrive.
    2. Ran the reset script from the app bundle (OneDrive.app > Show Package Contents > Contents > Resources > Reset...Standalone...command).
    3. Moved OneDrive.app to the Trash.
    4. Removed all remaining OneDrive-specific items in ~/Library (Application Support, Caches, Containers, Group Containers, FileProvider), the OneDrive LaunchAgents/LaunchDaemons and receipts, plus the OneDrive entries in Keychain. Careful: do NOT delete the UBF8T346G9.Office or UBF8T346G9.ms group containers, they are shared with Office.
    5. Restarted the Mac.
    6. Reinstalled the standalone OneDrive from Microsoft's download page (not the App Store) and re-synced the SharePoint libraries from the browser.

    After this, files opened from Finder are recognized as cloud documents again and AutoSave is on.

    Current setup: OneDrive standalone 26.168.0830.0006, macOS 27.0.1, Apple Silicon.

    Make sure everything is uploaded before unlinking or removing OneDrive, as files that haven't synced could be lost.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  2. Helen Luu 3,300 Reputation points Independent Advisor
    2026-07-31T15:21:55.0933333+00:00

    Hello @Batuhan Köklüçınar,

    Based on the information you provided, I understand that you are unable to use the AutoSave feature when opening locally synced files, and that the issue started after upgrading to macOS Tahoe 26.6.

    As this is a relatively new macOS release, we currently do not have any known records or widespread reports of this specific issue. However, I will continue to monitor for similar cases and keep you informed if we identify a broader trend. At this stage, there is a possibility that the issue is related to a compatibility conflict between the OneDrive sync client and the new macOS version.

    In the meantime, I strongly encourage you to submit your feedback through the Microsoft Feedback Portal. The Microsoft development teams actively review customer feedback, and many enhancements have been implemented based on community input. The engineering team will analyze reported cases and gather feedback from affected users to evaluate whether a future update is required to improve compatibility with the latest Apple release.

    If you decide to submit feedback, please feel free to share the link with us. I would be more than happy to support it, and doing so may also help increase visibility so that other users experiencing the same situation can find and endorse it. The more engagement a request receives, the higher the likelihood that it will be carefully reviewed. 

    Thank you again for clearly documenting your concerns. I sincerely hope this feedback will be reviewed and upgraded by Microsoft in the near future.  

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.