Unable to access Azure or Azure Support

Question

When trying to access potal.azure.com I receive this error:

Sign-in failed

Error code: AADSTS5000225

The tenant 'Default Directory (17e197e7-99b2-417b-9a49-f5e48c27e579)' has been deauthenticated and is no longer available. Try signing into another tenant from the dropdown below. Error message: 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: cea97159-3e53-49a7-b87f-499809781d00 Correlation ID: 019f244b-1e51-7cc8-8f21-5e6564cfe0d4 Timestamp: 2026-07-02 19:25:30Z

**When trying to access Azure Support with another email, I receive the following error (with buttons "Sign In Again" and "Ignore"), both giving me the error again immediately:

**Interaction required

The portal encountered an issue while attempting to retrieve access tokens. We suggest attempting to sign in again, or alternatively, continuing without access tokens, although this may result in a suboptimal user experience. Additional details: login_required: AADSTS50058: A silent sign-in request was sent but no user is signed in. The cookies used to represent the user's session were not sent in the request to Azure AD. This can happen if the user is using Internet Explorer or Edge, and the web app sending the silent sign-in request is in different IE security zone than the Azure AD endpoint (login.microsoftonline.com). Trace ID: 93da3f2c-d76b-4221-a33d-29b9fc3a1100 Correlation ID: 1a3097d0-60a6-44b9-9773-35e5455ac0e0 Timestamp: 2026-07-02 19:26:48Z. Learn more

Click here to copy details

---

This makes me completely unable to request support and the generic Microsoft support was unable to assist, saying it was an Azure issue.

Thanks for any suggestions.

Answer 1

Hello Emil,

Greetings! Thanks for raising this question in the Q&A forum.

The first error, AADSTS5000225, means your Azure tenant has been automatically blocked by Microsoft's tenant lifecycle policy after being flagged as inactive. This is why you also can't reach Azure Support through the portal, since the support blade itself needs to authenticate against that same blocked tenant, which is what's causing the second "Interaction required" token error. Both errors trace back to the same root cause. The good news is that based on your timestamp of 2026-07-02, you're well within the 20-day reactivation window, since tenants in this state are only permanently deleted after 20 days.

1. Try signing in with your Global Administrator account specifically, if you have one separate from the account that hit this error, at

https://portal.azure.com

or

https://admin.microsoft.com

In some cases a standard user is blocked while the original Global Admin account that created the tenant can still get in. If you get in, check

Billing > Subscriptions

for any subscription showing as Expired or Disabled, and reactivate it, since reactivating a subscription can automatically lift the tenant block.

If you cannot sign in at all, this must be resolved by phone, not the portal, since the portal-based support request flow requires the same authentication that's currently blocked. Call Microsoft Support using the number for your country or region at Customer service phone numbers, select the option for Azure or "Can't sign in," and explain that your tenant is blocked with AADSTS5000225 due to inactivity and that this is also preventing you from opening a support case through the portal.

Have these details ready when you call, since support will need them to locate and reactivate your specific tenant:

Tenant: Default Directory (17e197e7-99b2-417b-9a49-f5e48c27e579)
Trace ID: cea97159-3e53-49a7-b87f-499809781d00
Correlation ID: 019f244b-1e51-7cc8-8f21-5e6564cfe0d4
Timestamp: 2026-07-02 19:25:30Z

Do not open multiple parallel support requests for the same tenant, since duplicate cases are tracked and can slow down processing rather than speed it up.

Once reactivated, sign in periodically going forward, since tenants that go extended periods without any sign-in activity are what triggers this lifecycle block in the first place.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.