But this is what I suspect: the MFA server must rely on some data or tokens stored in your individual Azure AD tenant, right alongside your password hashes that are synced from the on-premises Active Directory. Curious, isn’t it? I plan to follow-up with whoever I can bug at Microsoft to figure out what the deal is here. It turns out, if you are using Azure AD Connect (formerly DirSync) with the password sync feature (this is like 90% of my client base), then the MFA Server is not going to be an option you. Just for the sake of doing my homework, I decided to read up on more detail on Azure’s documentation library.* And wouldn’t you know it, look what I found:
There is a great resource on the web at RDS Gurus that steps you through this process. I was recently asked for help implementing Microsoft’s Multifactor Authentication Server for an on-premises Remote Desktop farm.
0 kommentar(er)
