SharePoint Online browser sign-in fails (“Something went wrong”, Unknown issue) with CBA + Conditional Access

Nguyen Thi Thu Thuy 0 Reputation points
2026-11-19T06:46:34.2+00:00

Description:

We are implementing certificate-based authentication (CBA) with Microsoft Entra ID and a Conditional Access policy. Device certificates are provisioned through ManageEngine MDM (SCEP).

Issue: When a CBA-enrolled user opens SharePoint Online in a browser, sign-in fails with “Something went wrong. We’re sorry, sign-in isn’t working right now.” Issue Type: Unknown issue.

Questions:

  1. What is the root cause of this SharePoint Online sign-in failure? Please review the backend logs for the Correlation ID above.
  2. Is there a CBA / Conditional Access / authentication strength setting that could block browser sign-in to SharePoint Online while mobile works?
  3. What do we need to configure so browser sign-in with CBA to SharePoint Online works?

User's image

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-19T06:48:16.71+00:00

    The displayed SharePoint correlation ID does not establish a CBA or Conditional Access root cause; reproduce the failure, correlate it with Microsoft Entra sign-in logs, and apply the remediation indicated by that event.

    The screenshot’s 11/11/2026 event is outside the Sign-in Diagnostic’s 48-hour search window. Also, a SharePoint correlation ID traces a SharePoint request and is not necessarily the same identifier as an Entra authentication correlationId or requestId.^1^

    Capture and identify a new failure

    1. Reproduce the issue in a new browser session.
    2. Record:
      • Exact date, time, and time zone.
      • Affected user and SharePoint URL.
      • Browser and operating system.
      • New SharePoint correlation ID.
      • Any Entra request ID, correlation ID, and error code shown under More details.
    3. As at least Reports Reader, open: Microsoft Entra admin center → Entra ID → Monitoring & health → Sign-in logs.
    4. Search first by the user, precise timestamp, Resource, and browser client. Use an Entra correlation ID only if it came from the authentication error details or matching sign-in event.
    5. Open the event and inspect:
      • Status and error code
      • Authentication Details
      • Conditional Access
      • Device Info
      • Resource/Audience
      • Troubleshooting and support

    The Conditional Access tab identifies each applied policy and whether it succeeded or failed; selecting the policy shows its assignments and grant controls.^2^

    For a fresh event, launch Sign-in diagnostic from the event, or use Diagnose & solve problems → Sign-in Diagnostic and search within 48 hours.^3^

    If Conditional Access or authentication strength failed

    Yes, policy configuration can permit a mobile flow while blocking a browser. Conditional Access evaluates controls such as authentication strength, compliant device, approved client app, and app-protection policy; multiple selected controls require all controls by default.^4^

    Check the matching event:

    1. Under Authentication Details, read Requirement to identify the enforced authentication strength.
    2. Under Conditional Access, select the failed policy and inspect Grant Controls.^5^
    3. If a custom strength requires CBA:
      • Confirm it permits the certificate’s protection level: x509CertificateSingleFactor or x509CertificateMultiFactor.
      • If advanced options are configured, ensure the certificate matches an allowed issuer and policy OID. When both are configured, both must match.
      • Ensure the CBA authentication binding policy classifies that issuer/OID at the protection level required by the policy.^6^
    4. If the log instead reports device compliance, hybrid join, approved-app, or app-protection failure, change that specific policy assignment or satisfy that control. Do not weaken the CBA strength unless the log shows it is the failed requirement.

    If certificate authentication failed

    Test core CBA independently in the same browser by signing into MyApps, selecting Sign in with a certificate, and choosing the intended certificate. A successful test validates certificate provisioning, trusted-CA configuration, and username binding; it does not validate SharePoint-specific Conditional Access, audience, device, or session controls.^7^

    Apply the matching remediation:

    • AADSTS50017: Upload the complete root and intermediate CA chain to the Entra trust store, and verify that the user certificate’s AKI matches the issuing CA’s SKI. Also validate required certificate policy extensions and OIDs.^8^
    • CRL error: Ensure the configured CRL endpoint is publicly reachable, current, correctly signed, and associated with the correct CA. If configured, an unavailable or expired CRL can block CBA.^9^
    • No certificate prompt or TLS failure: Permit the sign-in endpoint and *.certauth.login.microsoftonline.com, and disable TLS inspection for the certificate-authentication endpoint because CBA requests the client certificate during mutual TLS.^10^
    • Wrong certificate cached in Edge: Select the lock icon → Your certificate choices → Reset certificate choices, then select Other ways to sign in → Use a certificate or smart card. Browsers cache one certificate for the session.

    Browser/platform support

    Desktop CBA is supported in Edge and Chrome on Windows and macOS. Mobile support differs: on iOS, on-device CBA is supported in Safari but not ordinary Chrome or Edge browser sessions; Android supports on-device certificates in Chrome but not Edge. A successful mobile-app sign-in therefore does not prove that the desktop browser followed the same authentication path.^11^

    If the matching Entra event is successful—or no authentication failure exists at the same time—do not change CBA or Conditional Access based solely on this page. Open a Microsoft 365 support case and provide the fresh SharePoint correlation ID, exact timestamp/time zone, affected URL, user, and matching Entra event details so Microsoft can trace SharePoint Online’s service-side logs.


    References

    1. SharePoint Correlation ID in error messages: what it is and how to use it | Microsoft Support
    2. Troubleshoot sign-in problems with Conditional Access
    3. What is the Sign-in diagnostic in Microsoft Entra ID?
    4. Build a Conditional Access policy
    5. Troubleshoot Conditional Access authentication strengths
    6. Create and manage custom Conditional Access authentication strengths
    7. Set up Microsoft Entra certificate-based authentication
    8. Error AADSTS50017 - Validation of given certificate for certificate-based authentication failed
    9. Microsoft Entra certificate-based authentication Certificate Revocation List (CRL)
    10. Microsoft Entra certificate-based authentication technical concepts
    11. Limitations with Microsoft Entra certificate-based authentication
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.