All settings appear to be there on the slave.The Slave server replicates the settings from the Master server.After being on the phone with MS support for 45 minutes and them looking through the logs etc, and flicking between screens and settings in the MFA console, I ended up working the problem out myself. Checking the logs showed that it could not resolve the username being presented. The issue was when the Netscaler was pointed at the slave server, the authentication failed continually. I could see all the settings etc and users. The second server was built and connected to the master without any real issues. With Netscaler, the Directory Authentication had to be set to to use LDAP instead of “Use Active Directory” as I was using Radius for authentication from the Netscaler to the MFA on-premise server.Īt this stage I thought it would be a great idea to build a second server to allow HA. Not to bad to setup really once you get past all the catches. I had built the initial MFA server and followed the usual web guides found on the Microsoft page ( ). We use Citrix and hence a Netscaler as well for external access. Recently went down the path of moving to Azure MFA for our 2-factor system of choice.

On prem mfa