Microsoft 365 features that help users manage their subscriptions, account settings, and billing information.
Start with the Microsoft 365 Admin Account Recovery portal at https://aka.ms/cloud-admin-recovery; if it cannot process or verify this Developer tenant, contact Microsoft Support and request recovery of a tenant whose sole Global Administrator cannot satisfy MFA.
1. Submit recovery through the account recovery portal
- Open https://aka.ms/cloud-admin-recovery from a browser that does not have a conflicting Microsoft 365 session.
- Identify the affected tenant using its
onmicrosoft.comdomain and sole Global Administrator sign-in name. - State that:
- The password is accepted.
- Microsoft Authenticator cannot generate codes or receive approvals.
- No alternative authentication method is available.
- There is no other Global Administrator, Authentication Administrator, or Privileged Authentication Administrator.
- Complete the ownership-verification steps offered by the portal.
This recovery path is specifically recommended for sole-administrator MFA lockouts and does not require access to the affected admin center.^1^
Because this is a Developer Program tenant using an onmicrosoft.com domain, the portal might not offer DNS-based custom-domain verification or might not support the tenant’s subscription type. If the portal reports that recovery is unavailable or cannot verify ownership, preserve the error text or screenshot and proceed directly to support.
2. Escalate to Microsoft Support if portal recovery fails
Use the Microsoft 365 business support number for your country or region.^2^ Tell the representative:
The sole Global Administrator of a Microsoft 365 Developer Program tenant cannot satisfy MFA. The password is accepted, there is no alternate administrator, and the Admin Account Recovery portal could not complete recovery. Please open a tenant-lockout recovery case requiring high-assurance tenant ownership verification.
Microsoft’s documented tenant-lockout process is to open a support case when the portals are inaccessible. Microsoft then verifies tenant ownership and helps a designated Global Administrator regain access to the existing tenant; it does not create a replacement tenant.^3^
Ask for the case to be routed to the team responsible for tenant ownership verification and tenant access recovery. Similar sole-admin Developer tenant cases have been handled through the Data Protection team,^4^ but Microsoft Support determines the actual internal routing.
If telephone automation does not produce a case, call again using another business-support number listed for your region and request a live representative. Do not create or post additional tenant/account identifiers in this public thread.
3. Prepare ownership evidence
Microsoft decides which evidence is required case by case. Prepare the following likely supporting information:
- Full tenant domain and, if known, Tenant ID.
- Affected Global Administrator username.
- Approximate tenant creation date and last successful administrative sign-in.
- Access to the personal Microsoft account associated with the Developer Program membership.
- Screenshot of the Developer Program dashboard showing the sandbox subscription, if still accessible.
- Developer Program subscription or order information.
- Billing or Azure subscription details, if the tenant has any paid services.
- Any custom-domain DNS proof, if a verified custom domain exists.
- Recovery-portal result and any existing support case number.
- A reachable contact email and telephone number outside the locked tenant.
The recovery guidance specifically identifies tenant-domain control and billing details as possible verification evidence, but these are not an exhaustive or guaranteed checklist.^1^ An onmicrosoft.com domain cannot provide registrar-level DNS ownership evidence, so emphasize control of the Developer Program membership and any subscription records instead.
Provide sensitive records only through the private channel supplied by Microsoft Support—not in Microsoft Q&A.
Can Microsoft reset the MFA registration?
Yes, Microsoft can assist with restoring access after ownership verification. The eventual remediation can involve recovering the designated administrator’s access so that authentication methods can be registered again.^3^
Ordinarily, an Authentication Administrator can select Entra ID → Users → affected user → Authentication methods → Require re-register MFA, which removes the registered Authenticator, phone, and software OATH methods and prompts new registration.^5^ That path is unavailable here because no other appropriately privileged administrator can sign in; a standard member account cannot perform the reset.
After access is restored, create at least one additional protected Global Administrator/emergency-access account with distinct credentials and authentication methods. Microsoft recommends at least two Global Administrator accounts to reduce the risk of another tenant-wide lockout.^6^
References
- Locked out of my admin account due to multi-factor authentication (MFA) issues - Microsoft Q&A
- Contact Microsoft customer support
- Plan for tenant recoverability
- EMERGENCY - Sole Global Admin locked out of Microsoft 365 Developer tenant – lost MFA phone, no back up! - Microsoft Q&A
- Manage user authentication methods for Microsoft Entra multifactor authentication
- Preventing tenant lockouts