A cloud-based identity and access management service for securing user authentication and resource access
Since you’re using a personal Microsoft account and you no longer have the old phone where Microsoft Authenticator was set up, the Azure portal is still trying to use the old MFA configuration. That’s why you’re stuck in a loop asking for a verification code that never appears — the portal is expecting an authentication method that no longer exists.
For personal accounts, the only way to fix this is to reset your security info so you can register Authenticator again on your new phone.
1. Start with the Microsoft account recovery flow
Go to: https://account.live.com/acsr. This is the official recovery process for personal Microsoft accounts. It will ask you to verify your identity using any backup methods you still have access to (alternate email, phone number, etc.). Once you complete this, you’ll be able to add Microsoft Authenticator on your new phone.
2. If the recovery flow doesn’t accept your information
Use the extended recovery option: https://aka.ms/recoveraccount**.**This lets you submit additional verification details so Microsoft can confirm you’re the rightful owner of the account.
3. Important clarification
You mentioned you can sign in to your email — that’s good, but Azure uses the same identity with stronger security requirements. If MFA was previously set up on your old phone, Azure won’t let you in until those authentication methods are reset.
Once your security info is cleared and re‑registered, you’ll be able to sign in to the Azure portal normally.
Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.