Skip to content

Commit 30ed3d4

Browse files
committed
update
1 parent 18dcb35 commit 30ed3d4

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/active-directory/saas-apps/google-apps-tutorial.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
134134
| `https://google.com/a/<yourdomain.com>` |
135135

136136
> [!NOTE]
137-
> These values are not real. Update these values with the actual Sign-On URL and Identifier. G Suite doesn't provide Entity ID/Identifier value on Single Sign On configuration so when you switch off the domain specific issuer, the Identifier value will be `google.com`. If you turn this switch on, it will be `google.com/a/<yourdomainname.com>`. For more information contact [G Suite Client support team](https://www.google.com/contact/).
137+
> These values are not real. Update these values with the actual Sign-On URL and Identifier. G Suite doesn't provide Entity ID/Identifier value on Single Sign On configuration so when you switch off the **domain specific issuer** option in the G Suite configuration section, the Identifier value will be `google.com`. If you switch on **domain specific issuer** option in the G Suite configuration section, it will be `google.com/a/<yourdomainname.com>`. For more information contact [G Suite Client support team](https://www.google.com/contact/).
138138

139139
1. On the **Basic SAML Configuration** section, if you want to configure for the **Google Cloud Platform** perform the following steps:
140140

@@ -150,7 +150,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
150150
| `https://google.com/a/<yourdomain.com>` |
151151

152152
> [!NOTE]
153-
> These values are not real. Update these values with the actual Sign-On URL and Identifier. G Suite doesn't provide Entity ID/Identifier value on Single Sign On configuration so when you switch off the domain specific issuer, the Identifier value will be `google.com`. If you turn on the domain specific issuer, it will be `google.com/a/<yourdomainname.com>`. For more information contact [G Suite Client support team](https://www.google.com/contact/).
153+
> These values are not real. Update these values with the actual Sign-On URL and Identifier. G Suite doesn't provide Entity ID/Identifier value on Single Sign On configuration so when you switch off the **domain specific issuer** option in the G Suite configuration section, the Identifier value will be `google.com`. If you switch on **domain specific issuer** option in the G Suite configuration section, it will be `google.com/a/<yourdomainname.com>`. For more information contact [G Suite Client support team](https://www.google.com/contact/).
154154

155155
1. Your G Suite application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows an example for this. The default value of **Unique User Identifier** is **user.userprincipalname** but G Suite expects this to be mapped with the user's email address. For that you can use **user.mail** attribute from the list or use the appropriate attribute value based on your organization configuration.
156156

@@ -244,7 +244,7 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
244244

245245
e. In G Suite, for the **Verification certificate**, upload the certificate that you have downloaded from Azure portal.
246246

247-
f. Select **Use a domain specific issuer**.
247+
f. Select **Use a domain specific issuer**. If you select the **Use a domain specific issuer** option, enter `google.com` as **Identifier** value or if you do not select the **Use a domain specific issuer** option, then you need to enter domain specific **Identifier** like `https://google.com/a/<yourdomain.com>` in the **Basic SAML Configuration** section in the Azure AD.
248248

249249
g. Click **Save Changes**.
250250

0 commit comments

Comments
 (0)