A cloud-based identity and access management service for securing user authentication and resource access
The error AADSTS5000225 with message “This tenant has been blocked due to inactivity” indicates the tenant has entered an inactive state and has been blocked from sign-in.
Key points from the documented behavior:
- Tenants blocked due to inactivity show the AADSTS5000225 error when trying to access Microsoft Entra ID or Azure resources.
- Administrators can request reactivation only within 20 days of the tenant entering this inactive state.
- After 20 days in this blocked state, the tenant is deleted and can’t be recovered.
To attempt reactivation (only possible if the tenant has been blocked for less than 20 days):
- As the tenant administrator/owner, contact Microsoft support using the global support phone numbers: see the “global support phone numbers” link in the tenant inactivity article.
- Provide the tenant’s domain or tenant ID and explain that the tenant is blocked due to inactivity (AADSTS5000225) and needs reactivation.
- Don’t submit multiple support requests for the same issue; wait for the decision on the initial case.
If the tenant has been blocked for more than 20 days:
- The tenant is deleted and can’t be restored. In that case, the only option is to create a new tenant and configure resources again.
If access to the portal UI is blocked but the tenant is still within the recoverable window, support is the only documented path to regain access; there’s no self-service reactivation flow once the tenant is in this inactive/blocked state.
References:
- Tenant inaccessible due to inactivity
- Discover your Microsoft cloud footprint FAQ
- 7 Day Old Azure Account: AADSTS5000225: This tenant has been blocked due to inactivity. - Microsoft Q&A
- Error message: AADSTS5000225: This tenant has been blocked due to inactivity. - Microsoft Q&A
- Error message: interaction_required: AADSTS5000225: This tenant has been blocked due to inactivity - Microsoft Q&A
- Tenant inaccessible due to inactivity - Microsoft Q&A