As an admin, you can set up user provisioning and single sign-on (SSO) between a Microsoft Entra ID tenant and your Google Workspace or Cloud Identity account. Then, your users can sign in to an Microsoft Entra ID authentication page instead of the Google sign-in screen on their ChromeOS devices.
Security Assertion Markup Language (SAML) single sign-on (SSO) support for ChromeOS devices allows users to sign in to a device with the same authentication mechanisms that you use within the rest of your organization. Their passwords can remain within your organization's Identity Provider (IdP). Signing in is very similar to signing in to a Google Workspace account from a browser via SAML SSO. However, because a user is signing in to a device, there are several additional considerations.
Before you begin
- Your domain is configured in Microsoft Entra ID and Google (Workspace or Cloud Identity).
- User account names are the same for Microsoft Entra ID and Google. The Microsoft Entra ID directory holds your domain as a registered subdomain.
- These steps do not require a local federation, such as Active Directory Federation Services (ADFS). However, they do rely on the equivalent cloud based service bundled with the Microsoft Entra ID Free tier.
How to
- Sign in to the Microsoft Azure portal.
- In the search box at the top, enter enterprise application and select it from the list of search results.
- At the top of the Enterprise applications pane, click New application.
- Under Cloud platforms, click Google Cloud Platform.
- Click Google Cloud/G Suite Connector by Microsoft.
- For Name, enter Google Cloud/G Suite Connector by Microsoft.
- Click Create.
Still in the Microsoft Azure portal:
- On the left, under Manage, click Users and groups. Or, on the Overview page, under Getting started, click Assign users and groups.
- At the top of the Users and groups pane, click Add user/group.
- In the Add Assignment pane on the left, under Users, click None selected.
- In the Users pane, select the user that you want.
- Click Select.
- In the Add Assignment pane, click Assign.
Still in the Microsoft Azure portal:
- On the left, under Manage, click Single sign-on.
- Select a single sign-on method. Click SAML.
- On the SAML-based Sign-on page, go to Basic SAML Configuration.
- Click Edit.
- Configure Identifier (Entity ID). Add URLs:
- google.com/a/yourdomain.com
- https://google.com/a/yourdomain.com
- Configure Reply URL (Assertion Consumer Service URL):
- Add URLs:
- https://www.google.com/acs
- https://www.google.com/a/yourdomain.com/acs
- Set the default:
- Next to https://www.google.com/a/yourdomain.com/acs, check the Default box.
- Add URLs:
- Configure Sign on URL. Add URL:
- https://www.google.com/a/yourdomain.com/ServiceLogin?continue=https://mail.google.com
- Click Save.
- Download the Base64 version of the certificate:
- Still on the SAML-based Sign-on page, go to SAML Signing Certificate.
- Next to Certificate (Base64), click Download.
- Gather the information that you'll need to configure the Google Cloud / G Suite Connector by Microsoft application to link with Microsoft Entra ID:
- Still on the SAML-based Sign-on page, go to Set up Google Cloud / G Suite Connector by Microsoft.
- Copy the URLs:
- Login URL—The page where users sign in to your system and Google Workspace.
- Logout URL—The page where users are redirected to after signing out.
Configure third-party IdP settings
-
Sign in to your Google Admin console.
Sign in using your administrator account (does not end in @gmail.com).
-
In the Admin console, go to Menu SecurityOverview.
- Click Set up single sign-on (SSO) with a third party IdP.
- Click Add SSO profile.
- Check the Set up SSO with third-party identity provider box.
- Enter your third-party IdP URLs:
- Click Replace certificate.
- Select the file that you want to use and click Open.
- Click the Use a domain specific issuer box.
- For Change password URL, enter the URL:
- https://account.activedirectory.windowsazure.com/changepassword.aspx
- Click Save.
Configure user settings
Still in the Admin console:
-
In the Admin console, go to Menu DevicesChromeSettings. The User & browser settings page opens by default.
If you signed up for Chrome Enterprise Core, go to Menu Chrome browserSettings.
-
To apply the setting to all users and enrolled browsers, leave the top organizational unit selected. Otherwise, select a child organizational unit.
- Go to Security.
- For Single sign-on, select Enable SAML-based single sign-on for Chrome devices.
- (Optional) For SAML single sign-on login frequency, enter a value that is smaller than the password expiration time. For details about the setting, see Set Chrome policies for users or browsers.
-
Click Save. Or, you might click Override for an organizational unit.
To later restore the inherited value, click Inherit.
Configure device settings
Still in the Admin console:
- At the top of the page, click Device settings. Or, from the Admin console Home page, go to DevicesChromeSettingsDevice.
- To apply the setting to all devices, leave the top organizational unit selected. Otherwise, select a child organizational unit.
- Go to Sign-in settings.
- For Single sign-on IdP redirection, select Allow users to go directly to SAML SSO IdP page. For details about the setting, see Set Chrome device policies.
- For Single sign-on cookie behavior, select Enable transfer of SAML SSO cookies into user session during sign-in. For details about the setting, see Set Chrome device policies.
- Click Save.
- Turn on a managed ChromeOS device.
- On the Sign in to your Chromebook page, click Next.
- On the Microsoft sign-in page, enter your AD username.
- Click Next.
- Enter your password.
- Click Sign in.
- To stay signed in and access the user session, click Yes.
When you signed up for Cloud Identity or Google Workspace, you created a super admin account. While you could use it for Microsoft Entra ID, we recommend that you create a separate super admin account that is used exclusively by Microsoft Entra ID.
Create user
-
Sign in to your Google Admin console.
Sign in using your administrator account (does not end in @gmail.com).
- In the Admin console, go to Menu DirectoryUsers.
- At the top of the page, click Add new user.
- Enter account information. For details, see Add an account for a new user.
- Click Add new user.
- To finish adding the new user, click Done.
Make user a super admin
Still in the Admin console:
- In the Admin console, go to Menu DirectoryUsers.
- In the Users list, find the new user that you just created.
- Click the user’s name to open their account page.
- Click Admin roles and privileges.
- Click Assign roles.
- Next to the Super Admin role, click the slider so it's marked Assigned.
- Click Save.
Tip: Have the new administrator add recovery options to their account.
The user typically becomes an admin within a few minutes. However, it can take up to 24 hours.
Manage user account provisioning
- Sign in to the Microsoft Azure portal.
- In the search box at the top, enter enterprise application and select it from the list of search results.
- Search for and click Google Cloud / G Suite Connector by Microsoft.
- On the left, under Manage, click Provisioning.
- Click Get started.
- For Provisioning mode, select Automatic.
- Click Admin Credentials.
- Click Authorize.
- Sign in using the new super admin account that you just created.
- Click Allow to confirm access to the Cloud Identity API.
- Under Admin Credentials, click Test Connection. You’ll see a message letting you know if you’re authorized to enable provisioning.
- (Optional) Under Mappings, configure user or group provisioning. We recommend that you use the default setting.
- Click Save.
- At the top of the Provisioning page, click Start provisioning.
- Wait until sync completes.
Related topics
- Configure SAML single sign-on for ChromeOS devices
- Micrsoft Entra ID user provisioning and single sign-on
- Tutorial: Micrsoft Entra SSO integration with Google Cloud / G Suite Connector by Microsoft
Google and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.