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?