Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | SHAREPOINT_ACCESSDENIED | SharePoint Online console | -> |
| Affected build range | Windows 11 23H2 | OS version | |
| Registry key involved | -> check for Kerberos config if hybrid | ||
| Relevant service/endpoint URL | https://admin.microsoft.com | SharePoint admin center | |
| Log line signature | Event ID 5200/5214 in Security log | Windows Event Viewer | -> Kerberos/token failure |
Log Files to Check
C:\Windows\System32\winevt\Logs\Security.evtxSharePoint Online Unified Audit Log
What This Error Actually Means
The error code SHAREPOINT_ACCESSDENIED is raised when a user attempts to access a SharePoint Online site collection or document library and encounters permission issues despite having the correct Azure AD group membership. The component responsible for this error is primarily the SharePoint Online service, which checks permissions against the current configuration of Conditional Access policies, site sensitivity labels, and direct permissions granted within SharePoint itself. This error can also be triggered by inconsistencies in how Active Directory groups are synced to SharePoint Online through Azure AD.Affected Versions and Scope
This issue is most prevalent on Windows 11 build 23H2 due to its integration with modern authentication protocols, including Kerberos and OAuth tokens. The error can occur across various tenant configurations, particularly those that have recently updated Conditional Access policies or modified site sensitivity labels. However, it does not affect tenants where permissions are correctly mapped from Azure AD groups to SharePoint Online users, and no recent changes have been made to the security infrastructure.Where To Look First: Logs and Event IDs
To diagnose this issue, start by examining the Security log in Windows Event Viewer for Event ID 5200 or 5214. These event IDs often indicate Kerberos token failures or issues with hybrid configurations that may be contributing to the access denied error. Additionally, review the SharePoint Online Unified Audit Log for any sharing inheritance broken events using the following PowerShell cmdlet:Search-UnifiedAuditLog -RecordType SharePoint -Operations SharingInheritanceBroken
This will help identify when and how permissions might have been altered or inherited incorrectly.
Root Causes
Conditional Access Policy Conflict
One common cause is a conflict with Conditional Access policies in Microsoft Entra ID. To determine if this is the case, navigate tohttps://admin.microsoft.com, then go to "Microsoft Entra admin center > Protection > Conditional Access". Check for any recent changes or new policies that might be blocking SharePoint Online access.
Inconsistent Group Syncing
Another cause can be inconsistencies in how Azure AD groups are synced with SharePoint. Use the following PowerShell cmdlets to verify group membership and permissions:Connect-PnPOnline -Url "https://tenant.sharepoint.com" -Interactive
Get-PnPSiteCollectionAdmin | Select-Object User, IsSiteCollectionAdmin
This will list all site collection administrators for verification.
Sensitivity Label Changes
Changes in sensitivity labels applied to SharePoint sites can also lead to permission issues. Navigate to the SharePoint admin center and check under "Policies > Sensitivity Labels" for any recent updates that might affect user access.Fix Procedure
To resolve this issue, follow these steps: 1. Connect to your SharePoint Online environment using PnP PowerShell:Connect-PnPOnline -Url "https://tenant.sharepoint.com" -Interactive
2. Verify the current site collection administrators and group memberships:
Get-PnPSiteCollectionAdmin | Select-Object User, IsSiteCollectionAdmin
Get-PnPGroupMember -Identity "GroupName" | Format-Table LoginName, Title
3. If necessary, re-grant permissions through the SharePoint admin center:
- Navigate to https://admin.microsoft.com
- Go to "SharePoint admin center > Sites > Active sites"
- Select the site collection and click on "Permissions" to manage access.
4. Alternatively, use PowerShell cmdlets to adjust user roles directly:
Set-SPOUser -Site https://tenant.sharepoint.com/sites/sitecollection -LoginName [email protected] -IsSiteCollectionAdmin $true
5. Review and update Conditional Access policies if needed.
Error Code Variants
| Code | Description | Distinguishing Factors |
|---|---|---|
| SHAREPOINT_ACCESSDENIED | User lacks permission to access SharePoint resource. | Error occurs despite correct Azure AD group membership. |
| ACCESS_DENIED | Generic access denied error in Windows OS. | Occurs without specific SharePoint context, often due to local file permissions or network issues. |
| SHAREPOINT_OBJECTNOTFOUND | Resource not found in SharePoint. | Error indicates the resource does not exist rather than permission issues. |
Verification
To verify that the fix has been applied successfully, check the Security log for Event ID 5200 or 5214 to ensure no further Kerberos token failures are occurring. Additionally, review the SharePoint Online Unified Audit Log for any new access denied events:Get-PnPUnifiedAuditLog -ContentType SharePoint -StartTime (Get-Date).AddDays(-7)
The absence of these errors and the presence of correct permissions in the SharePoint admin center indicate a successful resolution.
Prevention
To prevent recurrence, ensure that any changes to Conditional Access policies or sensitivity labels are thoroughly tested before deployment. Regularly review group membership and permission settings using PowerShell cmdlets likeGet-PnPSiteCollectionAdmin. Establishing a baseline of permissions and regularly auditing these configurations can help catch discrepancies early.
Be cautious when modifying Conditional Access policies, as changes can affect access to multiple resources.
Use the
Get-PnPUnifiedAuditLog cmdlet to quickly identify recent permission-related issues without manually reviewing logs.