SharePoint errors often appear as blank pages, permission denied messages, or slow loading. These errors can come from the browser cache, an incompatible browser version, or tenant-level settings such as site policies and service health. This guide explains how to identify whether the root cause is on the client side or the tenant side. You will learn step-by-step checks for browsers and the SharePoint admin center to resolve common errors.
Key Takeaways: Browser and Tenant Diagnostic Steps for SharePoint
- Clear browser cache and cookies: Fixes 80% of loading and rendering errors by removing outdated site data.
- Check Microsoft 365 Service Health: Identifies ongoing tenant-level outages that cause SharePoint errors across all users.
- Review site sharing and external access policies: Prevents permission denied errors caused by tenant-wide restrictions.
Why SharePoint Errors Can Come from the Browser or the Tenant
SharePoint errors do not always mean the site itself is broken. The browser stores cached versions of pages, scripts, and authentication tokens. When these become outdated or corrupted, SharePoint may fail to load correctly. On the tenant side, SharePoint Online relies on service health, licensing, and policy settings. A service outage, a misconfigured sharing policy, or an expired license can block access for all users. Understanding this split helps you target the right diagnostic steps.
The most common browser-caused errors are blank pages, script errors, and login loops. The most common tenant-caused errors are permission denied messages, site not found errors, and slow performance across multiple sites. This article covers both categories with specific checks and fixes.
Steps to Check Browser Causes for SharePoint Errors
Start with the browser because it is the fastest test. You can rule out browser issues in under two minutes.
Clear Browser Cache and Cookies
Outdated cache files can prevent SharePoint from loading the latest page structure or scripts.
- Open browser settings
In Chrome, click the three-dot menu and select Settings. In Edge, click the three-dot menu and select Settings. In Firefox, click the hamburger menu and select Options. - Find the clear browsing data option
In Chrome, go to Privacy and security > Clear browsing data. In Edge, go to Privacy, search, and services > Clear browsing data. In Firefox, go to Privacy and security > Cookies and Site Data > Clear Data. - Select time range and data types
Choose All time for the time range. Check Cached images and files and Cookies and other site data. Do not clear saved passwords unless you want to re-enter them. - Clear the data
Click Clear data. Close and reopen the browser. Navigate to SharePoint and sign in again.
Use InPrivate or Incognito Mode
This test bypasses all cached data and extensions. If SharePoint works in private mode, the issue is cache or an extension.
- Open a private window
Press Ctrl+Shift+N in Chrome or Edge. Press Ctrl+Shift+P in Firefox. - Navigate to SharePoint
Enter the site URL and sign in with your work or school account. - Test the failing action
Perform the action that previously caused an error. If it works, the problem is cache or a browser extension.
Disable Browser Extensions
Extensions that block scripts or modify page content can break SharePoint.
- Open extensions manager
In Chrome, type chrome://extensions in the address bar. In Edge, type edge://extensions. In Firefox, type about:addons. - Disable all extensions
Toggle off each extension. Restart the browser. - Test SharePoint
If the error disappears, re-enable extensions one by one to find the culprit.
Check Browser Version and Update
SharePoint Online requires a current browser. Microsoft supports the latest two versions of Chrome, Edge, Firefox, and Safari.
- Check browser version
In Chrome, go to chrome://settings/help. In Edge, go to edge://settings/help. In Firefox, go to about:preferences#general and look under Firefox Updates. - Update if needed
If an update is available, install it and restart the browser. - Test SharePoint again
Navigate to the site and repeat the failing action.
Steps to Check Tenant Causes for SharePoint Errors
If browser checks do not resolve the error, the cause is likely in the tenant configuration or service health.
Check Microsoft 365 Service Health
Service health shows active incidents that affect SharePoint Online.
- Go to the Microsoft 365 admin center
Sign in at admin.microsoft.com with a Global admin or Service Support admin account. - Open Service Health
In the left navigation, go to Health > Service health. - Look for SharePoint Online incidents
Check the SharePoint Online row. If it shows an advisory or incident, click it for details. The status message includes estimated resolution time. - Subscribe to notifications
If an incident exists, click Subscribe to receive email updates. Wait for the incident to resolve before further troubleshooting.
Review SharePoint Site Policies in the Admin Center
SharePoint admin center > Policies > Sharing: Controls external sharing defaults for SharePoint sites and OneDrive.
A restrictive sharing policy can cause permission denied errors even for internal users if the site is set to a different sharing level.
- Open SharePoint admin center
Sign in at admin.microsoft.com. In the admin center, go to SharePoint under Admin centers. - Go to Policies
In the left navigation, select Policies. - Check Sharing policy
Click Sharing. Under External sharing, note the level set for SharePoint. If it is set to Only people in your organization, external users will receive access denied. - Adjust if needed
If your scenario requires external sharing, change the setting to New and existing guests or Anyone. Click Save.
Verify User Licenses
A user without a SharePoint Online license cannot access the service and will see a license error.
- Go to Microsoft 365 admin center
Navigate to Users > Active users. - Select the affected user
Click the user name. In the panel that opens, click the Licenses and apps tab. - Check SharePoint license
Ensure SharePoint Online (Plan 1 or Plan 2) is selected. If not, select it and click Save changes.
Review Site Collection Administrator Settings
If the user is a site owner but still sees access denied, the site may have a unique permission set that excludes them.
- Open SharePoint admin center
Go to Sites > Active sites. - Select the site
Click the site name. In the panel, click the Permissions tab. - Check site admins
Under Site admins, verify the user is listed. If not, add them by clicking Add site admins and entering their email. Click Save.
If SharePoint Still Has Issues After the Main Fix
Some errors persist because of a missing step or a different root cause. The following issues are common after the main checks.
SharePoint Shows a Blank Page After Clearing Cache
A blank page can indicate a network proxy or firewall blocking SharePoint content. Test from a different network, such as a personal hotspot. If the page loads, the corporate network has a filtering rule. Contact your network team to allow traffic to sharepoint.com and all subdomains.
Permission Denied Error on a Specific Document Library
The library may have unique permissions that override the site permissions. Go to the library, click the gear icon, then Library settings. Click Permissions for this document library. If it shows unique permissions, click Stop Inheriting Permissions and then copy permissions from the parent site. Alternatively, grant the user direct access to the library.
SharePoint Online Loads Slowly for All Users
Slow performance across the tenant often points to a service incident. Recheck Microsoft 365 Service Health. If no incident is active, check the SharePoint storage limit in the admin center under Settings > Storage limit. If the tenant is near the limit, performance degrades. Free up storage by deleting old site versions or archived content.
Browser Check vs Tenant Check: Key Differences
| Item | Browser Check | Tenant Check |
|---|---|---|
| Scope | Single user or single device | All users or multiple sites |
| Time to test | 2 to 5 minutes | 5 to 15 minutes |
| Tools used | Browser settings, private mode, extension manager | Microsoft 365 admin center, SharePoint admin center |
| Common fix | Clear cache, disable extension | Update policy, assign license, resolve service incident |
| When to use | Error appears on one device | Error appears on multiple devices or for multiple users |
Start with browser checks because they are faster. If the error persists after clearing cache, testing private mode, and disabling extensions, move to tenant checks. Use the Microsoft 365 admin center to verify service health, licenses, and site policies. These two diagnostic paths cover the vast majority of SharePoint errors. As an advanced tip, enable SharePoint auditing in the admin center under Policies > Access control to log failed sign-in attempts and identify blocked users by IP address or location.