Cannot access my VM suddenly in Azure Portal

Question

Since yesterday, I have been unable access the resource group or the VM within it that I created over a year ago.

I have had no issues for a long time and suddenly I am getting an error.

{ "shellProps": { "sessionId": "771fef9444ba418bba40226b16881bee", "extName": "HubsExtension", "contentName": "ResourceMenuBlade", "resourceId": "/subscriptions/ID/resourceGroups/VM-GROUP/providers/Microsoft.Compute/virtualMachines/VM" }, "error": { "message": "No access to the VirtualMachine resource", "code": 401, "details": "You do not have authorization to access the VirtualMachine resource. Resource ID: /subscriptions/ID/resourceGroups/VM-GROUP/providers/Microsoft.Compute/virtualMachines/VM, Status Code: 401, Status Message: The access token is from the wrong issuer 'https://sts.windows.net/8643ce68-ce6e-4f0a-bf75-6cfd1cefd4a8/'. It must match the tenant 'https://sts.windows.net/b7d78e28-fc6b-4b77-ae87-8976287b2448/' associated with this subscription. Please use the authority (URL) 'https://login.windows.net/b7d78e28-fc6b-4b77-ae87-8976287b2448' to get the token. Note, if the subscription is transferred to another tenant there is no impact to the services, but information about new tenant could take time to propagate (up to an hour). If you just transferred your subscription and see this error message, please try back later." }}

I have not transferred my subscription or anything within it at all. I'm super confused what's going on and would love some help.

Answer 1

Thanks for posting your question in the Microsoft Q&A forum.

To resolve this issue, try the following steps:

• Sign out of the Azure portal completely and then sign back in. This will force a new authentication token to be generated.
• Clear your browser cache and cookies, then try accessing the VM again.
• If you're using multiple Microsoft accounts, ensure you're logged in with the correct account that has access to this subscription and VM.
• Try accessing the VM using a different browser or the Azure CLI to rule out any browser-specific issues.
• Check your Azure Active Directory settings to ensure your account is still properly associated with the correct tenant.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful