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 – Historical per-user MFA configuration

Posted on November 4, 2019

Historical per-user MFA notice — September 2026: This article preserves the per-user MFA interface and procedure shown at its original publication. For current deployments, Microsoft recommends requiring Microsoft Entra multifactor authentication through Conditional Access. For Microsoft Entra ID Free tenants without Conditional Access, use security defaults. Do not enable or enforce per-user MFA for users governed by Conditional Access policies.

Source: Enable per-user multifactor authentication: “The best way to protect users with Microsoft Entra MFA is to create a Conditional Access policy.” Microsoft also states: “Don’t enable or enforce per-user Microsoft Entra multifactor authentication if you use Conditional Access policies.”

Current implementation guide: Enable Microsoft Entra multifactor authentication: “The recommended way to enable and use Microsoft Entra multifactor authentication is with Conditional Access policies.”

Hello, everyone. In today’s article, we’ll show how to enable MFA for users in Azure. This article continues covering content from 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 upcoming articles on this blog.

Enabling MFA on a Global Administrator Account

Let’s enable MFA for an account with global administrator privileges. It’s a good security practice to use these accounts only in emergencies and, to administer the environment, use accounts with specific roles for each activity.

Let’s enable MFA for a user with global admin privilege to allow us to enable other users.

Access the users menu by clicking this link.

The alt attribute for this image is empty. The file name is image-14-1024x333.png

Select the More option.

Select the Multi-Factor Authentication option.

The alt attribute for this image is empty. The file name is image-15.png

In the View option, select Global Administrators.

Note: If you want to enable MFA for users with other roles, simply select the desired role to filter the users.

The alt attribute for this image is empty. The file name is image-16.png

Select the user for whom you want to enable MFA and click Enable.

The alt attribute for this image is empty. The file name is image-17.png

Select enable multi-factor auth.

The alt attribute for this image is empty. The file name is image-18.png

You can configure some options for users who use MFA by clicking Manage User settings.

The alt attribute for this image is empty. The file name is image-21.png
  • Require selected users to provide contact methods again – Forces the user to register their contact methods again. This request is made for applications accessed through browsers.
  • Delete all existing app passwords generated by the selected users – Removes the passwords created for applications that are not accessible through browsers.
  • Restore multi-factor authentication on all remembered devices – Forces two-step verification on devices marked as trusted by users on their next access.
The alt attribute for this image is empty. The file name is image-20.png

Using Two-Factor Authentication

With MFA enabled for the user Ismar, let’s log in to portal.azure.com with the user’s credentials and validate the two-factor authentication.

Enter the credential and click Avançar.

Enter the password and click Entrar.

In the screen below, click Avançar.

On the two-step verification method selection screen, let’s select Aplicativo móvel with the Usar código de verificação option to demonstrate how to use Microsoft Authenticator with MFA.

Click Configurar.

Follow the steps below to use two-factor authentication in Azure using Microsoft Authenticator.

Configuring Microsoft Authenticator on the Mobile Device

Install Microsoft Authenticator on your iOS or Android device. For more information, click this link.

Select the Work or school account option.

Point the camera at the QR code from the screen above to log in to the app.

Back in the browser, click Avançar.

Enter the code generated by the app and click Verificar.

Enter your contact phone number to add more verification methods to your account.

Click Avançar.

If you use applications that don’t support modern authentication, you can use an “app password” to protect against unauthorized access.

Click Concluído.

Done! Now you’ll be able to access the Azure portal or the application you want with more security.

Summary
In today’s article, we showed how to enable MFA for users in Azure and demonstrated a two-factor validation using Microsoft Authenticator.

In the next article, we’ll continue with the “Configure Microsoft Azure Active Directory for workloads” topic, explaining how to activate MFA licenses for users in Azure using the portal and PowerShell.

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, leave a comment.

[ ]’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

  • Conditional Access report-only: why a successful sign-in can show a policy failure October 9, 2026
  • Microsoft Entra SMS and Voice Retirement: An Admin Preparation Checklist September 24, 2026
  • 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

Archives

  • October 2026
  • 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}