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 – Introduction to Multi-factor Authentication

Posted on October 21, 2019

Hello, everyone. In today’s article, we’ll explain what Microsoft Entra multifactor authentication is and what it is used for. This article covers the subtopic “configure multi-factor authentication settings” of the AZ-500 – Microsoft Azure Security Technologies exam. If you’re preparing to take this exam, don’t miss the upcoming articles.

What is Microsoft Entra multifactor authentication?

Microsoft Entra multifactor authentication (Multi-factor Authentication) uses an additional layer of access protection for applications or services hosted in Azure. It is possible to enable or disable MFA for users according to the information security policy defined by the company.

Password issues

The use of passwords to access cloud applications brings some information security issues. Among them, we can mention:

  • Password reuse;
  • Passwords stored electronically in a single place;
  • Passwords that are easy to remember are also easy to guess;
  • The same or similar passwords across different sites;
  • Passwords that are not changed frequently;
  • Users reusing personal passwords in professional environments.

Authentication types

With the issues mentioned above and the number of stolen passwords, the concept of multifactor authentication is introduced, where more than one authentication method is used to provide access to a resource. For example: password, hardware or software token, mobile device to receive a secret code, biometrics.

Microsoft Entra multifactor authentication uses some of the methods mentioned above. Let’s talk a little more about them.

Phone call mode

The phone call mode used by Microsoft Entra multifactor authentication places an automated call to a previously registered number, and the user presses the # key to authenticate.

It is possible to configure the caller number and also optionally request a PIN code during the call (Azure MFA Server).

SMS mode

SMS mode allows an authentication code to be sent, which the user uses to confirm their access credentials in the browser, called a one-way check.

When there is an Azure MFA Server, it is possible to ask the user to send the PIN code back, confirming their credentials and gaining access to the service in the browser. This mode is called a two-way check.

Microsoft Authenticator app mode

The Microsoft Authenticator app is software used for two-factor authentication and uses three methods to protect users’ access to services in Azure. They are:

  • Push verification – A message is sent to the user’s app on their smartphone or tablet, and they confirm whether the access is legitimate.
  • Pin code – It is possible to add a PIN code to confirm the identity when you have an Azure MFA Server.
  • OAUTH Token – After signing in to the app, it generates a random 6-digit code every 30 seconds that the user uses to access services in Azure.

Summary

In today’s article, we gave a brief introduction to the purpose of Microsoft Entra multifactor authentication and the methods used to confirm users’ identities when accessing services in Azure.

In the next article, we’ll explain the licenses available for MFA and how to enable the two-factor authentication methods we just explained.

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

Best regards,

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}