Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
/cc @Raja Pothuraju
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Dear Microsoft Support Team,
I am seeking assistance with an Azure administrator MFA lockout.
I am the sole administrator of a personal Azure tenant, accessed using my Microsoft account (Hotmail).
After replacing my mobile phone, I lost access to the Microsoft Authenticator registration associated with Azure.
Although I can successfully access my personal Microsoft account and have configured Authenticator on my new phone, Azure continues requesting verification through the previous Authenticator registration.
Troubleshooting already completed:
Confirmed that no alternative MFA verification methods are available.
Attempted to re-register Authenticator without success.
Contacted Microsoft telephone support multiple times but was redirected to password recovery or disconnected.
Attempted to obtain assistance through a separate Azure tenant, but could not successfully submit a recovery request.
As I am the only administrator, I cannot reset the Azure MFA registration myself.
Request for Microsoft Moderator Assistance
I understand from similar cases on Microsoft Q&A that sole-administrator MFA lockouts can be escalated to the Azure / Microsoft Entra Data Protection team.
Could a Microsoft moderator please assist in initiating this escalation or arranging contact with the appropriate recovery team?
I can provide my tenant ID, affected account, contact details and any necessary ownership verification privately through an official Microsoft support channel.
Thank you for your assistance.
/cc @Raja Pothuraju,
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
/cc @Raja Pothuraju
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more