Office 365 cloud application

Using Security Assertion Markup Language (SAML), your users can use their Google Cloud credentials to sign in to enterprise-cloud applications.

Set up SSO via SAML for Office 365

Here's how to set up Single Sign-On (SSO) via SAML for the Office 365® application.

Step 1: Set up Office 365 as a SAML 2.0 service provider (SP)
  1. Sign in to your Google Admin console.

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

  2. From the Admin console dashboard, go to Security and then Set up single sign-on (SSO).

    To see Security, you might have to click More controls at the bottom. 

  3. Click the Download button to download the Google IdP metadata and the X.509 Certificate.
  4. In a new browser tab, log into your Office 365 application as an administrator.
  5. Set up a federation of your On-Premises Active Directory and Azure Active Directory.

    You must set up the federation to execute the Active Directory PowerShell commands. Refer to the Microsoft Active Directory documentation online for more information.

  6. Configure the IdP certificates and set the URL using the Active Directory PowerShell on your federated Active Directory Domain. 
  7. Proceed to the next section to set up Google as a SAML identity provider (IdP).
Step 2: Use the pre configured Office 365 cloud application to set up Google as a SAML identity provider (IdP)
  1. In a new browser tab, sign in to your Admin console as a super administrator.
  2. Click Apps SAML apps.
  3. Click the plus (+) icon in the bottom corner.
  4. Select the Office 365 item from the list. The values on the Google IDP Information page automatically populate.
  5. There are two ways to collect the service provider Setup information: you can copy the Entity ID and the Single Sign-On URL field values and download the X.509 Certificate, paste them into the appropriate service provider Setup fields, and then click Next, or you can download the IDP metadata, upload it into the appropriate service provider Setup fields, and then  come back to the admin console and click Next.
  6. In the Basic application information window, the Application name and Description values automatically populate.
  7. Click Next.
Step 3: Enter the Office 365 specific service provider details in Google Admin console
  1. In the Service Provider Details section, enter the following URLs into the Entity IDACS URL, and Start URL fields:
            ACS URL: https://login.microsoftonline.com/login.srf
            Entity ID: urn:federation:MicrosoftOnline
            Start URL: Empty
  2. Check Signed Response.
    When the Signed Response checkbox is unchecked, only the assertion is signed. When the Signed Response checkbox is checked, the entire response is signed.
  3. The default Name ID must match the requirements set by ImmutableID. Use an Active Directory sync to configure this. Multi-value input is not supported.
  4. Set the NameID format to “persistent”.
  5. Click Next.
  6. Click Add new mapping and map the attribute value "IDPEmail" to Basic Information > Primary Email
  7. In the drop-down list, select the Category and User attribute to map the attribute from the Google profile.
  8. Click Finish.
Step 4: Enable the Office 365 app
  1. Sign in to your Admin console.
  2. Go to Apps SAML apps.
  3. Select Office 365.
  4. At the top of the gray box, click More Settingsand choose:
    • On for everyone to turn on the service for all users (click again to confirm).
    • Off to turn off the service for all users (click again to confirm).
    • On for some organizations to change the setting only for some users.
  5. Ensure that your Office 365 user account email IDs match those in your Google domain.
Step 5: Verify that the SSO is working between Google and Office 365
  1. Open https://login.microsoftonline.com/.
    You should be automatically redirected to the Google sign in page.
  2. Enter your sign in credentials.
  3. After your sign in credentials are authenticated you will be automatically redirected back to Office 365.
Step 6: Set up user provisioning
Was this article helpful?
How can we improve it?