Skip to content

Commit 33d9334

Browse files
authored
Merge pull request #190325 from msmimart/mm-issue84946
[EXID] Google federation: add note regarding app verification per GitHub issue 84946
2 parents 351738d + aad6111 commit 33d9334

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/active-directory/external-identities/google-federation.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ services: active-directory
77
ms.service: active-directory
88
ms.subservice: B2B
99
ms.topic: how-to
10-
ms.date: 02/24/2022
10+
ms.date: 03/02/2022
1111

1212
ms.author: mimart
1313
author: msmimart
@@ -184,6 +184,9 @@ First, create a new project in the Google Developers Console to obtain a client
184184

185185
1. You can leave your project at a publishing status of **Testing** and add test users to the OAuth consent screen. Or you can select the **Publish app** button on the OAuth consent screen to make the app available to any user with a Google Account.
186186

187+
> [!NOTE]
188+
> In some cases, your app might require verification by Google (for example, if you update the application logo). For more information, see Google's [verification status help](https://support.google.com/cloud/answer/10311615#verification-status).
189+
187190
## Step 2: Configure Google federation in Azure AD
188191

189192
You'll now set the Google client ID and client secret. You can use the Azure portal or PowerShell to do so. Be sure to test your Google federation configuration by inviting yourself. Use a Gmail address and try to redeem the invitation with your invited Google account.

0 commit comments

Comments
 (0)