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 multifactor authentication – How to enable MFA using a conditional access policy

Posted on November 20, 2019

Hello, everyone. In today’s article, we’ll explain how to enable MFA for Azure users using a conditional access policy. If you don’t yet know what a conditional access policy is, check out this link where I explain the concept of this feature in Azure. This article covers the “configure multi-factor authentication settings” topic of the AZ-500 – Microsoft Azure Security Technologies exam. If you’re preparing to take this exam, don’t miss the next articles on this blog.

Enabling MFA using conditional access

Go to the conditional access policies menu by clicking this link.

Sign in with your Azure credential with administrative privileges.

When you open the menu options, you can see a few default policies already created that can be used.

Creating a custom policy

To illustrate, let’s create a policy that forces the use of a second authentication for users defined as global admins:
Name: Azure Admins force MFA
Assignments: Global admins
Cloud apps: Microsoft Azure management (Azure portal)
Access controls: grant access (Require Multi-factor authentication)

Click the New policy button.

Set a name for your policy in the Name option.

Conditional access policy scope: We’ll set it so that users assigned the global administrator role must use MFA to access the Azure management portal.

Set the affected users by selecting Assignments > Users and groups > Include.

Click the Select users and groups > Directory roles (Preview) option.

Search for the Global Administrator role and click Done.

Let’s set the application to be affected by the policy by clicking Cloud apps and actions > Cloud apps > Include > Select apps.

In the app search option, type Microsoft Azure Management (Azure portal).

Check whether the policy does not affect the user performing the action, or applications that could impact restoring the policy to its original state in case of problems.

Click Done.

To configure access control, look for the Access controls menu. Let’s click Grant > Grant access > Require multi-factor authentication.

Since the policy affects the user I’m logged in as, because I hold the global administrator role, a message is shown along with the option to exclude the logged-in user from the policy.

Let’s keep the policy turned off and click Create.

Activating the conditional access policy

With the policy created, we’ll find it in the list of available policies.

Click the policy you created.

In the Enable policy menu, there are three options:

  • Report-only: This is the newest conditional access policy option, intended to let the administrator evaluate the policy’s impact on the users who will be affected by it. For more information, visit this link.
  • On: Policy enabled.
  • Off: Policy disabled.

Let’s enable the policy by clicking On and then Save.

Accessing the Azure portal

To test the policy, let’s access the Azure portal again using the user John@ulyssesneves.com.

Azure MFA is triggered and requests more information from the user.

Click Avançar.

Let’s select two-step phone verification by selecting the SMS option.

Enter the country code and the phone number that will receive the SMS and click Avançar.

Enter the code received by SMS and click Verificar.

Click Concluído.

With two-factor authentication verified, access to the Azure portal is granted to the user John.

Summary

In today’s article, we talked about how to enable MFA using a conditional access policy.

In the next article, we’ll continue with the topic “Configure Microsoft Azure Active Directory for workloads“, explaining how to configure conditional access policies as an exception for MFA use based on the user’s location.

I hope this content has contributed to enriching 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}