Skip to content

Ulysses Neves

Microsoft Entra ID, authentication, and hybrid identity troubleshooting.

Menu
  • Home
  • Microsoft Azure
  • Microsoft AD FS
  • Microsoft 365
  • Contact
  • Troubleshooting Index
Menu

Microsoft Entra ID – Enabling the MFA registration policy using Microsoft Entra ID Identity Protection

Posted on January 14, 2020

Hi everyone. In today’s article, we’ll explain what the MFA registration policy in Azure is and how to configure it using Microsoft Entra ID Identity Protection.

What is Microsoft Entra ID Identity Protection

Azure Identity Protection is a risk detection tool that enables automated actions based on data in the Azure platform. This data is also used to control access to resources in Azure through Conditional Access policies, depending on the risk level assigned to the access.

For more information about the types of access risk, check out this link.

Required licensing

To use Identity Protection, at least an Azure AD Premium P1 license is required. Depending on the license type, you can use advanced options of the tool.

  • With an Azure AD Premium P2 license, you can obtain detailed information about the detections made by the tool.
  • With an Azure AD Premium P1 license, you can identify a risk, but you cannot obtain details about it. All events will appear as Additional risk detected access, but the risk level and details are omitted.

Enabling MFA registration

Let’s enable MFA registration using identity protection.

Access the MFA policy menu in Microsoft Entra ID by clicking this link.

To select a user or group required to register, click the Users menu.

Select the user/group to be affected by the policy.

Click Done.

Let’s configure the policy to require MFA registration on the next sign-in, in case the user hasn’t done it yet.

Check the Require Azure MFA registration option.

Note: This policy only affects cloud-based MFA. If the infrastructure has an MFA server, it will not be applied.

Enable the policy by clicking On.

Click Save.

Testing the user’s first access

When accessing any service in Azure with the user affected by the policy, they are prompted to complete MFA registration.

Enter a contact phone number and click Next.

Enter the code received via SMS and click Next.

Once the SMS code is confirmed, you’ll see the message below:

Click Next.

Click Done.

With MFA configured, access to the portal is granted.

Let’s check the MFA methods registered for this user by clicking Update Info in the Security Info menu on the screen above.

Identity confirmation is requested by sending an SMS to the device we just registered.

Enter the code and click Verify.

After verifying the SMS code, access to the portal with the security information is granted.

Adding another authentication method

You can add authentication using Microsoft’s Authenticator App by clicking Add method.

If you don’t have the Microsoft Authenticator app, click Download now. If you already have the app installed, click Next.

Click Next on the screen below.

With the code shown below, perform the steps on your mobile device.

Registering the account in Microsoft Authenticator

After installing the Microsoft Authenticator app on your mobile device, open the app and click the + option located in the top-right corner.

Select the Work or school account option in the Accounts menu.

Scan the code shown by the Azure portal.

With the code scanned, the user’s profile is added to the Microsoft Authenticator app.

After the configuration is done on the device, Azure sends a Push request to the device to complete the process.

On the mobile device, click Approve.

Back in the Azure portal, after the approval is confirmed, you’ll receive the message below:

Click Next.

Changing the default MFA method

With more than one MFA method configured, you can change which option will be requested from the user when MFA is required.

To change the first MFA option, click Change.

Select the Microsoft Authenticator – notification option and click Confirm.

Now we can see that the default option for MFA is the Microsoft Authenticator app. When the user is prompted to confirm their identity, a Push will be sent to the app requesting approval of access.

Summary

In today’s article, we explained step by step how to enable the MFA registration policy using the Identity Protection tool in Microsoft Entra ID. We also demonstrated how to add a second authentication method in the user portal and how to set Microsoft Authenticator as the default for identity confirmation.

I hope this content has helped enrich your knowledge of Azure.

Did you like the post? Like and share it. 🙂

If you have any suggestions or comments, let us know.

[ ]’s

Ulysses Neves

Related guides: Browse the Microsoft Identity Troubleshooting Index or the Microsoft Entra multifactor authentication topic archive.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Microsoft Defender for Identity domain investigation: six questions to ask first September 10, 2026
  • Microsoft Entra Kerberos key rotation: what changes—and what administrators should check September 6, 2026
  • Microsoft Authenticator Will Block Jailbroken Devices in 2026 — What You Need to Know March 17, 2026
  • Enhancing Azure role activation security with FIDO2/Passkeys September 23, 2024
  • Microsoft Entra ID CAP | Enforcing WHfB using Authentication Strength April 21, 2024

Archives

  • September 2026
  • March 2026
  • September 2024
  • April 2024
  • February 2024
  • December 2023
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019

Tags

#aaddownleveldevice #adfs #adfscertificate #adfscertificates #adfsmfaadapter #azureauth #azureCA #azuredevice #capolicy #cloudsummit2021 #conditionalaccess #conditionalaccesspolicy #deviceregistration #farmbehavior #gopasswordless #mfaserver #msidentity #namedlocation #securingazure #securingazuread #sslprivatekey #troubleshootingadfs #troubleshootingwaptrust #tshootadfs #waptrust #webapplicationproxy #WHFBcerttrust #whfbdeployment #WHfBhybridsetup #WHfBprovisioning #widdatabase adconnect AD FS authenticationstrength az500 azurepim Azure security cloudsecurity microsoft365 Microsoft Azure Microsoft Entra hybrid join Microsoft Entra ID Microsoft Entra MFA PowerShell WHfB
©2026 Ulysses Neves | Design: Newspaperly WordPress Theme
Ulysses Neves
Gerenciar Consentimento de Cookies
Para fornecer as melhores experiências, usamos tecnologias como cookies para armazenar e/ou acessar informações do dispositivo. O consentimento para essas tecnologias nos permitirá processar dados como comportamento de navegação ou IDs exclusivos neste site. Não consentir ou retirar o consentimento pode afetar negativamente certos recursos e funções.
Funcional Always active
O armazenamento ou acesso técnico é estritamente necessário para a finalidade legítima de permitir a utilização de um serviço específico explicitamente solicitado pelo assinante ou utilizador, ou com a finalidade exclusiva de efetuar a transmissão de uma comunicação através de uma rede de comunicações eletrónicas.
Preferências
O armazenamento ou acesso técnico é necessário para o propósito legítimo de armazenar preferências que não são solicitadas pelo assinante ou usuário.
Estatísticas
O armazenamento ou acesso técnico que é usado exclusivamente para fins estatísticos. O armazenamento técnico ou acesso que é usado exclusivamente para fins estatísticos anônimos. Sem uma intimação, conformidade voluntária por parte de seu provedor de serviços de Internet ou registros adicionais de terceiros, as informações armazenadas ou recuperadas apenas para esse fim geralmente não podem ser usadas para identificá-lo.
Marketing
O armazenamento ou acesso técnico é necessário para criar perfis de usuário para enviar publicidade ou para rastrear o usuário em um site ou em vários sites para fins de marketing semelhantes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
Ver preferências
  • {title}
  • {title}
  • {title}