A 2026 troubleshooting guide for IT teams running SharePoint Online, OneDrive, Teams and Copilot. Updated October 2026.
Why SharePoint troubleshooting looks different in 2026
SharePoint is no longer just where files live. It stores every Teams channel's files, it triggers Power Automate flows, and it is the main content source Microsoft 365 Copilot reads when it answers a question. A permission mistake that used to mean one locked folder can now mean Copilot summarising a payroll file for the wrong person.
Most SharePoint tickets get slower, not faster, because someone changes three settings at once. They add a user directly to a file to close an access ticket, or create a new library when a view breaks. Six months later the tenant is full of broken inheritance and nobody knows why.
The faster approach is to sort every issue into one of six layers before touching anything: service health, identity, permissions, content structure, sync client, and automation ownership. Figure 1 shows the order we use on our own helpdesk tickets.
Figure 1. Work through the layers in order and change one variable at a time.
Before you change anything: capture the exact URL, the user's account, the time, the browser or app, the full error text, and whether one user, one site, or the whole tenant is affected. |
Problem 1: Access denied, even though the user is in the group
What users see: "You need permission to access this item" or "Access denied" on a site, library or file they believe they should reach.
Usual causes:
Broken inheritance. Someone shared a folder or file directly, so it no longer follows the site's Owners, Members and Visitors groups.
Restricted site access. With SharePoint Advanced Management, a site can be limited to specific groups. Users outside those groups are blocked even with a direct link.
Wrong account. The user is signed in with a personal or guest identity instead of their work account.
Draft visibility. Library versioning is set so only editors can see drafts, so readers cannot open unpublished files.
How to fix it:
1. Go to Site settings, Site permissions, Advanced permissions settings, then Check Permissions. Enter the user to see their effective access and where it comes from.
2. Open Library settings, then Permissions for this document library. If you see "This library has unique permissions", decide whether it really needs them. If not, select Delete unique permissions to inherit from the site again.
3. Ask the user to open the link in a private window and confirm which account they are signed in with.
4. Check whether restricted site access applies:
Get-SPOSite -Identity "https://contoso.sharepoint.com/sites/Finance" |
Select-Object RestrictedAccessControl, RestrictedAccessControlGroups
Microsoft explains the built-in groups and levels in Understanding permission levels in SharePoint. For the plain-English version, read our guide to SharePoint permissions: Owners, Members and Visitors.
Problem 2: Copilot or search shows files people should not see
What users see: Search results or Copilot answers that include salary sheets, board notes or HR files.
Why it happens: Copilot does not bypass permissions. It shows what a user can already open. The issue is that many older sites were shared with "Everyone except external users" or full of company-wide links nobody cleaned up. People never found those files by browsing, but Copilot and search find them in seconds.
How to fix it:
1. In the SharePoint admin center, run the Data access governance reports to find sites shared with large groups or with many sharing links.
2. On sensitive sites, remove "Everyone except external users" and company-wide groups from site permissions and SharePoint groups.
3. If you need a short-term safety net, turn on Restricted SharePoint Search. It limits organization-wide search and Copilot to an allowed list of up to 100 sites, while users still see their own files and content they recently used.
Set-SPOTenantRestrictedSearchMode -Mode Enabled
4. Apply sensitivity labels to the most sensitive content so protection travels with the file.
Microsoft's setup steps are in Restricted SharePoint Search. Treat it as a stop-gap, not the fix. The real fix is clean permissions, which is the first step of our Copilot readiness work.
Figure 2. Restricted SharePoint Search narrows what Copilot can draw from while permissions are cleaned up.
For a deeper look at how SharePoint is changing with AI agents, see SharePoint in 2026: agentic AI, storage economics and governance.
Problem 3: The 5,000 item list view threshold
What users see: "This view cannot be displayed because it exceeds the list view threshold (5000 items)." Sorting, filtering or grouping fails on large lists and libraries.
Why it happens: A list or library can hold up to 30 million items. The limit is on how many items one view can scan at once without an index. Buying more storage does not change it.
How to fix it:
1. In Library settings, open Indexed columns and add an index on the columns people filter and sort by, such as Department, Status or Modified. You can have up to 20 indexed columns per list.
2. Make the default view filter on an indexed column first, so it returns fewer than 5,000 items. Example: Status equals Active.
3. Do not rely on folders alone. A "show all items without folders" view will still hit the threshold.
4. Move closed or old content to an archive library so active views stay small.
See Microsoft's guidance on the list view threshold error and managing large lists and libraries. Full platform limits are in the SharePoint limits service description.
Figure 3. Storage and the view threshold are two different limits.
If your libraries are deep folder trees copied from an old file server, our SharePoint information architecture guide covers how to restructure with metadata.
Problem 4: OneDrive sync stalls or shows red errors
What users see: "Processing changes" that never finishes, red X icons in File Explorer, or a laptop that slows down whenever OneDrive is running.
Usual causes:
Too many items. Microsoft notes sync performance can suffer beyond about 300,000 files across everything a user syncs.
Double syncing. The same library is added with both Sync and Add shortcut to My files.
Long paths or blocked names. The full path is limited to 400 characters, and some names and characters are not allowed.
How to fix it:
1. Move users from the Sync button to Add shortcut to My files. Remove any duplicate sync relationships.
2. Enforce Files On-Demand through Intune so files stay in the cloud until opened.
3. Shorten deep folder names that push paths over the limit.
4. If the client is stuck, reset it and let it rebuild:
%localappdata%\Microsoft\OneDrive\onedrive.exe /reset
Figure 4. Shortcuts are easier to support than per-library Sync on large tenants.
Not sure which content belongs in OneDrive versus SharePoint? Read OneDrive vs SharePoint vs Teams: where files should live. For storage questions, see SharePoint Online storage limits explained.
Problem 5: Power Automate flows stop after someone leaves
What users see: Approvals stop arriving, documents are not tagged, and nobody notices for days.
Why it happens: The flow was built in one person's account using their connections. When that account is disabled, every SharePoint connection it owns stops working.
How to fix it:
1. Add a second owner, ideally an IT group, to every business-critical flow.
2. Move important flows into a Power Platform solution so they can be managed and moved between environments.
3. Switch connections to a dedicated service account or service principal where the connector supports it.
4. Set up failure alerts so a broken run reaches IT the same day.
Microsoft covers connection management in Manage connections in Power Automate. If your flows have grown into a tangle, our business process automation team can rebuild them properly.
Problem 6: External guests cannot open shared files
What users see: Partners report that a link has expired, their email is not recognised, or they keep being asked to sign in.
Usual causes: the site's sharing setting is stricter than the tenant setting, the guest redeemed the invite with a different email, or a Conditional Access policy requires something a guest cannot meet.
How to fix it:
1. In the SharePoint admin center, open the site and check its external sharing level. A site can be stricter than the tenant, never more open.
2. In the Entra admin center, find the guest and confirm the invitation was accepted. Resend or reset redemption if it is still pending.
3. In Manage access, remove expired links and reshare with Specific people.
Microsoft's reference: Manage sharing settings for SharePoint and OneDrive.
Quick reference: symptom to fix
Symptom | Likely cause | Where to check | Lasting fix |
Access denied for a group member | Broken inheritance or restricted site access | Check Permissions in site settings | Group-based access, fewer direct shares |
Copilot shows sensitive files | Sites shared with everyone | Data access governance reports | Permission cleanup, labels, RSS while fixing |
5,000 item view error | Unindexed view on a large list | Library settings, Indexed columns | Indexed filtered views, archive old items |
OneDrive sync stuck | Too many items, double sync, long paths | OneDrive sync status | Shortcuts and Files On-Demand |
Flow stopped running | Owner account disabled | Power Automate run history | Co-owners, solutions, service accounts |
Guest cannot open link | Site sharing or invite mismatch | Entra users, site sharing settings | Specific-people links, guest reviews |
Turn every fix into a standard
Solving the ticket is half the job. If the same problem comes back, the real fix is a standard: a group naming rule, a co-owner rule for flows, a default view template, or a guest review schedule. Track a few numbers so you know it is working:
Time to find the cause. Is triage getting faster?
Repeat tickets. Did the fix stop the pattern or only help one user?
Fixes without rollback. Are changes controlled?
Runbook coverage. Could another engineer solve this next time?
How MSPowerhouse helps
Our Microsoft-certified engineers handle SharePoint tickets every week for businesses across the US. When the same issues keep coming back, we fix the structure behind them.
Day-to-day support. L1 and L2 tickets through our helpdesk, with clear SLAs and escalation.
SharePoint cleanup and design. Permissions, site structure and libraries through our SharePoint services.
Copilot readiness. Oversharing reports, permission cleanup and Restricted SharePoint Search setup before rollout.
Migrations. File shares and older SharePoint moved with a tested plan. See our SharePoint migration checklist and file share migration guide.
Ongoing management. Monitoring, reporting and support through managed IT services.
Wondering if you need outside help? Here are 10 signs you might need a SharePoint consultant.
Tired of the same SharePoint tickets? Book a free 30-minute review with our engineers. We will look at your sharing settings, library structure and Copilot exposure, and give you a short list of fixes. |
