Error Code: 53003

Question

Error Code: 53003

Request Id: 5dba4275-3a8c-493e-9ecc-ddbf3d818e00

Correlation Id: 019cadcb-401b-7a7c-9b1b-57d848130bbc

Timestamp: 2026-03-02T09:05:11.026Z

App: Azure Portal

I enabled conditional access and set up a block access policy. Now I can't login to any websites like Microsoft and Azure. They all show error code 53003. I can't log in to Azure to delete this policy.

At the same time, I only have this one administrator account.

I'm using the Support for business, but it asks me to log in as an enterprise user. I can't login with this user, and it's stuck in a loop.

How can I solve this problem? Please help me. Thank you.

Answer 1

Error code AADSTS53003 means sign-in is being blocked by a Conditional Access policy. Because a tenant-wide block policy was enabled and there is only one administrator account, that account is now also blocked and cannot reach the Azure or Microsoft 365 portals to change the policy.

In this situation, the policy cannot be fixed from the portal by the locked-out admin and must be corrected by Microsoft support after verifying tenant ownership.

Actions to take:

1. Gather sign-in details
   • Keep the information from the error page, including:
     • Error code: AADSTS53003
     • Request Id: 5dba4275-3a8c-493e-9ecc-ddbf3d818e00
     • Correlation Id: 019cadcb-401b-7a7c-9b1b-57d848130bbc
     • Timestamp: 2026-03-02T09:05:11.026Z
   • These values help Microsoft support locate the exact failed sign-in event.
2. Open a support case with Microsoft
   • Because no admin can sign in, use an external support channel for business products (for example, the Microsoft 365/Azure business support contact for the region) and request escalation to the Data Protection / Tenant Recovery team.
   • Clearly state that:
     • Conditional Access was configured with a tenant-wide block policy.
     • There is only one administrator account.
     • That account is now blocked by error AADSTS53003 and cannot access the Entra or Azure portals.
   • Provide the Request Id, Correlation Id, and Timestamp so support can confirm the lockout and adjust the Conditional Access policy on the backend.
3. If any other admin exists
   • If it is later discovered that another global admin account exists that is not blocked, that admin can:
     1. Sign in to the Microsoft Entra admin center.
     2. Go to Entra ID > Enterprise apps > Conditional Access.
     3. Locate the blocking policy and set Enable policy to No, then Save.
     4. Confirm that sign-in for the original admin works again.
4. After access is restored
   • Sign in and review Conditional Access configuration:
     • Avoid “Block access” policies that apply to all users and all cloud apps without exclusions, as this can lock out the entire tenant.
     • Create and document at least one emergency access (break-glass) account that is excluded from restrictive Conditional Access policies to prevent future lockouts.

Until Microsoft support or an unblocked admin disables or adjusts the blocking Conditional Access policy, sign-in will continue to fail with error 53003.

---

References:

• Troubleshoot sign-in problems with Conditional Access
• Problems signing in to a Microsoft application
• Troubleshoot sign-in issues and account access problems