Use the same device and network used to provision the sandbox once; if error 53003 remains and this is the tenant’s only administrator, open a Microsoft Support tenant-lockout case rather than deleting the sandbox.
Recover the existing sandbox
- Retry from the original provisioning environment
- Use the device, browser profile, and network from which the E5 sandbox was created.
- Sign in with the sandbox administrator shown on the Developer Program dashboard—not the Microsoft account used to join the Developer Program.
- This is the resolution recommended for the closely matching scenario of a newly provisioned E5 sandbox whose sole administrator receives AADSTS53003 during first-time sign-in.^1^
- If it still fails, record the complete error details
Expand More details on the 53003 page and save:
- Error code
- Request ID
- Correlation ID
- Timestamp, including time zone
- Application/resource name
- Screenshot with passwords and authentication codes removed
AADSTS53003 specifically means BlockedByConditionalAccess: a Conditional Access decision prevented token issuance.^2^
- Contact Microsoft Support as a tenant lockout
Because the admin center is also blocked and no second administrator is available, use Microsoft’s customer-service phone route and state:
A newly provisioned Microsoft 365 Developer Program E5 sandbox returns AADSTS53003 on the first administrator sign-in. The affected account is the tenant’s only Global Administrator, so the Microsoft 365 and Entra admin centers are inaccessible. A tenant-lockout recovery case is required.
Provide the sandbox domain, administrator ID, correlation ID, request ID, and timestamp—but not the password or MFA codes. Microsoft’s tenant-recovery guidance says to call support when portals are inaccessible; after ownership verification, Microsoft can help the designated Global Administrator regain access to the existing tenant.^3^
If another Microsoft 365 tenant is available where you are an administrator, its admin center can also be used to create a request through Help & support → Contact Support, identifying the locked sandbox as the affected tenant.^4^
Why the policy cannot be checked directly
Normally, an administrator would inspect:
Microsoft Entra admin center → Entra ID → Monitoring & health → Sign-in logs → affected event → Conditional Access
The event identifies the policy and conditions that blocked the request. That requires access to the tenant with at least the Reports Reader role, so it is unavailable while the only administrator is locked out.^5^
Deleting and recreating the sandbox
Deletion is possible, but it is not the fastest recovery path:
- Sign in to the Microsoft 365 Developer Program dashboard using the member account originally used to join the program.
- Select Delete Profile.
- Re-enroll and provision a new subscription only if still eligible.
Microsoft permits only one Developer Program subscription per membership. More importantly, after deleting the profile, a replacement subscription is available only after the existing subscription has been held for more than 60 days.^6^
Therefore, if this sandbox is newly created, deleting it could leave you unable to provision a replacement immediately. Support recovery should be attempted first.
References
- Tenant appears to be a Conditional Access lockout of the sole administrator account. - Microsoft Q&A
- Microsoft Entra authentication and authorization error codes
- Plan for tenant recoverability
- Get support for Microsoft 365 for business
- Troubleshoot sign-in problems with Conditional Access
- Microsoft 365 Developer Program FAQ