PIM role activation but only with FIDO2-based MFA?

%3CLINGO-SUB%20id%3D%22lingo-sub-2862930%22%20slang%3D%22en-US%22%3EPIM%20role%20activation%20but%20only%20with%20FIDO2-based%20MFA%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2862930%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20currently%20possible%20to%20define%20an%20authentication%20method%20policy%20so%20that%20FIDO2%20security%20keys%20can%20only%20be%20used%20by%20a%20select%20number%20of%20users%20or%20groups%20(that%20is%2C%20in%20the%20Azure%20portal%20under%20Security%20%26gt%3B%20Authentication%20methods%20%26gt%3B%20FIDO2%20Security%20Key%20%26gt%3B%20FIDO2%20Security%20Key%20settings).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20a%20user%20who%20is%20eligible%20for%20an%20Azure%20AD%20admin%20role%20which%20is%20managed%20via%20PIM%2C%20if%20MFA%20is%20required%20to%20activate%20that%20role%2C%20is%20it%20possible%20to%20limit%20the%20choice%20of%20MFA%20to%20only%20a%20FIDO2%20security%20key%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20would%20be%20for%20a%20scenario%20where%20a%20standard%20user%20sign-in%20to%20the%20Azure%20portal%20would%20be%20secured%20using%20MFA%20(for%20example%2C%20using%20the%20Microsoft%20Authenticator)%2C%20but%20activating%20an%20admin%20role%20through%20PIM%20would%20require%20the%20use%20of%20a%20FIDO2%20security%20key%20instead.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20Sign-Ins%20(%20%3CA%20href%3D%22https%3A%2F%2Fmysignins.microsoft.com%2Fsecurity-info%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmysignins.microsoft.com%2Fsecurity-info%3C%2FA%3E%26nbsp%3B)%20lets%20you%20select%20a%20default%20sign-in%20method%20under%20Security%20info%20(for%20example%2C%20Microsoft%20Authenticator%20-%20notification%2C%20or%20Authenticator%20app%20or%20hardware%20token%20-%20code)%2C%20but%20I%20can't%20see%20a%20setting%20in%20the%20Azure%20portal%20to%20specify%20a%20FIDO2%20security%20key%20as%20a%20default%20or%20preferred%20MFA%20method.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20had%20success%20in%20making%20a%20FIDO2%20security%20key%20the%20default%20MFA%20method%2C%20in%20particular%20when%20working%20with%20PIM%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2862930%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Efido2%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMFA%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPIM%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2863085%22%20slang%3D%22en-US%22%3ERe%3A%20PIM%20role%20activation%20but%20only%20with%20FIDO2-based%20MFA%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2863085%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F278450%22%20target%3D%22_blank%22%3E%40RGFUK%3C%2FA%3E%26nbsp%3BInteresting%20question.%20The%20enabling%20of%20PIM%20and%20requiring%20MFA%20for%20activation%20calls%20for%20Azure%20MFA%20which%20is%20configured%20by%20you%20the%20admin%2C%20i.e.%20the%20options%20under%20%3CA%20href%3D%22https%3A%2F%2Fportal.azure.com%2F%23blade%2FMicrosoft_AAD_IAM%2FMultifactorAuthenticationMenuBlade%2FGettingStarted%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EService%20settings%3C%2FA%3E%26nbsp%3BWhich%20in%20turn%20are%20also%20the%20options%20being%20available%20to%20you%20in%20the%20security%20info%20drop-down%20you're%20referring%20to.%20I%20don't%20work%20setting%20up%20PIM%20as%20a%20feature%20(must%20have%20that%20said)%20but%20AFAIK%20you%20cannot%20separate%20MFA%20with%20%22must%20use%20authenticator%20app%20here%20and%20must%20use%20FIDO2%20here%22.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFIDO2%20satisfies%20MFA%20while%20not%20being%20supported%20as%20a%20true%20second%20factor.%20With%20that%20in%20mind%20you%20should%20be%20able%20to%20use%20FIDO2%20as%20the%20verification%20method%20(hardware%20token)%20when%20enabling%20a%20PIM%20role%20and%20requiring%20Azure%20MFA%20as%20both%20Authenticator%20app%20and%20FIDO2%20are%20used%20for%20sign-in%20%3CEM%3Eand%3C%2FEM%3E%20strong%20authentication.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELet%20me%20know%20how%20it%20goes!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Senior Member

Hi there,

 

It's currently possible to define an authentication method policy so that FIDO2 security keys can only be used by a select number of users or groups (that is, in the Azure portal under Security > Authentication methods > FIDO2 Security Key > FIDO2 Security Key settings).

 

For a user who is eligible for an Azure AD admin role which is managed via PIM, if MFA is required to activate that role, is it possible to limit the choice of MFA to only a FIDO2 security key?

 

This would be for a scenario where a standard user sign-in to the Azure portal would be secured using MFA (for example, using the Microsoft Authenticator), but activating an admin role through PIM would require the use of a FIDO2 security key instead.

 

My Sign-Ins ( https://mysignins.microsoft.com/security-info ) lets you select a default sign-in method under Security info (for example, Microsoft Authenticator - notification, or Authenticator app or hardware token - code), but I can't see a setting in the Azure portal to specify a FIDO2 security key as a default or preferred MFA method.

 

Has anyone had success in making a FIDO2 security key the default MFA method, in particular when working with PIM?

1 Reply

@RGFUK Interesting question. The enabling of PIM and requiring MFA for activation calls for Azure MFA which is configured by you the admin, i.e. the options under Service settings Which in turn are also the options being available to you in the security info drop-down you're referring to. I don't work setting up PIM as a feature (must have that said) but AFAIK you cannot separate MFA with "must use authenticator app here and must use FIDO2 here".

 

FIDO2 satisfies MFA while not being supported as a true second factor. With that in mind you should be able to use FIDO2 as the verification method (hardware token) when enabling a PIM role and requiring Azure MFA as both Authenticator app and FIDO2 are used for sign-in and strong authentication.

 

Let me know how it goes!