Completely locked out of Azure portal (AADSTS16000, 'Microsoft Services' tenant) – cannot even create a support ticket, chat support keeps sending broken link

Burak TÜRK 0 Reputation points
2026-08-11T07:43:46.3+00:00

Title: Completely locked out of Azure portal (AADSTS16000, 'Microsoft Services' tenant) – cannot even create a support ticket, chat support keeps sending broken link

Body:

I'm fully locked out of the Azure portal with a personal Microsoft account (hotmail.com.tr address, identity provider live.com). Every blade I open (Resource Manager, Help + Support, creating a new subscription) fails, always resolving into the default "Microsoft Services" tenant (f8cdef31-a31e-4b4a-93e4-5f571e91255a). This is not a one-time glitch — it has happened consistently across three separate occasions and two different portal extensions:

Occurrence 1 (Azure Portal itself, ADIbizaUX):

"interaction_required: AADSTS16000: User account does not exist in tenant 'Microsoft Services' and cannot access the application '74658136-14ec-4630-ad9b-26e160ff0fc6'(ADIbizaUX)"

Trace ID: e8cd4a3b-ec34-493d-a5b2-d9b65df30000 | Correlation ID: e0e69cb7-7a28-42a3-a436-e7fef09c312a | Timestamp: 2026-08-11 06:29:59Z

Occurrence 2 (Help + Support blade, Microsoft_Azure_SupportPortalExtension):

Same error, application 'e6694c91-1590-4e35-9bb7-b865c638b9c1'

Trace ID: 6fe01add-32f4-4285-bc8d-9000dcb0100 | Correlation ID: b506ae9c-e257-4528-8b52-c55bc6e31a23 | Timestamp: 2026-08-11 07:18:39Z

Occurrence 3 (Help + Support blade again, a few minutes later):

Same error, same application

Trace ID: e04f755a-759f-4d9f-be68-2eeff74a1c00 | Correlation ID: d37425d2-a905-48e2-bb12-1b0bc589d950 | Timestamp: 2026-08-11 07:33:15Z

I additionally get a separate error in Resource Manager: "Token validation failed. A passthrough token was detected without proper resource provider context" (Code: PassthroughTokenValidationFailed, request correlation identifier 6341a04a-a94c-48e4-8722-604aff94e73a).

What I've already tried (all failed with the same result):

  • Signing out completely and retrying in a fresh incognito/private window
  • Using a completely different browser and device
  • Trying the tenant-specific URL format (portal.azure.com/<tenant>.onmicrosoft.com)
  • Starting a new Azure Free Trial on this same account (blocked separately because an old, closed credit card is stuck on the billing profile and cannot be removed via self-service)
  • Contacting Microsoft consumer support chat twice, who both times sent me back to portal.azure.com, which fails with the exact same error shown above

Please do NOT reply with the standard "open an incognito window and sign in again" or "go to Help + Support and create a ticket" suggestions — I have already documented above, with trace IDs, that both of those specifically fail for this account. I'm not asking how to use the portal; I'm reporting that the portal itself will not let this account in anywhere, including the ticket-creation page. What I need is someone with backend access to Microsoft Entra ID / tenant provisioning to actually look at this account.

Could someone with backend access please help:

  1. Resolve why this account is permanently routed into the 'Microsoft Services' tenant instead of being allowed to create/access its own directory, and
  2. Remove the old, closed credit card stuck on the account's billing profile so I can complete free trial signup as a fallback if needed.

I'd rather not post my account email publicly on an open forum to avoid spam/phishing — if a moderator with the ability to actually investigate this picks it up, I'm happy to share the exact account email and any further diagnostic details privately (e.g. via forum private message).

This is currently blocking me from using Azure and Microsoft Fabric for my professional data engineering work. Any help is greatly appreciated.

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.