Unable to login - After subscription is created

Question

Unable to login - After subscription is created

Boggarapu Sahithi 0

Hello, I have taken a free trial subscription. after creation i am not able to login to Azure portal. the error message is : Sign-in failed Error code: interaction_required Error message: interaction_required: interaction_required: AADSTS5000225: This tenant has been blocked due to inactivity. To learn more about tenant lifecycle policies, see https://aka.ms/TenantLifecycle Trace ID: dc70f0e8-fa38-4bf3-9023-b24773303100 Correlation ID: 019ba61d-7767-772d-b0e4-a45d6220d275 Timestamp: 2026-01-10 04:15:07Z Learn more abo

Shubham Sharma 17,930 Reputation points Microsoft External Staff Moderator

2026-01-12T02:05:17.22+00:00
Boggarapu Sahithi

Thank you for reaching out to Microsoft Q&A.

The error message you encountered indicates that your tenant has been inactive for over 200 days past the billing cycle, triggering Microsoft’s effort to remove inactive tenants. When a tenant remains inactive for this period, the OMS commerce system imposes a login block (AADSTS5000225). Twenty days after the login block is applied, the tenant is permanently deleted.

Tenant inaccessible due to inactivity

If you plan to unblock your inactive tenant, it’s essential that it has been blocked for less than 20 days. After the 20-day period, the tenant is permanently deleted and cannot be recovered.

If it has been less than 20 days since the block, please provide the following details for further assistance via private message:

Tenant ID

Correlation ID from the login failure

Timestamp of the failure

Subscription ID

Contact phone number (add +Country code)

Contact email address

Email address (affected account)

Country

TimeZone
Shubham Sharma 17,930 Reputation points Microsoft External Staff Moderator

2026-02-25T13:04:12.4266667+00:00

Hello Boggarapu

Following up to check if the resolution provided above was helpful. Please let us know if you need any further assistance.

1 answer

Your answer

Shubham Sharma 17,930 Reputation points Microsoft External Staff Moderator

2026-01-12T02:05:17.22+00:00

Boggarapu Sahithi

Thank you for reaching out to Microsoft Q&A.

The error message you encountered indicates that your tenant has been inactive for over 200 days past the billing cycle, triggering Microsoft’s effort to remove inactive tenants. When a tenant remains inactive for this period, the OMS commerce system imposes a login block (AADSTS5000225). Twenty days after the login block is applied, the tenant is permanently deleted.

Tenant inaccessible due to inactivity

If you plan to unblock your inactive tenant, it’s essential that it has been blocked for less than 20 days. After the 20-day period, the tenant is permanently deleted and cannot be recovered.

If it has been less than 20 days since the block, please provide the following details for further assistance via private message:

Tenant ID

Correlation ID from the login failure

Timestamp of the failure

Subscription ID

Contact phone number (add +Country code)

Contact email address

Email address (affected account)

Country

TimeZone
Shubham Sharma 17,930 Reputation points Microsoft External Staff Moderator

2026-02-25T13:04:12.4266667+00:00

Hello Boggarapu

Following up to check if the resolution provided above was helpful. Please let us know if you need any further assistance.

Answer 1

The error message you are encountering indicates that the tenant associated with your Azure subscription has been blocked due to inactivity. This can happen if the tenant has not been used for a certain period of time. To resolve this issue, you may need to check the tenant lifecycle policies as suggested in the error message.

You can try the following steps:

Review the tenant lifecycle policies provided in the link mentioned in the error message to understand the inactivity criteria.
If necessary, contact Azure support for assistance in unblocking your tenant or to get more information about your specific situation.

For further troubleshooting related to sign-in issues, you might find it helpful to consult additional Azure documentation or support resources.

References: