MicrosoftDocs
Does CloudAPAuthEnabled for Chrome 111 replace the requirement for Windows Accounts?
It seems like the CloudAPAuthEnabled feature of Chrome 111 can be used instead of deploying the Windows Accounts extension. Can you confirm and if confirmed by product group update the documentation and guidance?
More info here: https://chromeenterprise.google/policies/?policy=CloudAPAuthEnabled
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 625bb1b2-81fd-9804-c0b5-3cd2904decd9
- Version Independent ID: e4468b05-200e-24ae-75e9-29fb2b3a6ddc
- Content: Conditions in Conditional Access policy - Microsoft Entra
- Content Source: articles/active-directory/conditional-access/concept-conditional-access-conditions.md
- Service: active-directory
- Sub-service: conditional-access
- GitHub Login: @MicrosoftGuyJFlo
- Microsoft Alias: joflore
@JonesMikael
Thanks for your feedback! We will investigate and update as appropriate.
FWIW, the CloudAPAuthEnabled feature is working in my tenant for about 95% of Chrome 113.x (I don't have anybody on earlier Chrome versions to test) users. I see Managed and Compliant fields filled under Device Info for requests coming from Chrome browsers with this policy enabled. There are a few outliers where it is not working yet, but that seems to be the exception not the rule.
We appreciate this feedback! Glad to hear it is working for a majority of your users @Lauwnch.
Our engineering team is still evaluating the full breadth of testing and outlier scenarios before we update documentation.
