During an Windows 10 / MDM / Syntaro project we faced an issue regarding MFA (Multi Factor Authentication). The customer was a local school where not all students have a smartphone during the class. Because of this, we had the requirement to disable MFA in his environment for Azure AD Joins.
Our first idea was to simply disabled the requirement for MFA in the Azure AD Device Settings blade :). But we experienced that the problem was not solved with this change. The Azure AD Join still triggers an MFA.
This means, that this is not the single setting, which will impact this behavior. We did some researches and found the feature, which triggers the MFA: Windows Hello for Business. The customer has enabled the automatic enrollment to Intune and configured there the Windows Hello for Business settings. To configure a device for Windows Hello an MFA is required. So, we had to disable Windows Hello for business and the MFA Requirement on Azure AD Join. Starting from this moment an Azure AD Join no longer requires an MFA.
I hope this post will help you in your future projects with the great EMS tools.
Latest posts by Thomas Kurth (see all)
- Active Setup is not Supported for Custom Use! Active Setup entries lost during Windows 10 Inplace upgrade! - July 6, 2018
- Allow changing Windows Language during device Enrollment - July 4, 2018
- Advanced publish of internal Webapp with specific Homepage to Internet with Azure AD Application Proxy - June 22, 2018