Skip to content

Commit 9aa9c3b

Browse files
authored
Merge pull request #106665 from msmimart/mm-42233
[B2B] Google federation - revise per updated Google Project UI
2 parents 3e741e9 + 192b62a commit 9aa9c3b

File tree

3 files changed

+9
-10
lines changed

3 files changed

+9
-10
lines changed

articles/active-directory/b2b/google-federation.md

Lines changed: 9 additions & 10 deletions
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: conceptual
10-
ms.date: 11/1/2019
10+
ms.date: 03/05/2020
1111

1212
ms.author: mimart
1313
author: msmimart
@@ -53,25 +53,24 @@ First, create a new project in the Google Developers Console to obtain a client
5353

5454
![Screenshot showing a New project page for Google](media/google-federation/google-new-project.png)
5555

56-
3. Make sure your new project is selected in the project menu. Then open the menu in the upper left and select **APIs & Services** > **Credentials**.
56+
3. Make sure your new project is selected in the project menu. Then under **APIs & Services**, select **OAuth consent screen**.
5757

58-
![Screenshot showing the Google API credentials option](media/google-federation/google-api.png)
59-
60-
4. Choose the **OAuth consent screen** tab and enter an **Application name**. (Leave the other settings.)
58+
4. Select **External**, and then select **Create**.
59+
5. On the **OAuth consent screen**, enter an **Application name**. (Leave the other settings.)
6160

6261
![Screenshot showing the Google OAuth consent screen option](media/google-federation/google-oauth-consent-screen.png)
6362

64-
5. Scroll to the **Authorized domains** section and enter microsoftonline.com.
63+
6. Scroll to the **Authorized domains** section and enter microsoftonline.com.
6564

6665
![Screenshot showing the Authorized domains section](media/google-federation/google-oauth-authorized-domains.png)
6766

68-
6. Select **Save**.
67+
7. Select **Save**.
6968

70-
7. Choose the **Credentials** tab. In the **Create credentials** menu, choose **OAuth client ID**.
69+
8. Choose **Credentials**. In the **Create credentials** menu, choose **OAuth client ID**.
7170

7271
![Screenshot showing the Google APIs create credentials option](media/google-federation/google-api-credentials.png)
7372

74-
8. Under **Application type**, choose **Web application**, and then under **Authorized redirect URIs**, enter the following URIs:
73+
9. Under **Application type**, choose **Web application**, and then under **Authorized redirect URIs**, enter the following URIs:
7574
- `https://login.microsoftonline.com`
7675
- `https://login.microsoftonline.com/te/<directory id>/oauth2/authresp` <br>(where `<directory id>` is your directory ID)
7776

@@ -80,7 +79,7 @@ First, create a new project in the Google Developers Console to obtain a client
8079
8180
![Screenshot showing the Authorized redirect URIs section](media/google-federation/google-create-oauth-client-id.png)
8281

83-
9. Select **Create**. Copy the client ID and client secret, which you'll use when you add the identity provider in the Azure AD portal.
82+
10. Select **Create**. Copy the client ID and client secret, which you'll use when you add the identity provider in the Azure AD portal.
8483

8584
![Screenshot showing the OAuth client ID and client secret](media/google-federation/google-auth-client-id-secret.png)
8685

Binary file not shown.
-3.12 KB
Loading

0 commit comments

Comments
 (0)