OneDrive Admin Checklist: web upload fails in one browser for mobile workers

Mobile workers often access OneDrive through a web browser when they are away from their corporate device. When uploading a file fails only in one specific browser, the cause is rarely a tenant-wide setting. This article walks through the admin checklist to identify whether the issue is browser-specific, a network restriction, or a local configuration problem. You will learn exactly which settings to check in the Microsoft 365 admin center, how to test browser compatibility, and what to verify on the user’s device.

Why OneDrive Web Upload Fails in Only One Browser

When a mobile worker reports that OneDrive file uploads fail in one browser but work in another, the root cause is almost always local to that browser or device. Tenant-wide settings in the Microsoft 365 admin center apply to all browsers equally. The most common technical causes include:

Third-Party Cookie Blocking

OneDrive uses OAuth 2.0 authentication tokens stored in browser cookies. If the browser blocks third-party cookies, the upload request cannot authenticate. Starting in 2024, Chrome and Edge have stricter default cookie policies. Firefox and Safari also block third-party cookies by default in private browsing mode.

Browser Extensions Interfering with Upload

Ad blockers, privacy extensions, and script blockers like uBlock Origin, Ghostery, or NoScript can block the JavaScript that handles the upload progress bar and file chunking. These extensions may allow the page to load but silently block file upload requests.

Cached or Corrupted Browser State

A stale cache or corrupted IndexedDB storage for the OneDrive web app can cause uploads to hang or fail with a generic error. Clearing the cache for the specific site usually resolves this.

Network Proxy or VPN Configuration

Some mobile workers use VPNs or corporate proxies that route traffic through different endpoints. If the browser uses a different proxy configuration than the system default, upload requests may time out or be blocked.

Admin Checklist: Steps to Diagnose a Browser-Specific Upload Failure

Follow these steps in order. Each step isolates a different layer of the problem.

Step 1: Confirm the Issue Is Browser-Specific

1. Ask the user to test with a second browser
   Instruct the user to open a different browser on the same device. Use Microsoft Edge if the failing browser is Chrome, or use Chrome if the failing browser is Edge. If the upload succeeds in the second browser, the problem is local to the first browser.
2. Test with a different device on the same network
   Have the user try uploading from a phone or tablet connected to the same Wi-Fi network. If the upload works on the other device, the issue is device-specific, not network-specific.
3. Test with the same browser in private or incognito mode
   Open a private browsing window in the failing browser. If the upload works there, the cause is likely an extension or cached data in the normal profile.

Step 2: Check Browser Settings and Extensions

1. Verify third-party cookie settings
   In Chrome, go to Settings > Privacy and security > Third-party cookies. Set to Allow third-party cookies. In Edge, go to Settings > Cookies and site permissions > Manage and delete cookies and site data. Ensure Block third-party cookies is turned off.
2. Disable all extensions temporarily
   In Chrome, go to chrome://extensions and toggle off each extension. In Edge, go to edge://extensions. Restart the browser and test the upload again. Re-enable extensions one by one to identify the blocker.
3. Clear site data for OneDrive
   In Chrome, open the lock icon next to the URL, click Site settings, then Clear data. In Edge, open the lock icon, click Cookies and site permissions, then Manage and delete cookies and site data. Remove all data for onedrive.live.com and sharepoint.com.

Step 3: Use Browser Developer Tools to Capture Errors

1. Open Developer Tools
   Press F12 or right-click the page and select Inspect.
2. Switch to the Console tab
   Attempt the upload. Look for red error messages. Common errors include “Failed to load resource: net::ERR_BLOCKED_BY_CLIENT” which indicates an extension blocked the request, or “Access-Control-Allow-Origin” errors which indicate a CORS misconfiguration.
3. Switch to the Network tab
   Filter by XHR or Fetch. Watch for upload requests that return a 403 Forbidden or 401 Unauthorized status. A 403 often means the authentication token is missing or expired.
4. Check the Application tab for IndexedDB
   Expand IndexedDB and look for a database named “OneDrive” or “Microsoft”. Right-click and delete it. Then reload the page and try the upload again.

Step 4: Verify Tenant Settings That Could Affect Uploads

1. Check OneDrive sync settings in the admin center
   Go to Microsoft 365 admin center > Settings > Org settings > OneDrive > Sync. Ensure Allow syncing only on PCs joined to specific domains is not enabled. This setting blocks all web uploads from unmanaged devices.
2. Check file type restrictions
   In the same Sync settings pane, verify Block syncing of specific file types is not blocking the file the user is trying to upload. If the file type is blocked, the web upload will fail silently.
3. Check Conditional Access policies
   Go to Microsoft Entra admin center > Protection > Conditional Access. Look for policies that require compliant devices or specific browsers. If a policy targets the browser the user is using, it may block uploads.

Step 5: Test Network and Proxy Configuration

1. Disable VPN temporarily
   Ask the user to disconnect from any VPN and try the upload again. If it works, the VPN is routing OneDrive traffic through a restricted endpoint.
2. Check proxy settings in the browser
   In Chrome, go to Settings > System > Open your computer’s proxy settings. Ensure the proxy is not set to a manual proxy that blocks https://onedrive.live.com and all subdomains.
3. Test with a mobile hotspot
   Have the user switch from the corporate Wi-Fi to a personal mobile hotspot. If the upload succeeds, the corporate network has a firewall or proxy rule that blocks large uploads to OneDrive.

If OneDrive Still Has Upload Issues After the Main Fix

Upload Fails with “File Too Large” Error

OneDrive web upload has a file size limit of 250 GB per file. If the user sees this error for a file under that limit, the browser may be misreporting the file size. Have the user compress the file into a ZIP archive and upload that instead. If the ZIP uploads, the original file may be corrupted.

Upload Starts but Stops at 99 Percent

This usually indicates a network timeout during the final chunk upload. Ask the user to disconnect and reconnect to the network, then try again. If the problem persists, clear the browser cache for OneDrive and restart the browser.

Upload Fails Only for Certain File Types

Check the tenant file type block list in Microsoft 365 admin center > Settings > Org settings > OneDrive > Sync > Block syncing of specific file types. If the file extension is on that list, web upload will fail. Also check if the file extension is blocked by the browser’s download manager. For example, .exe and .msi files are often blocked by corporate browsers.

Browser-Specific Upload Capabilities: Edge vs Chrome vs Firefox

Item	Microsoft Edge	Google Chrome	Mozilla Firefox
Third-party cookie default	Blocked in InPrivate; allowed in normal mode	Blocked by default since Chrome 80	Blocked in Private Browsing; allowed in normal mode
OneDrive web upload support	Full support with drag-and-drop and folder upload	Full support but requires cookies enabled	Full support but may block file type detection
Maximum upload size via web	250 GB per file	250 GB per file	250 GB per file
Extension interference risk	Low with default settings	Moderate due to popular ad blockers	Moderate due to privacy-focused extensions

All three browsers support the same OneDrive web upload features. The differences lie in default cookie policies and extension ecosystems. Chrome’s default blocking of third-party cookies is the most common reason for upload failures in that browser.

When a mobile worker uses a browser with strict cookie defaults, the OneDrive web app cannot maintain the authentication session across upload chunks. The result is a silent failure or a generic error message. Enabling third-party cookies for onedrive.live.com and sharepoint.com resolves this in nearly all cases.

For organizations that cannot allow third-party cookies due to security policies, instruct users to access OneDrive through the Edge browser with the “Allow for this site” option set in Cookie settings. Edge’s enterprise mode also supports legacy authentication flows that bypass some cookie restrictions.