OneDrive Admin Checklist: web upload fails in one browser for external sharing

When an external sharing recipient tries to upload a file to a OneDrive shared folder through the web browser and the upload fails only in that specific browser, the cause is rarely a server outage. Browser extensions, cached credentials, or incorrect security settings often block the upload while other browsers work normally. This article explains how to isolate the browser-side cause and provides a step-by-step checklist for administrators to resolve the failure without disabling security controls across the tenant.

Why Web Uploads Fail in One Browser for External Sharing

OneDrive uses Microsoft 365 authentication tokens stored in browser cookies and local storage. When an external recipient accesses a shared folder via a browser, the browser must allow cross-origin requests to sharepoint.com domains, execute JavaScript from multiple Microsoft endpoints, and maintain a session cookie for the upload chunking process. If any of these elements are blocked by a browser extension, a strict privacy setting, or corrupted cache, the upload fails with a generic error such as “Upload failed” or “Something went wrong.” The failure is browser-specific because each browser maintains its own extension set, cookie store, and security profile. The server-side sharing link and permissions remain intact; the issue lies entirely in the browser environment.

Step-by-Step Checklist for Administrators

Before changing any tenant-level settings, follow these steps in order. Perform each step on the affected browser only.

Step 1: Confirm the Failure Is Browser-Specific

1. Test upload in a different browser on the same device
   Open Microsoft Edge, Google Chrome, or Mozilla Firefox. Navigate to the same OneDrive shared folder and attempt the same file upload. If the upload succeeds, the problem is isolated to the original browser.
2. Test upload in the same browser on a different device
   Log into the external sharing recipient account on another computer using the same browser brand. If the upload works, the cause is local to the first device’s browser profile.

Step 2: Clear Browser Cache and Cookies for Microsoft Domains

1. Open browser settings
   In Chrome, click the three-dot menu > Settings > Privacy and security > Clear browsing data. In Edge, click the three-dot menu > Settings > Privacy, search, and services > Clear browsing data.
2. Select time range and data types
   Set the time range to “All time.” Check “Cookies and other site data” and “Cached images and files.” Do not clear saved passwords or autofill data.
3. Clear only Microsoft domains
   Click “Clear data.” Alternatively, use the site-specific clearing option: In Chrome, go to Settings > Privacy and security > Site Settings > See all sites. Search for “sharepoint.com” and “microsoftonline.com” and clear their data individually.

Step 3: Disable Browser Extensions Temporarily

1. Open the extension manager
   In Chrome, type chrome://extensions in the address bar. In Edge, type edge://extensions.
2. Disable all extensions
   Toggle each extension off. Do not uninstall yet. Restart the browser.
3. Retest the upload
   If upload succeeds, enable extensions one by one and test after each enable to identify the blocking extension. Common culprits include ad blockers like uBlock Origin, privacy extensions like Privacy Badger, and script blockers like NoScript.

Step 4: Check Third-Party Cookie and JavaScript Settings

1. Verify third-party cookie permissions
   In Chrome, go to Settings > Privacy and security > Third-party cookies. Ensure “Block third-party cookies” is not enabled. If it must remain on, add []sharepoint.com and []microsoftonline.com to the “Allowed to use third-party cookies” list.
2. Verify JavaScript is enabled
   In Chrome, go to Settings > Privacy and security > Site Settings > JavaScript. Ensure “Allowed” is selected. If site-specific overrides exist, remove any block for sharepoint.com domains.

Step 5: Use Browser Developer Tools to Capture the Failure

1. Open developer tools
   Press F12 or Ctrl+Shift+I. Click the Network tab.
2. Reproduce the upload
   Select the file and click Upload. Watch the network log. Look for requests to sharepoint.com that return status 403 Forbidden or 401 Unauthorized.
3. Check the Console tab
   Click the Console tab. Note any error messages that mention “CORS” or “cross-origin.” A CORS error indicates the browser blocked a cross-origin request due to missing or invalid headers.

Step 6: Reset Browser Settings to Default

1. Reset in Chrome
   Go to Settings > Reset and cleanup > Restore settings to their original defaults. Confirm the reset. This preserves bookmarks and passwords but removes extensions and site permissions.
2. Reset in Edge
   Go to Settings > Reset settings > Restore settings to their default values. Click Reset.

If the Upload Still Fails After Browser Troubleshooting

External sharing link permissions are too restrictive

The sharing link may be set to “View” only. Go to the OneDrive folder in the browser, click the share icon, and verify the link type is “Edit” or “Upload” for external recipients. If the link was created with “Allow editing” unchecked, recipients cannot upload files regardless of browser behavior.

Tenant-level upload restrictions block the file type

An administrator may have blocked specific file extensions via the SharePoint admin center. Go to Microsoft 365 admin center > SharePoint > Policies > Access control > Block file extensions. If the file type is listed, users cannot upload it in any browser. Remove the extension or choose a different file format.

Conditional Access policies require a compliant device

If the external recipient accesses the link from an unmanaged device, a Conditional Access policy may block the upload session. The browser may fail silently. Check the Microsoft Entra admin center under Protection > Conditional Access > Policies for any policy targeting external users or guest accounts that requires device compliance.

Browser profile corruption

If all browser-level steps fail, create a new browser profile. In Chrome, click the profile icon > Add > Sign in without an account. In Edge, click the profile icon > Add profile > Add. Test the upload in the new profile. If it works, migrate bookmarks and extensions from the old profile, then delete the corrupted profile.

Browser Troubleshooting vs Tenant-Level Settings: Key Differences

Item	Browser Troubleshooting	Tenant-Level Settings
Scope	Single browser on one device	Entire Microsoft 365 organization
Typical cause	Extension, cookie block, cache corruption	Sharing policy, Conditional Access, file type block
Fix duration	5 to 15 minutes	30 minutes to several hours for policy propagation
Tools used	Browser settings, developer tools, extension manager	Microsoft 365 admin center, SharePoint admin center, Microsoft Entra admin center
Impact of fix	Affects only the local user session	Affects all external sharing recipients

After completing the browser-side checklist, the external sharing recipient should be able to upload files in the previously failing browser. If the problem persists, inspect the tenant-level sharing link permissions and Conditional Access policies as described above. A useful final step is to have the recipient test the upload using a browser InPrivate or Incognito window, which disables all extensions and uses a temporary session by default, to confirm the root cause is indeed browser configuration rather than server settings.