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.
[Community tool] Find the GPO, registry value and Intune setting for any Office ribbon button
Hi everyone, as a technical service owner for Microsoft 365 Apps, one question comes up for me again and again: which policy actually controls this button or option? The information is all there – in the Office ADMX/ADML templates, the Office Fluent UI control ID lists, the Intune Settings Catalog and many Learn articles. But I never found it in one place, so every answer meant connecting several sources by hand. Especially when onboarding new colleagues, this costs a lot of time. So I built a free community tool for it: Office Admin Explorer https://tools.pascal-donath.de/office-admin-explorer/ How it works It's a clickable mock of Word, Excel, PowerPoint and Outlook (ribbon, File menu, Options, Trust Center). Click any element and you get: idMso and Policy ID (for customUI and the "Disable commands" policy) the ADMX policy with its exact path in Group Policy Management the registry value it writes, with ready-to-copy PowerShell or .reg the matching Intune Settings Catalog entry Cloud Policy notes, step-by-step guides and Microsoft Learn links The search covers all Office ADMX policies (2,400+) and command IDs (8,000+), including elements that aren't part of the mock. Also included Ribbon builder – hide or disable buttons, groups or tabs and export the result as customUI XML, a macro-free add-in (.dotx / .xlam / .ppam) or the "Disable commands" policy for Group Policy and Intune Deployment view – configuration.xml generator for the Office Deployment Tool User Support view – typical user problems: symptom → cause → fix Policy names and registry values are checked against Microsoft's ADMX/ADML files, and the Intune mapping against the Graph settings catalog. It runs in the browser without sign-in and is available in English and German. Please test any configuration on a lab device or pilot group first. I'd like your input How do you handle this today – ADMX search, Group Policy Search, the Intune catalog, your own documentation? Which Office settings do you get asked about most often? I'd like to add the most requested ones next. If you find a wrong or outdated entry, every entry has a "Report it on GitHub" link – corrections are very welcome. Thanks! Pascal --- *Transparency note: The tool was developed with the help of AI. The content is based on my own admin experience, and policy names, registry values and Intune mappings are validated automatically against Microsoft's official sources (ADMX/ADML templates, Fluent UI control lists, Microsoft Graph settings catalog). This is a community project and not affiliated with Microsoft.*
OneDrive files opened from Finder not recognized as cloud files on Mac
Office for Mac: OneDrive files opened from Finder no longer recognized as cloud files – AutoSave disabled Hi everyone, I am experiencing a persistent issue with Microsoft 365 for Mac and OneDrive that started suddenly around August 10, 2026. The same setup and workflow had worked without problems for more than two years before that. Problem My Office files are stored in OneDrive and synchronized to my Mac via the standard macOS File Provider. When I open an Excel or Word file by double-clicking it in Finder, the Office application opens the file, but it apparently does not recognize it correctly as a OneDrive/cloud file. For example: AutoSave is disabled real-time co-authoring does not work as expected when I try to enable AutoSave manually, Office behaves as if the file were local and asks me to upload/save it to OneDrive – even though the file is already stored and synchronized in OneDrive However, if I open the exact same file from within Excel or Word via the OneDrive/Online Locations option, everything works correctly: AutoSave is enabled immediately co-authoring works changes made by another user appear in real time This behavior is reproducible with multiple files and affects both Excel and Word, so it does not appear to be an issue with one particular workbook or application. Environment MacBook Air M2 current macOS version current Microsoft 365 version current OneDrive version OneDrive Personal files synchronized through the standard macOS File Provider I have also tested opening files directly from: ~/Library/CloudStorage/OneDrive/... The result is the same: when opened from Finder, Office does not appear to recognize the file correctly as a cloud file and AutoSave remains disabled. Troubleshooting already performed I have already: completely reset and reconfigured OneDrive allowed OneDrive to fully resynchronize verified the files and folders in OneDrive on the web confirmed that OneDrive reports everything as synchronized restarted Finder and macOS removed and recreated Finder shortcuts/favorites tested without Finder favorites or aliases tested directly from ~/Library/CloudStorage/OneDrive updated macOS updated all Microsoft 365 applications updated OneDrive None of these steps changed the behavior. Key diagnostic result The following comparison is consistently reproducible: Finder → OneDrive file → double-click → Excel/Word → AutoSave OFF → file appears not to be recognized as an active OneDrive cloud document → co-authoring does not work correctly Excel/Word → Open → OneDrive/Online Locations → same file → AutoSave ON immediately → cloud functionality works → co-authoring works correctly This suggests that OneDrive synchronization itself is functioning correctly. The issue seems specifically related to the handoff between macOS Finder / Apple File Provider / OneDrive and Microsoft 365 for Mac when a OneDrive file is opened from Finder. Important detail This is not a workflow that has never worked on macOS. For more than two years, we routinely opened our synchronized OneDrive Word and Excel files directly from Finder. Office recognized them as cloud files, AutoSave was available, and collaborative editing worked normally. The behavior changed suddenly around August 10, 2026, without us intentionally changing the OneDrive folder structure or our workflow. Question Has anyone else encountered this recently? In particular: Is this a known regression in Microsoft 365 for Mac, OneDrive for Mac, or their integration with Apple's File Provider? Why would Office recognize a file as a OneDrive cloud document when opened through the application's Online Locations, but not when the exact same synchronized file is opened from Finder? Is there a way to reset or repair the Microsoft 365/OneDrive cloud-file recognition or File Provider integration without resetting the entire OneDrive again? Are there any relevant logs, caches or diagnostics that could show why Office considers a Finder-opened OneDrive file to be local? Opening every document through the Office application's Online Locations is a possible workaround, but it is not a practical long-term solution when working with a larger shared folder structure in Finder. I have already contacted both Apple Support and Microsoft Support. Apple referred me to Microsoft, and Microsoft Support subsequently recommended that I raise the issue here in the Tech Community. Any insight from Microsoft staff, MVPs or others familiar with Microsoft 365 for Mac, OneDrive and the macOS File Provider would be greatly appreciated.
Business Central - Blocking External Operations Until Previous Operation Quality
Hello Team, We are evaluating the Quality Management process in Microsoft Dynamics 365 Business Central for a Release Production scenario. Our requirement is to control the production workflow in such a way that an External Operation (Subcontracting Operation) cannot be processed or posted unless the previous operation's quality inspection has been completed and approved. Business Requirement Production consists of multiple routing operations. Quality inspection is required after specific operations. If an inspection result is pending, failed, or not approved, the next operation (especially an external/subcontracting operation) should not be allowed to proceed. The system should enforce this control automatically to prevent production from moving to the next stage without quality clearance. Questions Does standard Business Central provide any functionality to block the posting or execution of a subsequent routing operation until the previous operation's quality inspection is completed? If using a Quality Management add-on, how is this scenario typically handled? Is there a standard quality status (Released, Accepted, Rejected, Hold, etc.) that can be linked with routing operation progression? Can the system prevent an External Operation from being posted when the previous operation's inspection order is still open? Has anyone implemented similar process controls in Business Central, and what approach was used (standard functionality, workflow, or customization)? Any guidance, best practices, or recommendations would be greatly appreciated.
An Authenticator initial login round-robin
Hello all. In migrating from an older Android to a very new Android, I of course had to perform initial login on most app. In trying an initial login to Authenticator (an essential app for many other apps I use on the phone and on the desktop) I've been facing a maddening closed loop of actions: To perform initial login, I must use Authenticator to confirm access - even though I'm still trying to set it up on my Office 365 account login. Selecting "other ways" leads to a phone code, which when entered leads only to a "change your password" screen and I'm back where I started. (I've uninstalled/reinstalled the phone app; I've reset the p/w about a dozen times.) Insights or suggestions most gratefully received! David
Booking Error Message
Microsoft Bookings public booking page displays “Something went wrong. We couldn't book that appointment,” but the appointment is actually created in the Bookings/Outlook calendar. The issue occurs even when using different browsers and Incognito mode. I checked availability and other things, everything looks fine. How to fix this?
