Device registration and security/MFA registration

%3CLINGO-SUB%20id%3D%22lingo-sub-1261885%22%20slang%3D%22en-US%22%3ERe%3A%20Device%20registration%20and%20security%2FMFA%20registration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1261885%22%20slang%3D%22en-US%22%3EHi%20Bart%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20think%20this%20particular%20setting%20cab%20controlled%20from%20different%20spots%2C%20like%20Identity%20Protection%2C%20Conditional%20Access%20or%20All%20tenant%20(you%20showed%20in%20your%20Screenshot).%3CBR%20%2F%3E%3CBR%20%2F%3ECould%20you%20check%20in%20Intune%20Profile%20or%20Conditional%20Access%3F%3CBR%20%2F%3E%3CBR%20%2F%3EMoe%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fidentity-protection%2Fhowto-identity-protection-configure-mfa-policy%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fidentity-protection%2Fhowto-identity-protection-configure-mfa-policy%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmem%2Fintune%2Fenrollment%2Fmulti-factor-authentication%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmem%2Fintune%2Fenrollment%2Fmulti-factor-authentication%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1262155%22%20slang%3D%22en-US%22%3ERe%3A%20Device%20registration%20and%20security%2FMFA%20registration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1262155%22%20slang%3D%22en-US%22%3EBy%20default%20I%20don%E2%80%99t%20think%20you%20should%20get%20MFA%20when%20peforming%20Azure%20AD%20registration%20of%20a%20device.%20I%20think%20this%20because%20(as%20another%20poster%20mentioned)%20either%20Conditional%20Access%2C%20or%20the%20fact%20the%20user%20is%20enabled%20and%20enforced%20for%20MFA%20(portal.azure.com%20%26gt%3B%20Azure%20Active%20Directory%20%26gt%3B%20Users%20%26gt%3B%20Multi%20Factor%20Authentication)%20or%20even%20Security%20Defaults%20enabled.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20not%20found%20any%20way%20to%20disable%20this%20behaviour%20of%20BYOD%20when%20using%20new%20versions%20of%20Office.%20The%20only%20way%20to%20skip%20Azure%20AD%20Registration%20is%20to%20let%20the%20user%20cancel%20the%20wizard%20of%20registration.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20only%20downside%20I%20see%20is%20that%20you%20get%20a%20bunch%20of%20%E2%80%9Dunknown%20personal%20devices%E2%80%9D%20in%20your%20Azure%20AD.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1264219%22%20slang%3D%22en-US%22%3ERe%3A%20Device%20registration%20and%20security%2FMFA%20registration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1264219%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20the%20suggestions%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F503735%22%20target%3D%22_blank%22%3E%40Moe_Kinani%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F19218%22%20target%3D%22_blank%22%3E%40Jonas%20Back%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20defined%20a%20few%20conditional%20access%20policies%2C%20but%20none%20of%20them%20requires%20mfa%20registration.%20There%20is%20only%20a%20limited%20group%20of%20users%20required%20to%20use%20mfa%20to%20log%20on%2C%20that's%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20specific%20policies%20are%20defined%20in%20intune.%26nbsp%3B%3C%2FP%3E%3CP%3EUser%20based%20MFA%20is%20disabled%20for%20all%20our%20users.%3C%2FP%3E%3CP%3EMFA%20registration%20in%20Azure%20Identity%20protection%20is%20also%20disabled.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMaybe%20I%20should%20open%20a%20support%20ticket.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBart%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1264506%22%20slang%3D%22en-US%22%3ERe%3A%20Device%20registration%20and%20security%2FMFA%20registration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1264506%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F7187%22%20target%3D%22_blank%22%3E%40bart%20vermeersch%3C%2FA%3E%26nbsp%3BWhat%20does%20Azure%20AD%20Sign-in%20logs%20say%3F%20This%20might%20tell%20you%20why%20MFA%20is%20required.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1265606%22%20slang%3D%22en-US%22%3ERe%3A%20Device%20registration%20and%20security%2FMFA%20registration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1265606%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F6201%22%20target%3D%22_blank%22%3E%40Jonas%20Back%3C%2FA%3E%26nbsp%3Bnot%20really%2C%20it's%20not%20mfa%20that%20is%20required%2C%20it's%20the%20%3CSTRONG%3Emfa%20registration%3C%2FSTRONG%3E%20that%20is%20requested.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20always%20see%20a%20user%20registering%20his%20device%20(eg%20when%20configuring%20Teams%20or%20Outlook)%20followed%20by%20mfa%20registration%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Aantekening%202020-03-30%20195725.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F180670iFF2D194443F294A1%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Aantekening%202020-03-30%20195725.png%22%20alt%3D%22Aantekening%202020-03-30%20195725.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1259993%22%20slang%3D%22en-US%22%3EDevice%20registration%20and%20security%2FMFA%20registration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1259993%22%20slang%3D%22en-US%22%3E%3CP%3EI%20would%20like%20to%20better%20understand%20how%20the%20AAD%20device%20registration%20works.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20AAD%20we%20see%20byods%20being%20registred%20in%20AAD%20when%20installing%20configuring%20Outlook%20or%20Teams.%20Is%20registration%20also%20triggered%20when%20configuring%20other%20applications%20(eg%20OneDrive%2C%20Word...)%3F%26nbsp%3BIs%20this%20a%20setting%20we%20can%20configure%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUpon%20registration%20of%20their%20byod%20device%2C%20users%20are%20requested%20for%20additional%20security%20registration%20(mfa).%20Is%20this%20a%20setting%20we%20can%20configure%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22Require%20Multi-Factor%20auth%20to%20join%20devices%22%20in%20AAD%20is%20set%20to%20NO.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Annotation%202020-03-27%20205151.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F180023i7348C10D7DF7A515%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Annotation%202020-03-27%20205151.png%22%20alt%3D%22Annotation%202020-03-27%20205151.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1259993%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIdentity%20Management%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1266940%22%20slang%3D%22en-US%22%3ERe%3A%20Device%20registration%20and%20security%2FMFA%20registration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1266940%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F7187%22%20target%3D%22_blank%22%3E%40bart%20vermeersch%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EUnless%20the%20user%20OOBE%20joined%20their%20own%20device%20at%20the%20time%20of%20setup.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EBYOD%20or%20connecting%20to%20Outlook%20or%20Teams%20on%20devices%20usually%20show%20up%20as%20Azure%20AD%20registered%20and%20not%20as%20Azure%20AD%20Joined.%26nbsp%3B%20%26nbsp%3BIf%20MAM%20enrollment%20is%20enabled.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20you%20enabled%20MAM%20enrollment%20most%20of%20the%20time%20those%20policies%20are%20App%20protection%20policies%20for%20Windows%2010%20without%20enrollment.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EConditional%20Access%20can%20still%20be%20enforced%20for%20MFA%20on%20non%20domain%20joined%20devices.%20%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Super Contributor

I would like to better understand how the AAD device registration works.

 

In AAD we see byods being registred in AAD when installing configuring Outlook or Teams. Is registration also triggered when configuring other applications (eg OneDrive, Word...)? Is this a setting we can configure?

 

Upon registration of their byod device, users are requested for additional security registration (mfa). Is this a setting we can configure?

 

"Require Multi-Factor auth to join devices" in AAD is set to NO.

 

Annotation 2020-03-27 205151.png

 

Thanks!

 

8 Replies
Highlighted
Hi Bart,

I think this particular setting cab controlled from different spots, like Identity Protection, Conditional Access or All tenant (you showed in your Screenshot).

Could you check in Intune Profile or Conditional Access?

Moe

https://docs.microsoft.com/en-us/azure/active-directory/identity-protection/howto-identity-protectio...

https://docs.microsoft.com/en-us/mem/intune/enrollment/multi-factor-authentication
Highlighted
By default I don’t think you should get MFA when peforming Azure AD registration of a device. I think this because (as another poster mentioned) either Conditional Access, or the fact the user is enabled and enforced for MFA (portal.azure.com > Azure Active Directory > Users > Multi Factor Authentication) or even Security Defaults enabled.

I have not found any way to disable this behaviour of BYOD when using new versions of Office. The only way to skip Azure AD Registration is to let the user cancel the wizard of registration.

The only downside I see is that you get a bunch of ”unknown personal devices” in your Azure AD.
Highlighted

Thank you for the suggestions, @Moe_Kinani and @Jonas Back 

 

We have defined a few conditional access policies, but none of them requires mfa registration. There is only a limited group of users required to use mfa to log on, that's it.

 

No specific policies are defined in intune. 

User based MFA is disabled for all our users.

MFA registration in Azure Identity protection is also disabled.

 

Maybe I should open a support ticket.

 

Bart

Highlighted

@bart vermeersch What does Azure AD Sign-in logs say? This might tell you why MFA is required.

Highlighted

@Jonas Back not really, it's not mfa that is required, it's the mfa registration that is requested.

 

We always see a user registering his device (eg when configuring Teams or Outlook) followed by mfa registration:

 Aantekening 2020-03-30 195725.png

Highlighted

@bart vermeersch 

 

Unless the user OOBE joined their own device at the time of setup.

BYOD or connecting to Outlook or Teams on devices usually show up as Azure AD registered and not as Azure AD Joined.   If MAM enrollment is enabled.

 

If you enabled MAM enrollment most of the time those policies are App protection policies for Windows 10 without enrollment. 

 

Conditional Access can still be enforced for MFA on non domain joined devices.

Highlighted

@bart vermeerschHave you ever sorted out what is causing this MFA registration request?  We are seeing the same thing and this thread seems to be the only place I can find any mention of this behavior.

Highlighted

@bflick I think I do. The key thing is a user is not using his password to log in to his device (but using PIN, Windows Hello...) , to be able to perform SSO towards Azure services, this isn't sufficient, you need a password or some additional factor. This triggers device registration. It is the device registration that needs the mfa (not yet sure why exactly).

 

So to be tested, if you use password to log in to Windows 10 you will not start the device/mfa registration, but SSO will be possible. If you do not use a password to log in to Windows 10 and skip the device/mfa registration you won't get SSO for Teams and Outlook.  

 

If the user logs into the machine via a new generation credential (PIN, Hello, ..) that is not already included in the existing PRT or there is no existing PRT on the device then the Azure AD MAM plugin will trigger device registration via a request which includes the “amr_values=ngcmfa” parameter and this will be the source of the MFA.

 

From MS support

 

  • The user is connecting from an Azure AD registered device via a PRT which only contains the password claim for the registration authentication method used(Registration_amr). This means that the device was previously workplace joined to Azure AD without MFA being required as per your current configuration in which MFA is not required. This evaluation is done based on the device authentication request sent to Azure AD.
  • The MFA requirement is enforced by the Azure AD WAM plugin(Microsoft Authentication broker) via the following request parameters “amr_values=ngcmfa”. This is occurring because the user signed into the machine using a new generation credential like a PIN or fingerprint. At this time, because the user signed into the Windows device via a different authentication method than the one included in the PRT(which was password), the authentication broker forces the user to configure MFA so that it can refresh the existing PRT record on the device with the new authentication method used.

Considering the above information, this behavior is by design and to be expected due to the PRT token refresh process and you can find it better detailed in the following articles:

 

How is a PRT renewed? - https://docs.microsoft.com/en-us/azure/active-directory/devices/concept-primary-refresh-token#how-is...

When does a PRT get an MFA claim? - https://docs.microsoft.com/en-us/azure/active-directory/devices/concept-primary-refresh-token#when-d...

 

Regards,

 

Bart