Edge and Chrome issue with sharepoint auth

Here's a remediation guide for SharePoint sign-in problems:

Cause: The issue isn't isolated to a specific device or browser cache, as it persists across devices and after OS reinstallation. The problem is most likely due to corrupted tokens or outdated session data in Azure AD/WAM, potentially caused by a recent Edge update.

Steps:

1. Check PRT Status:
   • Open Command Prompt as administrator and run dsregcmd /status.
   • Under Device State, confirm AzureAdJoined, SSO State, and PRT Status are all YES. SSO will fail if the PRT is missing or bad.
2. Revoke User Sessions:
   • In Azure AD, go to Users > [Affected User] > Sign-ins and check for errors.
   • Under Authentication Methods, click Revoke Sessions to force a new token refresh.
3. Remove Device Registration:
   • In Azure AD, go to Devices > [Affected Device] and click Delete.
   • On the device, run dsregcmd /leave, reboot, then run dsregcmd /join to rejoin Azure AD.
4. Clear WAM and Credentials:
   • On the device, sign out of all Edge accounts.
   • Go to Settings > Accounts > Access work or school and disconnect the work account.
   • Open Credential Manager and delete entries for login.microsoftonline.com and sharepoint.com. Reboot and reconnect the work account.
5. Test:
   • Sign back into Edge with the work account and test SharePoint in both normal and InPrivate modes.

Optional: Policy Check

• Verify the BrowserSignin policy is active for Edge and there are no conflicting Intune policies for cookies or SSO.

If the problem continues after the steps above, there may be a WAM/SSO bug in the latest Chromium build. Report this to Microsoft, including logs from dsregcmd /status and Azure AD sign-in error information.

Thanks for clarifying that, it’s an important detail. If the same user fails even in InPrivate on their own device, but another user works fine on that same device (even in InPrivate), then this is not a browser cache issue. It’s something tied to the user’s identity tokens or device registration in Azure AD rather than the local profile.

Here’s what that tells us:

• The problem follows the user, not the device.
• Wiping the device didn’t help, so the corruption is likely in the cloud identity layer (Azure AD / WAM tokens) or Conditional Access session state.
• InPrivate working for a different user confirms the browser itself is fine.

Next steps:

1. Check the affected user’s Azure AD sign-in logs for SharePoint. Look for conditional access failures or token issuance errors.
2. Verify the user’s Primary Refresh Token (PRT) status with dsregcmd /status on their device. If PRT is missing or invalid, SSO will fail.
3. Try revoking all sessions for the affected user in Azure AD and force reauthentication.
4. If that doesn’t help, remove the user’s device registration from Azure AD and rejoin it.

This feels like a PRT or WAM token issue triggered by the Edge update, but persisting because the user’s cloud session state is broken.