OneDrive for macOS documentation issue. DefaultFolder plist example is missing array wrapper
Hi everyone, The Microsoft Learn documentation for configuring the OneDrive sync app on macOS currently contains an incorrect plist example for the DefaultFolderLocation setting. Documentation page: https://learn.microsoft.com/en-us/sharepoint/deploy-and-configure-on-macos#defaultfolderlocation In the “DefaultFolderLocation” section, the current plist example shows the DefaultFolder key as a dictionary: <key>DefaultFolder</key> <dict> <key>Path</key> <string>(DefaultFolderPath)</string> <key>TenantId</key> <string>(TenantID)</string> </dict> This format does not work correctly when deployed as a managed preference/configuration profile. The setting starts working when the DefaultFolder dictionary is wrapped in an array, like this: <key>DefaultFolder</key> <array> <dict> <key>Path</key> <string>(DefaultFolderPath)</string> <key>TenantId</key> <string>(TenantID)</string> </dict> </array> Please update the Microsoft Learn documentation to include the array wrapper in the DefaultFolder plist example. The current Microsoft Learn example is confusing because administrators may deploy the documented plist exactly as shown, but the setting does not appear to work correctly until the array wrapper is added.
OneDrive sync causes workflow inefficiencies and UX issues in Microsoft 365 and File Explorer
I would like to describe some workflow issues caused by the current integration between OneDrive, Windows, File Explorer, and Microsoft 365 apps. I understand that OneDrive is designed to synchronize files across devices, but in some scenarios the current behavior creates unnecessary delays, especially with slow internet connections or large synchronization queues. 1. Exported Microsoft 365 files are not immediately available in the selected OneDrive folder When exporting a Microsoft 365 file, for example exporting a Word, Excel, or PowerPoint document to PDF, the user can select a OneDrive-synced folder as the destination. However, the exported file is not always immediately visible or accessible in that folder through Windows File Explorer. From the user’s perspective, it seems that the file is first saved into a temporary or internal Microsoft 365/OneDrive staging location, then uploaded to OneDrive, and only later appears in the actual synced folder through the normal synchronization process. The issue is not that the file is never stored locally, but that it is not immediately available in the location explicitly selected by the user. This creates practical problems. After exporting a PDF, I may need to quickly locate it in File Explorer to copy it elsewhere, attach it, upload it to another platform, or use it in a web tool to merge it with other PDFs. However, even though I selected a OneDrive folder as the destination, the file may not be available there right away. A related issue is that Microsoft 365 or Windows may open the exported file through a browser or web link instead of opening the local file directly. This can trigger login prompts, open the web version of Office, and interrupt the expected desktop workflow. Expected behavior: When saving or exporting a file to a OneDrive-synced folder, the file should become immediately visible and accessible in the selected folder in File Explorer, while OneDrive continues uploading or syncing it in the background. If the user selected a local OneDrive path, Microsoft 365 should prioritize the local file workflow and avoid redirecting to the browser unless explicitly requested. 2. File duplication inside OneDrive should use both cloud-side copy and local optimization Another issue occurs when duplicating or copying a file that is already stored in OneDrive, especially within the same OneDrive account. Currently, the process may behave like a traditional local copy: the file is downloaded if needed, copied locally, and then uploaded again as a new file. This is inefficient when OneDrive already has the source file in the cloud and the operation is simply a copy within the same account. Ideally, OneDrive should combine two optimizations: Perform a cloud-side copy when possible, so the duplicated file appears quickly in OneDrive online and on other devices. Reuse the local cache when available, so the current device does not unnecessarily download and re-upload the same data. This would make copied files appear faster on other devices as online-only placeholders, ready to be downloaded later if the user opens them or marks them as available offline. The other device should not have to wait for the first computer to download, copy, re-upload, and then synchronize the change. Expected behavior: When copying or duplicating a OneDrive file within the same account, OneDrive should use a cloud-side copy whenever possible, while also reusing local data when available. The copied file should appear quickly across devices as an online-available item, without forcing a redundant download, local copy, upload, and synchronization cycle. 3. OneDrive does not dynamically prioritize files the user needs immediately A third issue appears when OneDrive has a large backlog of pending synchronization changes, especially after using another computer. In this situation, OneDrive seems to follow its own synchronization order, even if the user opens a specific folder or tries to access a specific file urgently. For example, if there are hundreds or thousands of pending changes, and I need one specific document, that file may remain unavailable until OneDrive reaches it in the queue. Even when I navigate directly to the folder or attempt to open the file, OneDrive does not seem to move that item to the top of the sync priority. Expected behavior: OneDrive should dynamically adjust synchronization priority based on user activity. If the user opens a folder, selects a file, or attempts to open a cloud-only item, that file and its immediate dependencies should be prioritized over the general sync queue. Summary of requested improvements I believe these issues could be improved with smarter local and cloud prioritization: Exported or saved files should become immediately visible in the OneDrive folder selected by the user. Microsoft 365 should avoid opening exported files through a browser when the local file workflow is expected. Copying files within the same OneDrive account should use cloud-side copy operations when possible. Local file data should be reused to avoid unnecessary download and upload cycles. Copied files should appear quickly on other devices as online-available placeholders. OneDrive should prioritize files and folders the user is actively trying to access. Is this behavior expected, or are there settings to make OneDrive prioritize local file availability, cloud-side copy operations, and currently accessed files more intelligently?
OneDrive Archival of Unlicensed Users
The change enforcing archival of unlicensed OneDrive users after 93 days was announced in January of last year but seems to be hitting tenants very gradually. https://learn.microsoft.com/en-us/sharepoint/unlicensed-onedrive-accounts?WT.mc_id=365AdminCSH_spo I'm curious what other organizations are doing to tackle this change and how widespread the rollout has been so far. When the change was announced, did your organizations do anything to prepare? For those of you who are already seeing archival in your tenant When did it actually begin? Particularly for very high volumes of unlicensed accounts, how are you handling this? Have you had any luck with Purview content search and export for retrieval of files?Account hacked - no real help anywhere
6h ago my account got hacked by some twerp from Russia. I wasn't quick enough to stop him as he changed my email, alt email, password, removed passkeys, 2FA and whatever else. Even clicking the "this is not me" on the recent sessions didn't do anything. Only one mail was given and that was the one that prompted me that something was wrong (had to check for phising too so lost precious seconds). I got logged out of my account completely and have been doing the same back and forth with microsoft "support" for the past hours. After filling in the Account Escalation form I get a mail stating that all is lost and that i pretty much need to suck it up. 1TB of files (also important ones) just gone? The support chat tells me to keep filling in the form and sending proof that i'm the owner to the email adress given but no reply has come. I need to get in contact with someone who can actually help in order to get my account back. None of the stuff works, the online forms loop me, I can't send codes cuz everything goes to the hackers account. Why can someone from Russia just login on my account and within 3 minutes change everything and there's NOTHING i can do about it? Why isn't anyone truly helping to get my files and account back - cuz everything connected to that account is of course gone too. Posting this from this account since the other one... is unusable for above reasons. I need help, I need all my files back.
Enabling OneDrive Health Sync
Hello, once again being victimized by Microsoft 😒 Have a series of users reporting constant sync errors. We've reached out to Microsoft technical support and they just successively told us it was garbage and not to use it. Anyway, trying to get the Sync Health Dashboard to work, based off this document: https://learn.microsoft.com/en-us/sharepoint/sync-health?tabs=windows It's one of those Microsoft documents that the community CAN'T edit, so of course - it's out of date and incorrect. From what I can figure, based on research from other sources, most of this process is now arbitrary, and you have to create a 'EnableSyncAdminReport' in some policy location in the registry. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OneDrive < already exists, but not referenced by documentation Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\OneDrive < key doesn't exist, but is referenced by documentation. but this sorta 'try it and see' methodology really upsets me. Anyone have any insight to this, and why the documentation team fails to update the documentation, or whether this process will work or not?
VERY SLOW "Processing changes"
Hello, In a completely random manner and without any identifiable common denominator, I frequently have users who synchronize with OneDrive at a snail’s pace. The library in question contains 60,000 items and is sometimes extremely slow to synchronize (it can take 3 days :///). We have well‑managed computers, powerful configurations, and good internet access. We also comply with all Microsoft prerequisites on this matter. (please look vidéo). Best regards, A. W11 - 24H2 up to date Version de OneDrive : Build 26.007.0112.0002 (64 bits) https://uploadnow.io/fr/files/3BKnQ9N
MacOS 14.8.1 OneDrive - Timestamped Sync Root directory?
Hello community, Attempted a plethora of web searches to find someone else who may have seen this. I utilize Shared Libraries with my MacOS OneDrive, and it seems within my ./Library/CloudStorage/ there are two versions of the Sync Root: OneDrive-SharedLibraries-*Company*/Directories & OneDrive-SharedLibraries-*Company* (Timestamp)/Directories This Timestamped Sync Root has over 140GBytes of 'reported' storage space consumption. Some of the folders already exist in OneDrive-ShareLibraries-*Company*/Directories, but others do not. Was curious if anyone else has seen this before and knows if the related storage can be 'freed'?
