Cannot Access E5 Sandbox 53003 Error Code

Nicole Daffe 5 Reputation points
2026-11-19T16:12:43.35+00:00

I have set up an E5 Sandbox through the Microsoft 365 Developer program. On the Dashboard it is showing that everything is correct and working but whenever I click on the Go to your E5 Sandbox link, I sign in using the newly created tenant administrator account but I keep getting a 53003 error code. I initially tried to access the Microsoft 365 Admin Center (admin.microsoft.com) to finish setting up the account but still received this error. Is there anyway I can delete this Sandbox and create a new one? Or get this error resolved?

Microsoft 365 and Office | Development | Microsoft 365 Developer Program
0 comments No comments

2 answers

Sort by: Most helpful
  1. Lin V 2,135 Reputation points Independent Advisor
    2026-11-19T16:37:23.39+00:00

    Hi Nicole,

    Before we go further, I would like to mention that I am also a user like you, so I can share some suggestions based on the available information, but I do not have access to your sandbox tenant from this forum.

    As a first step, you could try opening an InPrivate/Incognito browser window and go directly to Microsfot 365 admin center.

    When signing in, make sure you use the new tenant administrator account created for your E5 developer sandbox. The sandbox is a separate tenant with its own administrator account, which may look something like ******@yourtenant.onmicrosoft.com.

    If you still receive error 53003 with that account and cannot access the Microsfot 365 admin center. I would suggest contacting Microsoft Support, since the affected account is the administrator of the sandbox tenant itself and the sign-in block may need to be investigated from Microsoft's side.

    To contact support, please call using the phone number listed for your country or region here: Contact Microsoft customer support.

    I hope the information provided will help guide you in the right direction.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-19T16:13:45.9366667+00:00

    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

    1. 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^
    2. 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^
    3. 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:

    1. Sign in to the Microsoft 365 Developer Program dashboard using the member account originally used to join the program.
    2. Select Delete Profile.
    3. 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

    1. Tenant appears to be a Conditional Access lockout of the sole administrator account. - Microsoft Q&A
    2. Microsoft Entra authentication and authorization error codes
    3. Plan for tenant recoverability
    4. Get support for Microsoft 365 for business
    5. Troubleshoot sign-in problems with Conditional Access
    6. Microsoft 365 Developer Program FAQ
    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.