Azure access blocked after Microsoft for Startups activation (AADSTS5000225 – tenant blocked)

Hi Jonathan,

Thank you for the detailed and thoughtful response — it’s been incredibly valuable in understanding what’s actually happening behind the scenes.

Unfortunately, I haven’t been able to resolve the issue yet. I’ve tried the suggested approaches, and everything still points to a tenant/subscription provisioning problem. I’ve escalated it through support and other channels, so now I’m waiting for Microsoft to take action on their side.

Really appreciate you taking the time to break this down so clearly. I’ll definitely be following you — this level of insight is rare and extremely helpful.

Thanks again!

Hello, Jesus. Congratulations on being accepted into the Microsoft for Startups program through Dell; that is a massive milestone for any founder. It is incredibly frustrating to have $100,000 in credits waiting for you while the "digital door" remains locked.

The error AADSTS5000225 is a specific Microsoft Entra (formerly Azure AD) lifecycle issue. It means the tenant you are trying to access has been inactive for more than 200 days and has been placed in a "blocked" state prior to permanent deletion.

Since you cannot access the portal to open a ticket, here is your tactical roadmap to resolve this:

1. The "Specific Directory" Workaround

Often, the Azure portal defaults to your oldest or "home" tenant. If your credits were provisioned to a different, active tenant, you might be hitting the blocked one by mistake.

• Action: Open a private/incognito window and use this specific URL format: [https://portal.azure.com/your-startup-domain.onmicrosoft.com](https://portal.azure.com/your-startup-domain.onmicrosoft.com)

If you have the Tenant ID (the long GUID), use: [https://portal.azure.com/](https://portal.azure.com/)<Tenant-ID>

2. The 20-Day Critical Window

Once a tenant hits the AADSTS5000225 state, you have a 20-day grace period to request reactivation before the tenant and all associated data are purged forever.

Action: Check the timestamp on your error screen. If it appeared recently, you must act fast.

3. Contacting Support Without Portal Access

Since you are blocked from the standard support dashboard, you need to bypass it using these channels:

Global Customer Service: Call the Microsoft support number for your region. Ask to be transferred to the "Data Protection Team" or "Subscription Management."

Required Info: Have the Trace ID and Correlation ID (from the error screen) ready. Tell the agent: "My tenant is blocked due to inactivity (AADSTS5000225) and I need a manual reactivation to access my Founders Hub benefits."

Social Media: Sometimes tweeting at @AzureSupport with your Correlation ID can escalate the ticket faster than the standard Founders Hub email thread.

4. The "Account Wake-up" Force

If this is a bug where a new tenant is showing as "inactive," some users have successfully forced a status update by:

Going to [https://signup.azure.com](https://signup.azure.com) in incognito mode.

Attempting to "Sign Up" with the same email. Sometimes the system recognizes the existing account and triggers a "Reactivate" or "Upgrade" flow that wakes up the identity service.

Technical Context: It appears the Microsoft for Startups provisioning system automatically attached your $100k subscription to an old, dormant tenant linked to your identity. The Founders Hub support team sees the "Subscription" as active, but they often don't have the permissions to unblock a "Tenant" (Identity layer). You need the Identity/Global Admin support to flip the switch on the tenant itself.

Good luck getting your infrastructure live—those credits are a game-changer once you're in!