A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
The 500 error on marketplace.visualstudio.com together with the Azure portal banner about “experiencing authentication issues” indicates a problem obtaining an authentication token in the browser session, not with the underlying account itself.
Use the following steps that address token and sign‑in problems in Microsoft portals:
- Clear cached sign‑in state and cookies
- Sign out of all Microsoft sites in the browser.
- Clear browsing data (history, cookies, cached files) for the browser you’re using.
- The Azure subscription sign‑in guidance notes that using multiple accounts in one browser can cause the wrong identity or stale tokens to be used; clearing cookies/cache or using a clean profile resolves this.
- Try a private/incognito session or different browser
- Open a new InPrivate/Incognito/Private window and sign in again to the Azure portal and then to the Visual Studio Marketplace.
- This avoids existing cookies and cached tokens that may be causing the authentication timeout.
- Check for sign‑in loops or security‑zone issues
- If using Internet Explorer or Microsoft Edge with custom security zones, make sure the following sites are not treated differently (for example, only some of them in Trusted Sites):
-
microsoft.com -
support.microsoft.comand its subdomains -
login.live.com -
login.microsoftonline.com
-
- If organizational policy requires them in Trusted Sites, ensure all of them are added so cookies can be shared correctly. Misconfigured zones can cause repeated sign‑in prompts or failures when contacting support from the portal.
- If using Internet Explorer or Microsoft Edge with custom security zones, make sure the following sites are not treated differently (for example, only some of them in Trusted Sites):
- If sign‑in still fails
- If the issue persists after clearing cache/cookies and using a private session, and you cannot use the “Contact support” button in the portal due to the same token error, use an alternate device or network to reach support.microsoft.com and sign in there. The support sign‑in troubleshooting article recommends ensuring browser security settings allow cookies for the Microsoft sign‑in endpoints.
If, after these steps, the Azure portal still shows “experiencing authentication issues” for the Microsoft_Azure_Support extension, the problem may be transient on the service side; retry later and then create a support request once the token acquisition succeeds.
References: