Posted on 11/11/26 11:05 am
Azure sign-ins use Microsoft Entra multifactor authentication. Register a method at your Security info page, ideally the Microsoft Authenticator app.
| Method | Notes |
|---|---|
| Microsoft Authenticator push or number matching | Common default; you approve on your phone |
| Passkey or FIDO2 security key | Strongest; resists phishing |
| Windows Hello for Business | Face, fingerprint or PIN on managed PCs |
| Text or voice call | Weaker; some organisations turn these off |
Microsoft now requires multifactor authentication for signing in to the Azure portal and other admin tools. If you are suddenly asked to set it up, this is likely why. Your organisation may also use Conditional Access rules that ask for MFA in more situations.
Add the Authenticator on the new phone in Security info before wiping the old one. If the old phone is gone, ask your IT admin to require re-registration of MFA for your account.
An approval request you did not start means someone may have your password. Deny it, change your password and tell your IT team. Number matching, where you type the number shown on screen, helps stop accidental approvals.
Personal Microsoft accounts work differently; see Microsoft two-step verification.
If you created an Azure subscription with a personal Microsoft account, MFA still applies to portal sign-ins. Set up the Authenticator app in your Microsoft account security settings, and add a recovery method so you are not locked out of billing and resources.
Azure CLI and PowerShell sign-ins also go through MFA for user accounts. For scheduled scripts and pipelines, use a service principal or managed identity with limited permissions instead of a person's account.
Add methods at mysignins.microsoft.com › Security info.
Yes, Microsoft now requires it.
Ask your IT admin to reset your MFA registration.
Related: Microsoft two-step verification · passkeys · lost authenticator phone.
Receive SMS online · Non-VoIP numbers · Temporary phone numbers · Free numbers