Fix SharePoint Redirects and 403 Errors in Chrome or Edge
Question details
Users need to resolve an issue where accessing SharePoint causes continuous redirects to the sign-in page and returns 403 Forbidden errors on Chromium-based browsers.

- Product
- Microsoft SharePoint
- Device & OS
- not provided
- Scenario
- Accessing SharePoint sites or interacting with SharePoint REST APIs using Google Chrome or Microsoft Edge.
- Observed behavior
- The browser repeatedly redirects the user to the sign-in page, and SharePoint REST API requests fail by returning a 403 Forbidden error, whereas Mozilla Firefox may function normally.
Before escalating the issue to your IT team, try clearing your browser's cache and cookies, or attempt to open SharePoint in an Incognito/InPrivate window to rule out temporary local token conflicts.
Contact Microsoft 365 Support via Admin Center
Since this specific browser behavior is tied to backend authentication failures, it requires investigation by the Microsoft 365 backend support team using your browser network logs.
Authentication loops and 403 Forbidden errors on specific Chromium-based browsers often indicate a deeper issue with how Microsoft Entra ID (formerly Azure AD) handles session tokens for your organization's tenant. Resolving this requires backend diagnostics.
If you are an end-user, reach out to your IT helpdesk, technical support, or the individual who originally provided your work or school email account.
Have your administrator log in to the Microsoft 365 admin center at admin.microsoft.com using their admin credentials.
Navigate to the 'Support' section on the left-hand menu and click on 'Help & support'. Enter a brief description of the 403 Forbidden and redirect loop issue to initiate a service request.
Follow the Microsoft support agent's instructions to capture HAR (HTTP Archive) network logs from Google Chrome or Microsoft Edge to help them trace the authentication failure.

Looking for a Hassle-Free Alternative to Microsoft 365? Try WPS Office
Dealing with cloud access issues, browser redirects, and constant permission errors can severely disrupt your daily workflow. WPS Office provides a robust, lightweight, and completely free alternative to Microsoft Office. With seamless offline document management and excellent format compatibility, you can keep working smoothly without relying heavily on web-based setups.
- 1. Download the Installer: Visit the official WPS Office website and click the free download button to get the setup file.
- 2. Install WPS Office: Run the downloaded installer and follow the simple on-screen instructions to set up the software on your computer.
- 3. Open Existing Documents: Launch WPS Office and directly open your existing Microsoft Office files to continue working without interruption.

Frequently Asked Questions
Why does SharePoint work in Firefox but not in Chrome or Edge?
This discrepancy often occurs due to differences in how Chromium-based browsers (Chrome, Edge) and Firefox handle cross-site tracking, third-party cookies, and caching mechanisms. If a Chromium browser blocks a necessary authentication cookie, SharePoint forces a sign-in redirect, resulting in an infinite loop.
Can clearing my browser cache fix the 403 Forbidden error in SharePoint?
Yes, occasionally a corrupted authentication token or outdated cookie in your browser cache can cause 403 errors. Clearing your cache and cookies forces the browser to fetch a fresh security token, which may resolve local instances of the issue.
What does a 403 Forbidden error mean in a SharePoint REST API?
A 403 Forbidden error indicates that the server understands your request but refuses to authorize it. In the context of SharePoint APIs, this typically means your current session token is invalid, has expired, or your user account lacks the specific permissions required to access the requested site or resource.
How can I find out who my Microsoft 365 administrator is?
If you are using Microsoft 365 for business or school, your administrator is usually the IT department or the technical support team that provided your login credentials. For smaller organizations, it may be the business owner or the person managing the company's software licenses.




