A cloud-based identity and access management service for securing user authentication and resource access
For this sign-in pattern, there are two supported paths depending on the exact failure:
- Try browser isolation first.
- Open a private browsing session.
- Edge: open the three-dot menu by the profile picture, select New InPrivate window, then sign in to the Azure portal.
- Chrome: use Incognito mode.
- Safari: use File > New Private Window.
- If the issue continues, clear browser cache and cookies.
- Edge: Settings > Privacy and Services > Clear Browsing Data. Select Browsing history, Download history, Cookies, and Cached images and files, then select Delete.
- Chrome: Settings > Privacy and Security > Clear browsing data.
- If Azure signs in to the wrong account automatically, clearing cookies or using private browsing is the recommended fix.
- Open a private browsing session.
- If the portal shows a tenant or directory-related error:
- In the Azure portal, select the account at the top-right and verify the correct Azure directory is selected.
- If the wrong directory is selected, use Switch directory and choose the correct one.
- If the correct directory is already selected but the portal shows No subscriptions found, the account must be added as Owner on the subscription.
- If the blocker is Microsoft Authenticator or MFA and access cannot be completed:
- If security info-based password reset is enabled by the tenant’s global admin, password recovery can be done using security information and a mobile device.
- If MFA cannot be re-registered and there is no other global admin available, the documented resolution in similar Azure cases is escalation through a support ticket so the Data Protection team can help restore tenant access.
- If a support request cannot be created from the Azure portal because sign-in fails:
- Use the Azure support request entry point: create a support request.
- If the account is effectively locked at the tenant level:
- Similar accepted Azure cases show that tenant lockout or tenant deauthentication requires Microsoft support intervention rather than a self-service fix.
- In those cases, support either engaged the Data Protection team to restore access or re-enabled authentication for the tenant.
- Troubleshoot Azure subscription sign-in issues
- No subscriptions found sign in error for Azure portal
- Troubleshoot sign-in issues and account access problems
- Unable to log into personal azure account - Microsoft Q&A
- Couldn't login in Azure Portal - Unable to verify my identity (Error:500121) - Microsoft Q&A
- Can't log into portal.azure.com using my personal account anymore - Microsoft Q&A
- I cannot login to Azure portal with MSA account? - Microsoft Q&A