Skip to content

Commit 1288894

Browse files
Merge pull request #224575 from msmimart/mm-idp-perms
[EIXD] Add roles required for configuring SAML/Ws-Fed, Google, and Facebook IdPs
2 parents aa4d27c + 1dcbd00 commit 1288894

File tree

4 files changed

+26
-17
lines changed

4 files changed

+26
-17
lines changed

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

Lines changed: 15 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: B2B
88
ms.topic: how-to
9-
ms.date: 10/24/2022
9+
ms.date: 01/20/2023
1010

1111
ms.author: mimart
1212
author: msmimart
@@ -96,6 +96,10 @@ Setting up SAML/WS-Fed IdP federation doesn’t change the authentication method
9696

9797
Currently, the Azure AD SAML/WS-Fed federation feature doesn't support sending a signed authentication token to the SAML identity provider.
9898

99+
**What permissions are required to configure a SAML/Ws-Fed identity provider?**
100+
101+
You need to be an [External Identity Provider Administrator](../roles/permissions-reference.md#external-identity-provider-administrator) or a [Global Administrator](../roles/permissions-reference.md#global-administrator) in your Azure AD tenant to configure a SAML/Ws-Fed identity provider.
102+
99103
## Step 1: Determine if the partner needs to update their DNS text records
100104

101105
Depending on the partner's IdP, the partner might need to update their DNS records to enable federation with you. Use the following steps to determine if DNS updates are needed.
@@ -187,9 +191,10 @@ Next, you'll configure federation with the IdP configured in step 1 in Azure AD.
187191

188192
### To configure federation in the Azure AD portal
189193

190-
1. Go to the [Azure portal](https://portal.azure.com/). In the left pane, select **Azure Active Directory**.
191-
2. Select **External Identities** > **All identity providers**.
192-
3. Select **New SAML/WS-Fed IdP**.
194+
1. Sign in to the [Azure portal](https://portal.azure.com/) as an External Identity Provider Administrator or a Global Administrator.
195+
2. In the left pane, select **Azure Active Directory**.
196+
3. Select **External Identities** > **All identity providers**.
197+
4. Select **New SAML/WS-Fed IdP**.
193198

194199
![Screenshot showing button for adding a new SAML or WS-Fed IdP.](media/direct-federation/new-saml-wsfed-idp.png)
195200

@@ -238,11 +243,12 @@ On the **All identity providers** page, you can view the list of SAML/WS-Fed ide
238243

239244
![Screenshot showing an identity provider in the SAML WS-Fed list](media/direct-federation/new-saml-wsfed-idp-list-multi.png)
240245

241-
1. Go to the [Azure portal](https://portal.azure.com/). In the left pane, select **Azure Active Directory**.
242-
1. Select **External Identities**.
243-
1. Select **All identity providers**.
244-
1. Under **SAML/WS-Fed identity providers**, scroll to an identity provider in the list or use the search box.
245-
1. To update the certificate or modify configuration details:
246+
1. Sign in to the [Azure portal](https://portal.azure.com) as an External Identity Provider Administrator or a Global Administrator.
247+
2. In the left pane, select **Azure Active Directory**.
248+
3. Select **External Identities**.
249+
4. Select **All identity providers**.
250+
5. Under **SAML/WS-Fed identity providers**, scroll to an identity provider in the list or use the search box.
251+
6. To update the certificate or modify configuration details:
246252
- In the **Configuration** column for the identity provider, select the **Edit** link.
247253
- On the configuration page, modify any of the following details:
248254
- **Display name** - Display name for the partner's organization.

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

Lines changed: 2 additions & 2 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: how-to
10-
ms.date: 01/06/2023
10+
ms.date: 01/20/2023
1111

1212
ms.author: mimart
1313
author: msmimart
@@ -63,7 +63,7 @@ To use a Facebook account as an [identity provider](identity-providers.md), you
6363
Now you'll set the Facebook client ID and client secret, either by entering it in the Azure AD portal or by using PowerShell. You can test your Facebook configuration by signing up via a user flow on an app enabled for self-service sign-up.
6464

6565
### To configure Facebook federation in the Azure AD portal
66-
1. Sign in to the [Azure portal](https://portal.azure.com) as the global administrator of your Azure AD tenant.
66+
1. Sign in to the [Azure portal](https://portal.azure.com) as an External Identity Provider Administrator or a Global Administrator.
6767
2. Under **Azure services**, select **Azure Active Directory**.
6868
3. In the left menu, select **External Identities**.
6969
4. Select **All identity providers**, then select **Facebook**.

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

Lines changed: 6 additions & 5 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: how-to
10-
ms.date: 07/12/2022
10+
ms.date: 01/20/2023
1111

1212
ms.author: mimart
1313
author: msmimart
@@ -191,10 +191,11 @@ First, create a new project in the Google Developers Console to obtain a client
191191
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.
192192

193193
**To configure Google federation in the Azure portal**
194-
1. Go to the [Azure portal](https://portal.azure.com). On the left pane, select **Azure Active Directory**.
195-
2. Select **External Identities**.
196-
3. Select **All identity providers**, and then select the **Google** button.
197-
4. Enter the client ID and client secret you obtained earlier. Select **Save**:
194+
1. Sign in to the [Azure portal](https://portal.azure.com) as an External Identity Provider Administrator or a Global Administrator.
195+
2. In the left pane, select **Azure Active Directory**.
196+
3. Select **External Identities**.
197+
4. Select **All identity providers**, and then select the **Google** button.
198+
5. Enter the client ID and client secret you obtained earlier. Select **Save**:
198199

199200
![Screenshot that shows the Add Google identity provider page.](media/google-federation/google-identity-provider.png)
200201

articles/active-directory/external-identities/identity-providers.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: active-directory
55
ms.service: active-directory
66
ms.subservice: B2B
77
ms.topic: conceptual
8-
ms.date: 09/14/2022
8+
ms.date: 01/20/2023
99

1010
ms.author: mimart
1111
author: msmimart
@@ -39,6 +39,8 @@ External Identities offers a variety of identity providers.
3939
> [!NOTE]
4040
> Federated SAML/WS-Fed IdPs can't be used in your self-service sign-up user flows.
4141
42+
To configure federation with Google, Facebook, or a SAML/Ws-Fed identity provider, you'll need to be an [External Identity Provider Administrator](../roles/permissions-reference.md#external-identity-provider-administrator) or a [Global Administrator](../roles/permissions-reference.md#global-administrator) in your Azure AD tenant.
43+
4244
## Adding social identity providers
4345

4446
Azure AD is enabled by default for self-service sign-up, so users always have the option of signing up using an Azure AD account. However, you can enable other identity providers, including social identity providers like Google or Facebook. To set up social identity providers in your Azure AD tenant, you'll create an application at the identity provider and configure credentials. You'll obtain a client or app ID and a client or app secret, which you can then add to your Azure AD tenant.

0 commit comments

Comments
 (0)