The content below is taken from the original ( An easier way to integrate Chrome devices with Active Directory infrastructure), to continue reading please visit the site. Remember to respect the Author & Copyright.
In 2017, when we launched Active Directory integration as part of our Chrome Enterprise announcement, we aimed to help customers with on-premise infrastructure leverage the benefits of Chrome devices in their organizations. This integration allowed for use of Active Directory credentials to authenticate across devices, support for Android applications through managed Google Play, and management of user and device policies for IT admins via GPO. All of this can be done without additional infrastructure, minimizing disruption for users and IT alike.
With the release of Chrome Enterprise version 74, we have made Active Directory integration available to existing Chrome Enterprise customers who are already managing Chrome devices with cloud management on their domain currently. Administrators can now configure their Chrome devices to be managed by Active Directory or cloud management, without the need to set up a separate domain. We have also made it easy to switch management methods based on what is most appropriate for your organization at any given time. This can be completed with a simple administration policy.
In recent months, we’ve also have made other features available that offer IT admins greater control and access. These features include support for native Samba (SMB) file shares with kerberos authentication and app configuration via ADMX templates for Chrome apps and extensions that support policy for configuration.
Native integration with Active Directory is a good option for customers who wish to move incrementally towards a cloud-native solution while continuing to leverage their existing Active Directory environment. Use cases include:
Quick pilots: Deploy Chrome Enterprise quickly by integrating with existing identity, infrastructure, and management systems to pilot and test with minimal friction.
Supporting kerberos: Integrate easily with your existing infrastructure and applications that require kerberos authentication.
Handling on-prem: Support environments where an on-premises solution is required or preferred for managing devices, identity, and policy.
Centralizing management: Support mixed device deployments to manage all your devices from a single, Active Directory-based management solution
Current users of Active Directory integration will be automatically upgraded to the new version. This means all your existing devices will continue to function in the same way and administrators now have added flexibility to enable or disable Active Directory management based on your organization’s needs—no manual changes necessary.
To learn more, read ourhelp center article.