A cloud-based identity and access management service for securing user authentication and resource access
Hello @Mark A Rawson
If multi-factor authentication (MFA) isn’t being triggered for your new Azure account, it’s likely because Azure Entra ID (formerly Azure Active Directory) does not enforce MFA by default. To prompt users to set up MFA using an authentication app like Microsoft Authenticator, you need to enable either Security Defaults or configure a Conditional Access policy.
The simplest approach is to enable Security Defaults. To do this:
- Go to the Azure Portal.
- Navigate to Microsoft Entra ID > Properties.
- Select Manage security defaults and set it to Enabled.
Once enabled, all users will be prompted to register for MFA during their next sign-in. This includes setting up the Microsoft Authenticator app, which they can download on their phone and use to scan a QR code for configuration.
If you require more granular control—for example, enforcing MFA only for specific users, groups, or applications—you can create a Conditional Access policy:
- Go to Microsoft Entra ID > Security > Conditional Access.
- Create a new policy and define the conditions under which MFA is required, such as access to certain apps or logins from untrusted locations.
Additionally, you can manually require a user to re-register for MFA:
- Navigate to Users > Authentication methods in the Azure Portal.
- Select the user and click Require re-register MFA.
Once one of these methods is configured, MFA setup using the authenticator app will be triggered automatically at the user's next sign-in.
We hope this information is helpful. If you need any further assistance, please feel free to reach out — we're happy to help.