

For the purpose of this blogpost, two Windows Server 2016-based installations will be deployed. NET Framework 4 installed and be made members of an existing Active Directory environment. WEB1 – This server becomes the Azure MFA Web Server.MFA1 – This server becomes the Azure MFA Back-end Server (Master).The implementation performed, resembles the Stretched deployment in terms of the supported Azure MFA Server deployment scenarios, discussed earlier:įor this scenario, two Windows Server installations are needed: Of course, it’s a good idea to make a back-up of your Domain Controllers and test one of the backups in a separate networking environment to make sure you’re able to restore. Credentials for an account that has the Global administrator role assigned in Azure AD.Credentials for an account that is a member of the Domain Admins group in Active Directory.


The DNS domain name of your organization’s Active Directory Domain Services (AD DS) environment.It details how to install and configure the base components: The MFA Server, the Web Service SDK and the User Portal.īefore you begin, you should have access to the following information: This blogpost details how to setup and configure Microsoft’s on-premises Azure Multi-factor Authentication (MFA) Server product in an existing environment.
