Error Code: 500121 - locked out from azure where I registered with a personal outlook account

Question

Error Code: 500121 - locked out from azure where I registered with a personal outlook account

ThinkER 0

I need help. Cannot login back to portal.azure.com where I opened an account with my personal outlook account. I cannot access back into azure. I get and MFA notification which does not reach Authenticator, and when try the alternative to verify with the authenticator verification code an 6 digit code is expected, but Authenticator for my personal outlook account gives me only a 8 digit code. I am given no other alternative, and meanwhile I am locket out from my azure account unable to use a VM. Please help, as I cannot even raise a ticket - no access to azure account -

Shubham Sharma 17,930 Reputation points Microsoft External Staff Moderator

2026-05-14T04:08:47.9466667+00:00

ThinkER

Based on the details you’ve shared, this appears to be a tenant lockout scenario.

To resolve this, the recommended approach is to contact the Microsoft Data Protection team. You can reach them by calling Microsoft Customer Service using the phone numbers listed here: https://support.microsoft.com/en-us/topic/customer-service-phone-numbers-c0389ade-5640-e588-8b0e-28de8afeb3f2

If you have access to another tenant or subscription where you still have Global Administrator privileges, you may also raise a support request from there to get assistance in restoring access to the affected tenant.

For future reference and to help prevent tenant lockouts, please check: https://learn.microsoft.com/en-us/partner-center/customers/gdap-preventing-tenant-lockouts

If neither option is possible, let us know, we are happy to assist you further!
Shubham Sharma 17,930 Reputation points Microsoft External Staff Moderator

2026-05-15T06:08:37.7933333+00:00

ThinkER

Following up to check if the resolution provided was helpful. Let us know if you need any further assistance.

1 answer

Your answer

Shubham Sharma 17,930 Reputation points Microsoft External Staff Moderator

2026-05-14T04:08:47.9466667+00:00

ThinkER

Based on the details you’ve shared, this appears to be a tenant lockout scenario.

To resolve this, the recommended approach is to contact the Microsoft Data Protection team. You can reach them by calling Microsoft Customer Service using the phone numbers listed here: https://support.microsoft.com/en-us/topic/customer-service-phone-numbers-c0389ade-5640-e588-8b0e-28de8afeb3f2

If you have access to another tenant or subscription where you still have Global Administrator privileges, you may also raise a support request from there to get assistance in restoring access to the affected tenant.

For future reference and to help prevent tenant lockouts, please check: https://learn.microsoft.com/en-us/partner-center/customers/gdap-preventing-tenant-lockouts

If neither option is possible, let us know, we are happy to assist you further!
Shubham Sharma 17,930 Reputation points Microsoft External Staff Moderator

2026-05-15T06:08:37.7933333+00:00

ThinkER

Following up to check if the resolution provided was helpful. Let us know if you need any further assistance.

Answer 1

Error 500121 with a personal Microsoft account used in Azure usually indicates a problem with the Azure MFA profile for that account. In this scenario, the Authenticator app is showing 8‑digit codes while Azure is prompting for a 6‑digit code and push notifications are not arriving, so the MFA configuration is effectively stuck and blocks sign‑in.

For a personal Microsoft account used in an Azure tenant, MFA cannot be reset self‑service from the personal account side; it must be reset from within the Azure tenant where the account is registered.

Use the following approach:

Have an administrator in the tenant reset MFA for the affected account
If the personal Outlook account is a user or guest in an Azure AD/Microsoft Entra tenant that has other Global Administrators:
1. A Global Administrator signs in to the Microsoft Entra admin center.
2. Go to Identity → Users → All users.
3. Select the affected personal Outlook account.
4. Open Authentication methods.
5. Select Require re‑register multifactor authentication.
6. Sign‑in with the affected account again; it should now prompt to set up MFA from scratch and allow registering a working method (new Authenticator registration, SMS, etc.).
This is the standard way to clear a stuck MFA profile for a user account in a tenant.
If there is no other Global Administrator (only one admin and it is locked out)
If the personal Outlook account is the only Global Administrator in the tenant and no one else can perform the reset:
- Microsoft’s Data Protection / Tenant Recovery process must be involved to verify identity and regain access to the administrator account.
- This requires contacting Microsoft support by phone (customer service phone numbers) or via a separate tenant:
  - Optionally create a new trial Microsoft 365/Azure tenant under a different account.
  - Sign in to the Microsoft 365 Admin Center of that new tenant.
  - Go to Support → Help & support and open a service request.
  - Clearly state that access is lost to a different, existing tenant where the locked‑out personal Outlook account is the only Global Administrator, and request Data Protection / Tenant Recovery assistance to reset MFA for that admin account.
  - Provide the locked tenant’s domain, the admin UPN (the personal Outlook address), and details of the MFA issue and error 500121.
This process does not give access to data from the new trial tenant; it is only a channel to reach Microsoft support so they can validate ownership and reset MFA on the original tenant.
If the personal Outlook account itself is locked or has verification issues
If, in addition to the Azure MFA problem, the underlying Microsoft account has verification issues (codes not arriving, account flagged, etc.), use the Microsoft account security and verification guidance:
- Go to the Security basics page for the Microsoft account and update or replace security info as described in the verification‑code troubleshooting article.
- Be aware that if the account has been flagged for unusual activity or locked, verification messages might not go through until that is resolved.

Until an admin in the tenant (or Microsoft via Data Protection/Tenant Recovery) resets the MFA registration for the personal account, the stuck 6‑digit vs 8‑digit code mismatch will continue to block sign‑in and prevent raising a support ticket from within the locked tenant.

References: