

This can have other adverse impacts, like the user appearing to be at risk in Azure AD Identity Protection. For example, ROPC sign-ins will fail if there are Conditional Access policies that require MFA or device compliance in place, even if the user’s username and password were correct. ROPC is not user interactive in a web browser, so it has limitations. These tools use the OAuth 2.0 Resource Owner Password Credentials (ROPC, sometimes called ROPG) grant flow to validate username and password credentials against Azure AD. Many customers also use tools like Jamf Connect that can validate credentials against an IDP rather than on-premises Active Directory.

To ensure that you have the most optimal configuration, you need to understand what your users are seeing and experiencing with prompts. Over-prompting also impacts productivity, especially on devices like macOS where single sign-on (SSO) with Azure AD is not configured out of the box. This is because users can learn bad behaviors like blindly approving MFA requests and being easily phished. Over-prompting your users with frequent password screens and MFA requests can reduce the security posture of your organization.


Determine if you have a prompting problem. Now that we understand the basics, let’s look at the recommendations we have for macOS customers: 1. Microsoft provides a deployment guide for conditional access. In successful organizations, the Mac admins and the identity and access management (IAM) teams have ongoing conversations as they tweak and optimize their conditional access policies. If you are the person managing macOS devices in your organization, it is important for you to understand the conditional access policies in your environment, as they can greatly impact the experience of your macOS users.
