A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
Use the following steps to troubleshoot sign-in issues with a personal Azure/Microsoft account and Azure portal access:
- If the Azure portal page hangs or doesn’t complete sign-in, try:
- Refreshing the page.
- Using a different browser.
- Using private/incognito mode (for example, Edge InPrivate, Chrome Incognito, Safari Private Window) and then browse to the Azure portal.
- Clearing browser cache and cookies (browsing history, download history, cookies, cached images and files) and then trying again.
- If the browser is automatically signing in with a different account than the personal Azure account:
- Clear cookies and cached data as above.
- Alternatively, sign out of all Microsoft accounts in the browser, then sign in again with the correct personal account.
- If the issue is specifically with the My Apps portal (for example, accessing apps tied to the account):
- Ensure the URL is correct:
https://myapps.microsoft.comor your organization-specific My Apps URL. - If there is an error about a personal Microsoft account, try using the tenant-specific URL format:
-
https://myapplications.microsoft.com?tenantId=*your_domain_name* -
https://myapplications.microsoft.com?tenant=*your_tenant_ID*
-
- Verify the password is correct and not expired; if needed, reset it using the work/school password reset flow.
- Ensure security verification info (phone, Authenticator, etc.) is up to date.
- Add the My Apps portal URL to Internet Properties > Security > Trusted sites.
- Clear browser cache and try again.
- Ensure the URL is correct:
- If sign-in fails because of Multi-Factor Authentication (MFA) verification problems (for example, phone call or SMS not working):
- For phone call MFA, make sure to respond by pressing the pound key (#) when prompted.
- For SMS MFA, ensure the correct verification code is entered.
- If other verification options are configured, choose Other verification options and try a different method, and verify that phone numbers in the account settings are correct.
- If the error message indicates the tenant is blocked due to inactivity (AADSTS5000225):
- A tenant blocked for inactivity can be reactivated only within 20 days of entering the inactive state. After 20 days, it is permanently deleted and cannot be recovered.
- If it has been less than 20 days since the block, the tenant administrator must contact Microsoft support (using the global support phone numbers) to request reactivation.
- If the tenant is already deleted (more than 20 days inactive), a new tenant must be created and associated with the account.
- If the account was created recently for a free Azure subscription and shows inactivity/blocked behavior:
- Try signing in from a clean/incognito browser session to
https://signup.azure.comusing the same email. If the sign-up page recognizes an existing free account with remaining credits, follow the prompts to upgrade to a pay-as-you-go account (for example, a basic pay-as-you-go tier) to restore portal access.
- Try signing in from a clean/incognito browser session to
If none of these steps resolve the issue and the tenant is still within the 20‑day reactivation window, the administrator of the tenant must open a support case with Microsoft as described in the tenant inactivity guidance.
References:
- Troubleshoot Azure subscription sign-in issues
- Troubleshoot problems with the My Apps portal
- "Account verification system is having trouble" error message when you try to sign in by using a work or school account
- Error AADSTS50020 - User account from identity provider does not exist in tenant
- Microsoft Invest - Identity Platform login troubleshooting
- Error message: interaction_required: AADSTS5000225: This tenant has been blocked due to inactivity - Microsoft Q&A
- 7 Day Old Azure Account: AADSTS5000225: This tenant has been blocked due to inactivity. - Microsoft Q&A
- Can not access Azure - Microsoft Q&A
- Azure has blocked myphone number for SMS verification due to a “bad reputation” flag - Microsoft Q&A
- Error message: AADSTS5000225: This tenant has been blocked due to inactivity. - Microsoft Q&A