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
- 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.
- 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:
- Open Microsoft Entra admin center → Entra ID → Monitoring & health → Sign-in logs.
- Find the failed event using the correlation ID, username, and timestamp.
- Open the event and select the Conditional Access tab.
- Identify the policy producing the failure.
- 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
- Tenant appears to be a Conditional Access lockout of the sole administrator account. - Microsoft Q&A
- Set up a Microsoft 365 developer sandbox subscription
- Troubleshoot sign-in problems with Conditional Access
- Contact Microsoft customer support
- Microsoft 365 Developer Program FAQ