An Azure service that provides fine-grained access management for Azure resources, enabling you to grant users only the rights they need to perform their jobs.
Hello Jim Xu,
Thanks for raising this question in the Q&A forum.
The error AADSTS5000224 means the Microsoft Entra ID (Azure AD) tenant your Visual Studio Azure subscription is linked to, named "Default Directory" with tenant ID bfaf4860-b959-420d-bd98-5dca0ab05001, has been deauthenticated. This means sign-in has been disabled for that entire directory, usually due to an internal security action, a billing or activation issue, or the directory being flagged inactive. This is a tenant-level problem and is not something you can fix from your own account, even if you are the admin, because the directory itself cannot accept interactive sign-ins right now.
You can try the following steps in order.
Confirm you are targeting the correct tenant Open a new InPrivate or Incognito browser window to rule out cached credentials, then try signing in directly to the tenant using:
https://portal.azure.com/[tenant-id]
Replace [tenant-id] with bfaf4860-b959-420d-bd98-5dca0ab05001. If you belong to other tenants as well, this forces the portal to target this specific directory instead of defaulting to a different one.
Check your Visual Studio Subscriptions portal Go to https://manage.visualstudio.com and sign in with the same account. Confirm whether your subscription benefit still shows as active. Sometimes the Visual Studio subscription itself is fine, but the linked Azure AD directory has been separately deauthenticated, which is what is blocking portal sign-in.
Note down the diagnostic details Keep the following from your error message, since support will need them and they cannot be recovered later if the page session expires:
- Trace ID:
170e7574-9e04-4fec-abc6-a4f64eb21d00- Correlation ID:
019f0c11-adcd-75fc-9328-7553c5c007b1- Timestamp:
2026-06-28 02:31:53Z- Tenant ID:
bfaf4860-b959-420d-bd98-5dca0ab05001
- Visual Studio Subscriptions support: `https://visualstudio.microsoft.com/vs/support/` - Or, if you have any Azure support plan, open a request from `https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade` once you can sign in to any tenant In the request, mention that the tenant was deauthenticated, and include the Trace ID, Correlation ID, Timestamp, and Tenant ID above along with your Visual Studio Subscriptions account email so they can locate the directory and the linked subscription quickly. **If you cannot sign in anywhere to raise a ticket** Use the general Microsoft account recovery and support form at `https://support.microsoft.com/contactus` and select Azure as the product, explaining that your only tenant is deauthenticated and you cannot reach the support blade from within the portal. - Tenant ID:
- Timestamp:
- Correlation ID:
This is a backend directory state that only Microsoft can reset, so self-service steps like clearing cache or re-registering will not resolve it. Once support re-enables authentication on the tenant, you should be able to sign back in and access your VM again without any additional configuration on your end.
If this answer helps you kindly accept the answer which will help others who have similar questions.
Regards,
Sangeetha Kesavan