Setting up SSO

You can set up SSO with Google as your service provider in a number of ways, depending on your organization’s needs. Google Workspace supports both SAML-based and OIDC-based SSO. 

• SSO profiles, which contain the settings for your IdP, give you the flexibility to apply different SSO settings to different users in your organization. Create SAML-based profiles, or use the default Microsoft Entra OIDC profile which needs no configuration.
• After creating SSO profiles, assign profiles to organization units or groups to set the IdP for those users. You can also turn off SSO for specific organization units or groups.

If your users use domain-specific service URLs to access Google services (for example, https://mail.google.com/a/example.com), you can also manage how these URLs work with SSO.

If your organization needs conditional SSO redirection based on IP address, or SSO for super admins, you also have the option to configure the legacy SSO profile.

Set up SSO with SAML

Before you begin

To set up a SAML SSO profile, you’ll need some basic configuration from your IdP’s support team or documentation:

• Sign-in page URL  This is also known as the SSO URL or SAML 2.0 Endpoint (HTTP). This is where users sign in to your IdP.
• Sign-out page URL  Where the user lands after exiting the Google app or service.
• Change password URL  The page where SSO users will go to change their password (instead of changing their password with Google).
• Certificate  X.509 PEM certificate from your IdP. The certificate contains the public key which verifies sign-in from the IdP.

Certificate requirements

Create a SAML SSO profile

Follow these steps to create a third-party SSO profile. You can create up to 1000 profiles in your organization.

1. Sign in to your Google Admin console.

   Sign in using your administrator account (does not end in @gmail.com).

2. In the Admin console, go to Menu  SecurityAuthenticationSSO with third party IdP.
3. In SSO profiles, click Add SAML profile.
4. Enter a name for the profile.
5. (Optional) If you have an XML metadata file from your IdP, click upload XML file to provide IdP information, then continue with Step 8
6. Fill in the Sign-in page URL and other information obtained from your IdP.
7. Enter a change password URL for your IdP. Users will go to this URL (rather than the Google change password page) to reset their passwords.
8. Click Upload certificate to upload your certificate file.

   You can upload up to two certificates, giving you the option to rotate certificates when necessary.

9. Click Save.
10. In the SP Details section, copy and save the Entity ID and ACS URL. You’ll need these values to configure SSO with Google in your IdP admin control panel.
11. (Optional) If your IdP supports encrypting assertions, you can generate and share a certificate with your IdP to enable encryption. Each SAML SSO profile can have up to 2 SP certificates.
    1. Click the SP Details section to enter edit mode.
    2. Under SP certificate, click Generate certificate. (The certificate will display after you save it.)
    3. Click Save. The certificate name, expiration date, and contents are displayed.
    4. Use the buttons above a certificate to either copy the certificate contents or download as a file, then share the certificate with your IdP. 
    5. (Optional) If you need to rotate a certificate, return to SP Details and click Generate another certificate, then share the new certificate with your IdP. Once you’re sure your IdP is using the new one, you can delete the original certificate.

Configure your IdP

To configure your IdP to use this SSO profile, enter the information from the Service Provider (SP) Details section of the profile into the appropriate fields in your IdP SSO settings. Both the ACS URL and Entity ID are unique to this profile.

	Format
ACS URL	https://accounts.google.com/samlrp/metadata?acs={random string}
Entity ID	https://accounts.google.com/samlrp/metadata?rpid={random string}

 

Configure the legacy SSO profile

Migrate from legacy SAML to SSO profiles

If your organization is using the legacy SSO profile, we recommend migrating to SSO profiles, which offer several advantages including OIDC support, more modern APIs, and greater flexibility in applying SSO settings to your user groups. Learn more.

Set up SSO with OIDC

1. Make sure you’ve configured the following prerequisites for OIDC in your organization’s Microsoft Entra ID tenant:
   • The Microsoft Entra ID tenant needs to be domain verified.
   • End users must have Microsoft 365 licenses.
   • The username (primary email) of the Google Workspace admin assigning the SSO profile must match the primary email address of your Azure AD tenant admin account.
2. Follow the steps in Decide which users should use SSO to assign the pre-configured OIDC profile to selected organizational units/groups.

   Note: The Google Cloud Command Line Interface does not currently support reauthentication with OIDC.

If you have users within an organizational unit (for example in a sub-organizational unit) who don’t need SSO, you can also use assignments to turn SSO off for those users.

Decide which users should use SSO

Turn SSO on for an organizational unit or group by assigning an SSO profile and its associated IdP. Or, turn SSO off by assigning ‘None’ for the SSO profile. You can also apply a mixed SSO policy within an organizational unit or group, for example turning SSO on for the organizational unit as a whole, then turning it off for a sub-organizational unit. 

If you haven't created a profile, do that before continuing. Or, you can assign the preconfigured OIDC profile. 

1. Click Manage SSO profile assignments.
2. If this is your first time assigning the SSO profile, click Get started. Otherwise, click Manage assignments.
3. On the left, select the organizational unit or group to which you’re assigning the SSO profile.
   • If the SSO profile assignment for an organizational unit or group differs from your domain-wide profile assignment, an override warning appears when you select that organizational unit or group.
   • You can’t assign the SSO profile on a per-user basis. The Users view lets you check the setting for a specific user.
4. Choose an SSO profile assignment for the selected organizational unit or group:
   • To exclude the organizational unit or group from SSO, choose None. Users in the organizational unit or group will sign in directly with Google.
   • To assign another IdP to the organizational unit or group, choose Another SSO profile, then select the SSO profile from the dropdown list.
5. (SAML SSO profiles only) After selecting a SAML profile, choose a sign-in option for users who go directly to a Google service without first signing in to the SSO profile's third-party IdP. You can prompt users for their Google username, then redirect them to the IdP, or require users to enter their Google username and password. 

   Note: If you choose to require users to enter their Google username and password, the Change password URL setting for this SAML SSO profile (available at SSO Profile > IDP details) is ignored. This ensures that users are able to change their Google passwords as needed.

6. Click Save.
7. (Optional) Assign SSO profiles to other organizational units or groups as needed.

After you close the Manage SSO profile assignments card, you’ll see the updated assignments for organizational units and groups in the Manage SSO profile assignments section. 

Remove an SSO profile assignment

1. Click a group or organizational unit name to open its profile assignment settings.
2. Replace the existing assignment setting with the parent organization unit setting:
   • For organizational unit assignments—click Inherit.
   • For group assignments—click Unset.  

Note: Your top organizational unit is always present in the profile assignment list, even if the Profile is set to None.

See also

• Optional SSO settings and maintenance
• Troubleshoot SSO
• Multi-party approval for sensitive actions