Provisioned a new E5 Add-ons enabled sandbox but unable to log in

Ron Giordano 0 Reputation points
2026-11-17T13:36:18.3433333+00:00

Provisioned a new E5 Add-ons enabled sandbox but unable to log in. Seems to be a provisioning error

When logging in for the very first time after provisioning it states the following:

Let's keep your account secure We'll help you set up another way to verify it's you.

and when clicking next i get

and when i click next i get this message

You cannot access this right now Your sign-in was successful but does not meet the criteria to access this resource. For example, you might be signing in from a browser, app, or location that is restricted by your admin.

I tried resetting the password which was successful but still get the same error upon login. Tried multiple browsers, incognito mode, all return the same error above.

Can I get the tenant reprovisioned or deleted and recreated?

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

3 answers

Sort by: Oldest
  1. AI answer

    2026-11-17T13:37:32.24+00:00

    Sign in with the sandbox administrator account from the same device and network used to provision the tenant; if that still fails, recover the Conditional Access lockout through another administrator or Microsoft Support rather than deleting the sandbox.

    This exact first-sign-in sequence has been reported for a newly provisioned Microsoft 365 Developer Program E5 sandbox, including the security-registration prompt followed by “Your sign-in was successful but does not meet the criteria.” The accepted recovery path starts with the original provisioning device and network.^1^

    Recovery steps

    1. Use the sandbox administrator identity
      • On the Developer Program dashboard, note the administrator shown for the subscription.
      • Sign in with that [Email] account—not the personal, work, or Visual Studio account used to join the Developer Program. Microsoft documents these as separate credentials.^2^
      • Use the same device and network from which the sandbox was provisioned.
    2. Capture the failure details
      • On the error page, select More details.
      • Record the error code, request ID, correlation ID, timestamp, application/resource, and tenant domain.
      • If the code is AADSTS53003, Microsoft defines it as BlockedByConditionalAccess.^3^

    Password resets, different browsers, and private browsing do not need to be repeated; those attempts do not alter the access criteria evaluated after authentication.

    If another administrator can sign in

    Have that administrator:

    1. Open Microsoft Entra admin center → Entra ID → Monitoring & health → Sign-in logs.
    2. Find the failed event using the correlation ID, username, and timestamp.
    3. Open the event and select the Conditional Access tab.
    4. Identify the policy producing the failure.
    5. Disable only that identified policy, then retry security-information registration.

    Microsoft’s lockout guidance explicitly permits an unaffected administrator to disable the policy blocking sign-in.^3^ Avoid making broad changes to unrelated policies.

    If this is the only administrator

    Contact Microsoft Support and request investigation and recovery of a sole-administrator Conditional Access lockout. Support can review the blocking policy after validating tenant ownership; ask Support to determine whether tenant recovery is possible and whether reprovisioning is required rather than requesting reprovisioning as the assumed fix.^3^

    Use the Microsoft 365 business support number for your country or region.^4^ Provide:

    • Tenant’s onmicrosoft.com domain
    • Sandbox administrator username, with unnecessary personal information removed
    • Exact error code
    • Request ID and correlation ID
    • UTC timestamp
    • Confirmation that this occurs during first-time security registration
    • Confirmation that no other administrator can access the tenant, if applicable
    • Confirmation that password reset and browser isolation have already been tested

    Deleting and recreating the sandbox

    Deletion should be the last resort:

    • Developer Program membership provides only one developer subscription.
    • Creating a replacement requires deleting the Developer Program account and setting up a new one.
    • Microsoft states that a new subscription can be obtained only after the existing subscription has been held for more than 60 days.
    • Delete Profile erases the profile and any unbacked-up developer-subscription data.^5^

    Therefore, deleting this newly provisioned profile might leave the account unable to create another sandbox immediately. Also, the Power Platform Reset environment command is not a reset of the Microsoft 365 Developer Program tenant and will not resolve this tenant-level sign-in lockout.


    References

    1. Tenant appears to be a Conditional Access lockout of the sole administrator account. - Microsoft Q&A
    2. Set up a Microsoft 365 developer sandbox subscription
    3. Troubleshoot sign-in problems with Conditional Access
    4. Contact Microsoft customer support
    5. Microsoft 365 Developer Program FAQ
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. BabybooHN 4,310 Reputation points Independent Advisor
    2026-11-17T13:41:48.84+00:00

    Dear @Ron Giordano

    The message indicates that your password was accepted, but an access requirement is blocking the next step of security registration. It does not, by itself, confirm a provisioning error. Microsoft recommends checking the error details and Entra sign-in logs to identify the restriction.

    I recommend these checks before deleting the sandbox:

    1. Confirm you are signing in with the sandbox administrator account created during provisioning, usually @yourtenant.onmicrosoft.com, rather than the account used to join the Developer Program.
    2. On the error page, select More details and record the error code, Request ID, Correlation ID and timestamp.
    3. If another sandbox administrator can sign in, ask them to check Entra ID > Monitoring & health > Sign-in logs, including the Conditional Access and Authentication Details tabs for that attempt.

    I would avoid deleting your Developer Program profile as a troubleshooting step. Microsoft documents restrictions on obtaining another subscription after profile deletion, so immediate recreation is not guaranteed. Please refer to this document: Microsoft 365 Developer Program FAQ

    I cannot reprovision the tenant through this forum. Could you share the error code, confirm whether this is the only administrator, and let me know whether the Developer Program dashboard shows provisioning as completed? Please hide personal information in screenshots.

    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.