How do I get ahold of Azure support if I can't access Azure?

Question

How do I get ahold of Azure support if I can't access Azure?

Andre Gagne 0

I think I used my personal account to replicate an external user at my last company and now I'm in a circular loop.

I'm getting the following error whenever I'm on an Azure page (including support) which completely breaks my ability to use the webpage. and Azure support phone now tells you to use the website to submit a ticket...

{
  "sessionId": "46fdaa8209724bce85bfc5321d847a94",
  "errors": [
    {
      "errorMessage": "login_required: AADSTS50058: A silent sign-in request was sent but no user is signed in. The cookies used to represent the user&#39;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: 30c0af08-0d56-46bb-8c1b-c9ac4f2f1b00 Correlation ID: 284aa6fa-db84-4786-83cd-c25a215756c9 Timestamp: 2026-10-13 15:46:40Z",
      "clientId": "<>",       
      "scopes": [         
          "<>/.default"       
      ]     
    }   
  ] 
}

0 comments

1 answer

Your answer

Answer 1

That error is AADSTS50058, and it means the application attempted silent** authentication, but Microsoft Entra could not find a usable signed-in session/cookie for the requested account. Microsoft guidance is to treat this as an interaction-required **condition and perform an interactive sign-in.

Open a completely fresh InPrivate/Incognito** **browser and explicitly authenticate to the target tenant/account rather than relying on an existing Microsoft session.

Be aware that browser privacy controls can themselves block cookies used for silent SSO. Microsoft specifically identifies missing/blocked authentication cookies as a cause of AADSTS50058. [learn.microsoft.com]

For troubleshooting, I would:

Close all Microsoft/Azure tabs.
Start a fresh InPrivate window.
Ensure cookies aren't being blocked for Microsoft sign-in endpoints.
Navigate directly to the application.
Explicitly enter the intended Microsoft account.
Complete interactive authentication rather than allowing silent SSO.

If interactive authentication succeeds, the problem was the silent-session context rather than the underlying account.