OneDrive Admin Checklist: web upload fails in one browser for field teams

Field teams often rely on the OneDrive web interface when the sync client is not installed or blocked on company-managed devices. When web uploads fail in one specific browser while working in another, the root cause is almost always a browser configuration issue rather than a OneDrive service outage. This article explains why a single browser can block file uploads and provides a structured checklist for administrators to diagnose and resolve the problem across field devices.

Why OneDrive Web Uploads Fail in a Single Browser

OneDrive for the web uses a combination of cookies, local storage, and service workers to authenticate the user and manage file chunks during upload. When a browser blocks cookies from Microsoft domains, the upload dialog may appear but the file never reaches the server. The same failure can occur if the browser has disabled third-party cookies, which OneDrive requires for cross-domain authentication between login.microsoftonline.com and yourtenant.sharepoint.com.

Another common cause is an extension or add-on that interferes with drag-and-drop events or the File API. Ad blockers, script blockers, and privacy-focused extensions frequently strip the headers that OneDrive uses to verify the upload session. Field teams using a managed browser may also be subject to group policies that restrict local storage size or disable service workers.

The key diagnostic clue is that the problem appears in only one browser across multiple devices. This eliminates tenant-level settings like upload throttling or file size limits, which would affect all browsers equally. The checklist below walks through each verification step in order of likelihood.

Admin Checklist to Resolve Browser-Specific Upload Failure

Step 1: Verify the Browser Version and Update Status

1. Open the browser’s About page
   In Chrome, go to chrome://settings/help. In Edge, go to edge://settings/help. In Firefox, go to about:preferences#general and scroll to Firefox Updates. Confirm the browser is on the latest stable release. An outdated browser may lack support for modern fetch APIs that OneDrive requires.
2. Check for pending updates on managed devices
   If field devices are managed through Microsoft Intune or a third-party MDM, verify that the browser update ring is active. Stale versions older than two major releases often break upload functionality.

Step 2: Clear Site Data and Cookies for Microsoft Domains

1. Navigate to the browser’s site settings
   In Chrome or Edge, open chrome://settings/siteData or edge://settings/siteData. Search for microsoft.com, sharepoint.com, live.com, and office.com. Click the trash icon to delete all stored data for these domains.
2. Clear cookies specifically
   In Firefox, go to about:preferences#privacy, click “Manage Data,” search for the same domains, and remove them. Do not clear all browser data — only Microsoft-related sites — to preserve other session data that field teams rely on.
3. Restart the browser and test the upload
   Sign in to OneDrive again and attempt to upload a small file under 10 MB. If the upload succeeds, the issue was stale or corrupted site data.

Step 3: Disable All Extensions and Re-enable One by One

1. Open the extensions management page
   In Chrome, go to chrome://extensions. In Edge, go to edge://extensions. In Firefox, go to about:addons. Toggle the switch to disable every extension.
2. Test the upload with all extensions disabled
   Upload a file to OneDrive. If it works, one of the extensions was the blocker. Re-enable extensions one at a time, testing after each, until the failing extension is identified.
3. Document the problematic extension
   Note the extension name and version. Search the Microsoft 365 admin center documentation to see if the extension is known to conflict with OneDrive. Add the extension to a block list for managed browsers if the field team does not require it.

Step 4: Check Third-Party Cookie and Local Storage Permissions

1. Open the browser’s privacy and security settings
   In Chrome, go to chrome://settings/cookies. In Edge, go to edge://settings/cookies. In Firefox, go to about:preferences#privacy under “Cookies and Site Data.” Ensure that third-party cookies are not blocked entirely. Set them to “Allow” or “Block only cross-site tracking” rather than “Block all.”
2. Add Microsoft domains to the allow list
   In the same settings page, add []microsoft.com, []sharepoint.com, []live.com, and []office.com as sites that can always use cookies and local storage.
3. Verify local storage quota
   Open the DevTools Console (F12) and type navigator.storage.estimate(). If the quota is below 100 MB, the browser may refuse to store upload chunk metadata. In managed environments, group policies can cap local storage — increase the limit to at least 500 MB.

Step 5: Inspect Network Traffic for Blocked Requests

1. Open the browser’s DevTools Network tab
   Press F12, click the Network tab, and reload the OneDrive page. Attempt an upload while the Network tab is recording. Look for requests that return HTTP 403, 404, or 500.
2. Filter by XHR or Fetch requests
   Use the filter input to show only XHR or Fetch requests. OneDrive uploads use the upload.aspx or personal/api/v2.0/upload endpoints. A 403 error often indicates a missing or expired authentication cookie.
3. Check the Console tab for CSP violations
   Switch to the Console tab. A Content Security Policy violation message like “Refused to connect to ‘https://yourtenant.sharepoint.com’ because it violates the document’s Content Security Policy” means a browser extension or group policy is blocking the connection. Remove the violating CSP directive or disable the extension.

If OneDrive Still Has Issues After the Main Fix

OneDrive upload fails only in Edge with IE mode enabled

When Edge is configured to open certain sites in Internet Explorer mode, the legacy Trident engine does not support the modern File API that OneDrive requires. Go to edge://settings/defaultBrowser and check “Allow sites to be reloaded in Internet Explorer mode.” Remove the SharePoint and OneDrive URLs from the IE mode site list. If the policy is enforced through Group Policy, update the “Configure Internet Explorer mode” policy to exclude your tenant’s SharePoint domain.

OneDrive upload works in Chrome but not in Firefox

Firefox applies Enhanced Tracking Protection by default, which can block the login.microsoftonline.com cookies needed for OneDrive authentication. Click the shield icon next to the address bar and turn off Enhanced Tracking Protection for the OneDrive site. For managed Firefox deployments, use the privacy.trackingprotection.fingerprinting.enabled and privacy.trackingprotection.cryptomining.enabled preferences in Firefox policies.json to allow Microsoft domains.

OneDrive upload fails for files over 100 MB in one browser

OneDrive web uploads chunk files into 4 MB blocks. If the browser’s local storage quota is too small to hold chunk metadata, the upload fails silently. Open DevTools and run navigator.storage.estimate(). If the quota is under 200 MB, increase it through the browser’s storage settings or remove the group policy that caps it. For Chrome, the policy is StorageQuota under Computer Configuration > Administrative Templates > Google > Google Chrome.

Browser Settings vs Group Policy: Causes of Upload Failure

Item	Browser Settings	Group Policy
Scope	Affects only the local user profile on one device	Applied to all managed devices in the organization
Third-party cookies	User can toggle in Privacy & Security settings	Policy “Block third-party cookies” in Chrome or Edge administrative templates
Local storage quota	Set per browser; default is usually 10% of disk	Policy “StorageQuota” caps local storage to a fixed MB value
Extension control	User can disable extensions manually	Policy “ExtensionInstallBlocklist” or “ExtensionInstallForcelist” in Chrome/Edge
IE mode	User can remove sites from IE mode list	Policy “InternetExplorerIntegrationSiteList” enforces IE mode for specific URLs
Diagnostic access	DevTools available to any user	Policy “DeveloperToolsAvailability” can disable DevTools entirely

The primary difference is that browser settings are user-configurable and device-specific, while group policies are enforced centrally and override user preferences. When uploads fail on a managed device, always check group policies first because they can silently block the settings that OneDrive requires.

After completing the checklist, field teams should be able to upload files in the previously failing browser. If the issue persists, use the DevTools Network and Console tabs to capture the exact HTTP error and share it with Microsoft support. As an advanced step, deploy a browser extension allow list via Intune that explicitly permits only the extensions known to be compatible with OneDrive web uploads.