OK, Here's what I found out from my support case.Īs of August 2019, there are now two forms of MFA policy:Įnabled through the /usermanagement/multifactorverification.aspx page.Ģ. If they cannot come up with a way to make AD Connect work with MFA Enabled account, then I'm hoping that they will carve out an exception because they are telling partners that we will no longer be able to transaction with Microsoft if we are not 100% MFA enabled. I've opened a support case with the Partner Center, but hoping that someone has already figured out how to make this work.
I'm not finding any documentation from Microsoft for AD Connect to indicate that they support their own MFA-Compliant method of performing this. Then as part of the registration give it the "App Permission" of "Microsoft Graph" and the sub-permissions that it needs. With other applications (like Veeam for Office 365 for example) I would open: CSP partners are required to have MFA enabled on 100% of accounts, but Azure AD Connect does not seem to support the Azure AD Application Graph which would allow it to work with MFA Enabled?
0 kommentar(er)
