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

AD FS – Historical guidance: Enabling MFA Server as primary authentication method

Posted on January 2, 2022

Deprecation notice — September 2026: This article documents a historical deployment that uses the on-premises Azure Multi-Factor Authentication Server adapter. MFA Server is deprecated and is not available for new deployments. Do not use this MFA Server procedure for a new implementation. For current AD FS deployments, use the built-in Microsoft Entra multifactor authentication adapter and review Microsoft’s migration guidance.

Source: Migrate from MFA Server to Microsoft Entra multifactor authentication: “Azure Multi-Factor Authentication Server (MFA Server) isn’t available for new deployments and is deprecated.”

Current AD FS guidance: Configure AD FS and Microsoft Entra multifactor authentication: “The AD FS 2016 Microsoft Entra multifactor authentication adapter integrates directly with Microsoft Entra ID and doesn’t require an on premises Azure Multifactor Authentication Server.”

Hi mates. Today we’re going to share how to enable additional authentication method to be used as primary authentication on AD FS. On this article, we’ll setup Azure Multi-Factor Authentication Server adapter, but these steps can be applied to Azure MFA adapter or any third-party additional authentication method supported by AD FS. To check the full list of supported adapters, please check this link.

If you plan to use Azure MFA with AD FS, but currently don’t have the service configured, check this official documentation to have it configured: Configure AD FS 2016 and Azure MFA | Microsoft Docs

Enabling the MFA Server as the primary authentication method

In case you have MFA Server environment setup, I will consider one already deployed MFA Server connector setup. As mentioned previously, Azure MFA can be used as well.

Open AD FS console on your AD FS server version 2019, expand Service » Authentication Methods » Select option: Allow additional authentication providers as primary

You will receive a warning message regarding AD FS custom pages as below:

With the option enabled, now we can select Azure Multi-Factor Authentication Server, previously additional authentication method only, now on the Primary authentication tab:

As our goal is to setup multi-factor authentication, on Additional Tab, we’ll use Forms Authentication to have users provide username and password as a second-factor authentication when the user has already authenticated using MFA Server as primary auth:

As recommended on AD FS 2019 version, you need to change the anchor type on the Active Directory Claims Provider Trust from windowsaccountname to UPN as properly documented on this official document: https://learn.microsoft.com/en-us/windows-server/identity/ad-fs/operations/configure-ad-fs-and-azure-mfa#azure-mfa-as-primary-authentication

Using PowerShell, run the command below:

Set-AdfsClaimsProviderTrust -AnchorClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn" -TargetName "Active Directory"

To have Multi-factor required, configure the Access Control Policy on AD FS with setting Permit everyone and require MFA as below:

User experience

With the policy properly configured, let’s have our user accessing portal.azure.com which belongs to Office 365 Relying Party Trust configured above.

First authentication prompt: MFA Server with Phone SMS method

On AD FS Tracing logs, checking event ID 155, we get more information on the Primary authentication:

Primary stage authDomain: AuthenticationMethods:

http://schemas.microsoft.com/ws/2012/12/authmethod/phoneconfirmation
http://schemas.microsoft.com/ws/2012/12/authmethod/voicebiometric
http://schemas.microsoft.com/ws/2012/12/authmethod/smsreply
http://schemas.microsoft.com/ws/2012/12/authmethod/phoneappnotification
http://schemas.microsoft.com/ws/2012/12/authmethod/smsotp
http://schemas.microsoft.com/ws/2012/12/authmethod/otp
http://schemas.microsoft.com/ws/2012/12/authmethod/kba
ProviderAuthInfoList: AzureMfaServerAuthentication
UseProviderAuthInfoList: True

Second authentication prompt: Forms-based authentication with username and password

On AD FS Tracing logs, we see on same event ID 155 Secondary authentication:

Second stage authDomain: AuthenticationMethods:
urn:oasis:names:tc:SAML:1.0:am:password
urn:oasis:names:tc:SAML:2.0:ac:classes:Password
urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport
http://schemas.microsoft.com/ws/2008/06/identity/authenticationmethod/password
ProviderAuthInfoList: FormsAuthentication
UseProviderAuthInfoList: True

Summary

In this article, we covered how to enable adapter ‘Azure Multi-Factor Authentication Server’ as the primary authentication method on AD FS.

I hope you have enjoyed reading this article and it helps you manage your AD FS environment.

Enjoyed the article? Like and share. 🙂

Note: I do not represent the organization I work for, all the opinions expressed here, are my own. This post is provided AS IS with no warranties or guarantees and confers no rights.

In case you have any suggestion or feedback, please leave a comment.

[ ]’s
Ulysses Neves

Related guides: Browse the Microsoft Identity Troubleshooting Index or the Microsoft AD FS 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}