![]() ![]() If you are using one of the other approaches, then cloud-based Azure AD MFA is what yo will want to go with, as you are correct, the on-premises Azure AD MFA server is no longer a supported and available option for new deployments. Note: I’m using the FEITIAN BioPass FIDO2 Security key. IF you are going with the Federation with ADFS solution, then a 3rd party MFA provider is an option, and there are links in the document, under the COMPARING METHODS section, about 3/4 of the way down the page in the MFA section to address how to go about that. Option 1: Windows Security key manager Go to Settings > Sign-in options Click Security keys > Manage Insert your Security key Touch your security key Since I’ve already setup a PIN earlier, I’ll continue with setting up Fingerprint. The document I suggested you look at above lists 3 different scenarios for deployment, and discuses, compares and contrasts all three for you in detail. it depends on what the architecture model you have chosen to go with is. A few things to be aware of here.Ī Third Party MFA solution would be a possibility, and appropriate in certain circumstances, BUT. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |