Try to sign in for ""Data encryption"" but cannot

Question

Correlation Id: 012bbbbca711000203c7540211a7dc01

Timestamp: 2026-03-01T09:28:08.052Z

Answer 1

The correlation ID and timestamp alone are not enough to determine why the “Data encryption” sign-in failed. Correlation IDs are diagnostic identifiers that must be looked up in service logs by a support or admin team.

Use the following steps depending on the scenario:

1. If this is a Microsoft 365 / Entra / Authenticator sign-in
   • Treat this as a sign-in failure to a Microsoft cloud service.
   • Capture the full error message shown on screen, including any error code (for example, AADSTS… or numeric HR code).
   • If the error appears on a login.microsoftonline.com page with “Sorry, but we’re having trouble signing you in”, view the page source and search for HR= to extract the numeric error code, then contact Microsoft technical support with:
     • The error code from HR=
     • The correlation ID: 012bbbbca711000203c7540211a7dc01
     • The timestamp: 2026-03-01T09:28:08.052Z
   • Open a support case through your Microsoft 365 or Azure portal so support can look up that correlation ID in backend logs and tell you the exact cause.
2. If this is related to Microsoft Graph Data Connect “Data encryption”
   • “Data encryption” in this context is configured and approved by an admin in the Microsoft 365 admin center for Microsoft Graph Data Connect apps.
   • Ensure an admin signs in to the Microsoft 365 admin authorization portal and reviews the Data Connect app:
     • Go to Org settings → Security & Privacy → Microsoft Graph Data Connect applications.
     • Select the app and verify that encryption is enabled and the datasets are eligible.
     • Complete the Review step and choose Approve so encryption is actually applied.
   • If the admin cannot sign in at all (for example, blocked by MFA or other sign-in errors), the admin must contact Microsoft support (or the Microsoft Data Protection team via a support ticket) and provide the correlation ID and timestamp so they can investigate and restore access.
3. If this is a SharePoint/OneDrive/Outlook web action
   • A correlation ID is not an error code; it is a GUID used only for tracing in logs.
   • Provide the correlation ID and timestamp to the tenant admin or helpdesk.
   • The admin should search Unified Logging System (ULS) or service logs for that correlation ID at the given time to see the underlying error and then remediate based on what the logs show.

In all cases, resolving this requires either:

• Extracting the actual error code from the sign-in page (if available) and following the documented troubleshooting for that code, or
• Opening a support request with Microsoft and supplying the correlation ID and timestamp so support can look up the failure in backend logs.

---

References:

• "Sorry, but we're having trouble signing you in" when a user signs in to Microsoft 365, Azure, or Intune
• SharePoint Correlation ID in error messages: what it is and how to use it
• Use encryption with Microsoft Graph Data Connect