Skip to content

Commit 1ac218a

Browse files
authored
Merge pull request #251271 from garrodonnell/godonnell-update-portal-instructions
[B2B] Update steps from Azure portal to Entra admin center - 147894
2 parents fd69683 + d6a9da7 commit 1ac218a

11 files changed

+73
-94
lines changed

articles/active-directory/develop/howto-create-service-principal-portal.md

Lines changed: 6 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,8 @@ You must have sufficient permissions to register an application with your Azure
3838

3939
[!INCLUDE [portal updates](~/articles/active-directory/includes/portal-update.md)]
4040

41-
1. Sign in to the [Azure portal](https://portal.azure.com).
42-
1. Search for and Select **Azure Active Directory**.
43-
1. Select **App registrations**, then select **New registration**.
41+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
42+
1. Browse to **Identity** > **Applications** > **App registrations** then select **New registration**.
4443
1. Name the application, for example "example-app".
4544
1. Select a supported account type, which determines who can use the application.
4645
1. Under **Redirect URI**, select **Web** for the type of application you want to create. Enter the URI where the access token is sent to.
@@ -76,8 +75,7 @@ The next section shows how to get values that are needed when signing in program
7675

7776
When programmatically signing in, pass the tenant ID and the application ID in your authentication request. You also need a certificate or an authentication key. To obtain the directory (tenant) ID and application ID:
7877

79-
1. Search for select **Azure Active Directory**.
80-
1. From **App registrations** in Azure AD, select your application.
78+
1. Browse to **Identity** > **Applications** > **App registrations**, then select your application.
8179
1. On the app's overview page, copy the Directory (tenant) ID value and store it in your application code.
8280
1. Copy the Application (client) ID value and store it in your application code.
8381

@@ -89,8 +87,7 @@ There are two types of authentication available for service principals: password
8987

9088
To upload the certificate file:
9189

92-
1. Search for and select **Azure Active Directory**.
93-
1. From **App registrations** in Azure AD, select your application.
90+
1. Browse to **Identity** > **Applications** > **App registrations**, then select your application.
9491
1. Select **Certificates & secrets**.
9592
1. Select **Certificates**, then select **Upload certificate** and then select the certificate file to upload.
9693
1. Select **Add**. Once the certificate is uploaded, the thumbprint, start date, and expiration values are displayed.
@@ -114,8 +111,7 @@ Export this certificate to a file using the [Manage User Certificate](/dotnet/fr
114111

115112
To upload the certificate:
116113

117-
1. Search for and select **Azure Active Directory**.
118-
1. From **App registrations** in Azure AD, select your application.
114+
1. Browse to **Identity** > **Applications** > **App registrations**, then select your application.
119115
1. Select **Certificates & secrets**.
120116
1. Select **Certificates**, then select **Upload certificate** and then select the certificate (an existing certificate or the self-signed certificate you exported).
121117
1. Select **Add**.
@@ -126,8 +122,7 @@ After registering the certificate with your application in the application regis
126122

127123
If you choose not to use a certificate, you can create a new application secret.
128124

129-
1. Search for and select **Azure Active Directory**.
130-
1. Select **App registrations** and select your application from the list.
125+
1. Browse to **Identity** > **Applications** > **App registrations**, then select your application.
131126
1. Select **Certificates & secrets**.
132127
1. Select **Client secrets**, and then Select **New client secret**.
133128
1. Provide a description of the secret, and a duration.

articles/active-directory/external-identities/reset-redemption-status.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -36,13 +36,13 @@ To reset a user's redemption status, you'll need one of the following roles:
3636
- [User Administrator](../roles/permissions-reference.md#user-administrator)
3737
- [Global Administrator](../roles/permissions-reference.md#global-administrator)
3838

39-
## Use the Azure portal to reset redemption status
39+
## Use the Microsoft Entra admin center to reset redemption status
4040

4141
[!INCLUDE [portal updates](~/articles/active-directory/includes/portal-update.md)]
4242

43-
1. Sign in to the [Azure portal](https://portal.azure.com) using a Global administrator or User administrator account for the directory.
44-
1. Search for and select **Azure Active Directory**.
45-
1. Select **Users**.
43+
44+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](../roles/permissions-reference.md#user-administrator).
45+
1. Browse to **Identity** > **Users** > **All users**.
4646
1. In the list, select the user's name to open their user profile.
4747
1. (Optional) If the user wants to sign in using a different email:
4848
1. Select the **Edit properties** icon.

articles/active-directory/external-identities/self-service-sign-up-add-api-connector.md

Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -27,20 +27,19 @@ To use an [API connector](api-connectors-overview.md), you first create the API
2727

2828
[!INCLUDE [portal updates](~/articles/active-directory/includes/portal-update.md)]
2929

30-
1. Sign in to the [Azure portal](https://portal.azure.com).
31-
2. Under **Azure services**, select **Azure Active Directory**.
32-
3. In the left menu, select **External Identities**.
33-
4. Select **All API connectors**, and then select **New API connector**.
30+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](../roles/permissions-reference.md#user-administrator).
31+
1. Browse to **Identity** > **External Identities** > **Overview**.
32+
1. Select **All API connectors**, and then select **New API connector**.
3433

3534
:::image type="content" source="media/self-service-sign-up-add-api-connector/api-connector-new.png" alt-text="Screenshot of adding a new API connector to External Identities.":::
3635

37-
5. Provide a display name for the call. For example, **Check approval status**.
38-
6. Provide the **Endpoint URL** for the API call.
39-
7. Choose the **Authentication type** and configure the authentication information for calling your API. Learn how to [Secure your API Connector](self-service-sign-up-secure-api-connector.md).
36+
1. Provide a display name for the call. For example, **Check approval status**.
37+
1. Provide the **Endpoint URL** for the API call.
38+
1. Choose the **Authentication type** and configure the authentication information for calling your API. Learn how to [Secure your API Connector](self-service-sign-up-secure-api-connector.md).
4039

4140
:::image type="content" source="media/self-service-sign-up-add-api-connector/api-connector-config.png" alt-text="Screenshot of configuring an API connector.":::
4241

43-
8. Select **Save**.
42+
1. Select **Save**.
4443

4544
## The request sent to your API
4645
An API connector materializes as an **HTTP POST** request, sending user attributes ('claims') as key-value pairs in a JSON body. Attributes are serialized similarly to [Microsoft Graph](/graph/api/resources/user#properties) user properties.
@@ -93,9 +92,8 @@ Additionally, the claims are typically sent in all request:
9392

9493
Follow these steps to add an API connector to a self-service sign-up user flow.
9594

96-
1. Sign in to the [Azure portal](https://portal.azure.com) as an Azure AD administrator.
97-
2. Under **Azure services**, select **Azure Active Directory**.
98-
3. In the left menu, select **External Identities**.
95+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](../roles/permissions-reference.md#user-administrator).
96+
1. Browse to **Identity** > **External Identities** > **Overview**.
9997
4. Select **User flows**, and then select the user flow you want to add the API connector to.
10098
5. Select **API connectors**, and then select the API endpoints you want to invoke at the following steps in the user flow:
10199

articles/active-directory/external-identities/self-service-sign-up-add-approvals.md

Lines changed: 11 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -36,17 +36,16 @@ This article gives an example of how to integrate with an approval system. In th
3636

3737
You need to register your approval system as an application in your Azure AD tenant so it can authenticate with Azure AD and have permission to create users. Learn more about [authentication and authorization basics for Microsoft Graph](/graph/auth/auth-concepts).
3838

39-
1. Sign in to the [Azure portal](https://portal.azure.com) as an Azure AD administrator.
40-
2. Under **Azure services**, select **Azure Active Directory**.
41-
3. In the left menu, select **App registrations**, and then select **New registration**.
42-
4. Enter a **Name** for the application, for example, _Sign-up Approvals_.
43-
5. Select **Register**. You can leave other fields at their defaults.
39+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](../roles/permissions-reference.md#user-administrator).
40+
1. Browse to **Identity** > **Applications** > **App registrations**, and then select **New registration**.
41+
1. Enter a **Name** for the application, for example, _Sign-up Approvals_.
42+
1. Select **Register**. You can leave other fields at their defaults.
4443

4544
:::image type="content" source="media/self-service-sign-up-add-approvals/register-approvals-app.png" alt-text="Screenshot that highlights the Register button.":::
4645

47-
6. Under **Manage** in the left menu, select **API permissions**, and then select **Add a permission**.
48-
7. On the **Request API permissions** page, select **Microsoft Graph**, and then select **Application permissions**.
49-
8. Under **Select permissions**, expand **User**, and then select the **User.ReadWrite.All** check box. This permission allows the approval system to create the user upon approval. Then select **Add permissions**.
46+
1. Under **Manage** in the left menu, select **API permissions**, and then select **Add a permission**.
47+
1. On the **Request API permissions** page, select **Microsoft Graph**, and then select **Application permissions**.
48+
1. Under **Select permissions**, expand **User**, and then select the **User.ReadWrite.All** check box. This permission allows the approval system to create the user upon approval. Then select **Add permissions**.
5049

5150
:::image type="content" source="media/self-service-sign-up-add-approvals/request-api-permissions.png" alt-text="Screenshot of requesting API permissions.":::
5251

@@ -77,19 +76,17 @@ To create these connectors, follow the steps in [create an API connector](self-s
7776

7877
Now you'll add the API connectors to a self-service sign-up user flow with these steps:
7978

80-
1. Sign in to the [Azure portal](https://portal.azure.com) as an Azure AD administrator.
81-
2. Under **Azure services**, select **Azure Active Directory**.
82-
3. In the left menu, select **External Identities**.
83-
4. Select **User flows**, and then select the user flow you want to enable the API connector for.
84-
5. Select **API connectors**, and then select the API endpoints you want to invoke at the following steps in the user flow:
79+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](../roles/permissions-reference.md#user-administrator).
80+
1. Browse to **Identity** > **External identities** > **User flows**, and then select the user flow you want to enable the API connector for.
81+
1. Select **API connectors**, and then select the API endpoints you want to invoke at the following steps in the user flow:
8582

8683
- **After federating with an identity provider during sign-up**: Select your approval status API connector, for example _Check approval status_.
8784
- **Before creating the user**: Select your approval request API connector, for example _Request approval_.
8885

8986
:::image type="content" source="media/self-service-sign-up-add-approvals/api-connectors-user-flow-api.png" alt-text="Screenshot of API connector in a user flow.":::
9087

9188

92-
6. Select **Save**.
89+
1. Select **Save**.
9390

9491
## Control the sign-up flow with API responses
9592

articles/active-directory/external-identities/self-service-sign-up-secure-api-connector.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -33,9 +33,8 @@ HTTP basic authentication is defined in [RFC 2617](https://tools.ietf.org/html/r
3333

3434
To configure an API Connector with HTTP basic authentication, follow these steps:
3535

36-
1. Sign in to the [Azure portal](https://portal.azure.com).
37-
2. Under **Azure services**, select **Azure AD**.
38-
1. In the left menu, select **External Identities**.
36+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](../roles/permissions-reference.md#user-administrator).
37+
1. Browse to **Identity** > **External Identities** > **Overview**.
3938
1. Select **All API connectors**, and then select the **API Connector** you want to configure.
4039
1. For the **Authentication type**, select **Basic**.
4140
1. Provide the **Username**, and **Password** of your REST API endpoint.
@@ -71,9 +70,8 @@ You can then [export the certificate](../../key-vault/certificates/how-to-export
7170

7271
To configure an API Connector with client certificate authentication, follow these steps:
7372

74-
1. Sign in to the [Azure portal](https://portal.azure.com).
75-
2. Under **Azure services**, select **Azure AD**.
76-
1. In the left menu, select **External Identities**.
73+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](../roles/permissions-reference.md#user-administrator).
74+
1. Browse to **Identity** > **External Identities** > **Overview**.
7775
1. Select **All API connectors**, and then select the **API Connector** you want to configure.
7876
1. For the **Authentication type**, select **Certificate**.
7977
1. In the **Upload certificate** box, select your certificate's .pfx file with a private key.

articles/active-directory/external-identities/self-service-sign-up-user-flow.md

Lines changed: 20 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -51,10 +51,8 @@ Before you can add a self-service sign-up user flow to your applications, you ne
5151
> [!NOTE]
5252
> This setting can also be configured with the [authenticationFlowsPolicy](/graph/api/resources/authenticationflowspolicy?view=graph-rest-1.0&preserve-view=true) resource type in the Microsoft Graph API.
5353
54-
1. Sign in to the [Azure portal](https://portal.azure.com) as an Azure AD administrator.
55-
2. Under **Azure services**, select **Azure Active Directory**.
56-
1. Under **Manage** in the left menu, select **Users**.
57-
1. Select **User settings**, and then under **External users**, select **Manage external collaboration settings**.
54+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](../roles/permissions-reference.md#user-administrator).
55+
1. Browse to **Identity** > **Users** > **User settings**, and then under **External users**, select **Manage external collaboration settings**.
5856
1. Set the **Enable guest self-service sign up via user flows** toggle to **Yes**.
5957

6058
:::image type="content" source="media/self-service-sign-up-user-flow/enable-self-service-sign-up.png" alt-text="Screenshot of the enable guest self-service sign up toggle.":::
@@ -64,32 +62,30 @@ Before you can add a self-service sign-up user flow to your applications, you ne
6462

6563
Next, you'll create the user flow for self-service sign-up and add it to an application.
6664

67-
1. Sign in to the [Azure portal](https://portal.azure.com) as an Azure AD administrator.
68-
2. Under **Azure services**, select **Azure Active Directory**.
69-
3. In the left menu, select **External Identities**.
70-
4. Select **User flows**, and then select **New user flow**.
65+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](../roles/permissions-reference.md#user-administrator).
66+
1. Browse to **Identity** > **External Identities** > **User flows**, and then select **New user flow**.
7167

7268
:::image type="content" source="media/self-service-sign-up-user-flow/new-user-flow.png" alt-text="Screenshot of the new user flow button.":::
7369

74-
5. Select the user flow type (for example, **Sign up and sign in**), and then select the version (**Recommended** or **Preview**).
75-
6. On the **Create** page, enter a **Name** for the user flow. The name is automatically prefixed with **B2X_1_**.
76-
7. In the **Identity providers** list, select one or more identity providers that your external users can use to log into your application. **Azure Active Directory Sign up** is selected by default. (See [Before you begin](#before-you-begin) earlier in this article to learn how to add identity providers.)
77-
8. Under **User attributes**, choose the attributes you want to collect from the user. For more attributes, select **Show more**. For example, select **Show more**, and then choose attributes and claims for **Country/Region**, **Display Name**, and **Postal Code**. Select **OK**.
70+
1. Select the user flow type (for example, **Sign up and sign in**), and then select the version (**Recommended** or **Preview**).
71+
1. On the **Create** page, enter a **Name** for the user flow. The name is automatically prefixed with **B2X_1_**.
72+
1. In the **Identity providers** list, select one or more identity providers that your external users can use to log into your application. **Azure Active Directory Sign up** is selected by default. (See [Before you begin](#before-you-begin) earlier in this article to learn how to add identity providers.)
73+
1. Under **User attributes**, choose the attributes you want to collect from the user. For more attributes, select **Show more**. For example, select **Show more**, and then choose attributes and claims for **Country/Region**, **Display Name**, and **Postal Code**. Select **OK**.
7874

7975
:::image type="content" source="media/self-service-sign-up-user-flow/create-user-flow.png" alt-text="Screenshot of the new user flow creation page. ":::
8076

8177
> [!NOTE]
8278
> You can only collect attributes when a user signs up for the first time. After a user signs up, they will no longer be prompted to collect attribute information, even if you change the user flow.
8379
84-
8. Select **Create**.
85-
9. The new user flow appears in the **User flows** list. If necessary, refresh the page.
80+
1. Select **Create**.
81+
1. The new user flow appears in the **User flows** list. If necessary, refresh the page.
8682

8783
## Select the layout of the attribute collection form
8884

8985
You can choose order in which the attributes are displayed on the sign-up page.
9086

91-
1. Sign in to the [Azure portal](https://portal.azure.com), then select **Azure Active Directory**.
92-
2. Select **External Identities**, select **User flows**.
87+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](../roles/permissions-reference.md#user-administrator).
88+
1. Browse to **Identity** > **External Identities** > **User flows**.
9389
3. Select the self-service sign-up user flow from the list.
9490
4. Under **Customize**, select **Page layouts**.
9591
5. The attributes you chose to collect are listed. To change the order of display, select an attribute, and then select **Move up**, **Move down**, **Move to top**, or **Move to bottom**.
@@ -99,18 +95,17 @@ You can choose order in which the attributes are displayed on the sign-up page.
9995

10096
Now you'll associate applications with the user flow to enable sign-up for those applications. New users who access the associated applications will be presented with your new self-service sign-up experience.
10197

102-
1. Sign in to the [Azure portal](https://portal.azure.com) as an Azure AD administrator.
103-
2. Under **Azure services**, select **Azure Active Directory**.
104-
3. In the left menu, select **External Identities**.
105-
4. Under **Self-service sign up**, select **User flows**.
106-
5. Select the self-service sign-up user flow from the list.
107-
6. In the left menu, under **Use**, select **Applications**.
108-
7. Select **Add application**.
98+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](../roles/permissions-reference.md#user-administrator).
99+
1. Browse to **Identity** > **External Identities** > **User flows**
100+
1. Under **Self-service sign up**, select **User flows**.
101+
1. Select the self-service sign-up user flow from the list.
102+
1. In the left menu, under **Use**, select **Applications**.
103+
1. Select **Add application**.
109104

110105
:::image type="content" source="media/self-service-sign-up-user-flow/assign-app-to-user-flow.png" alt-text="Screenshot of adding an application to the user flow.":::
111106

112-
8. Select the application from the list. Or use the search box to find the application, and then select it.
113-
9. Click **Select**.
107+
1. Select the application from the list. Or use the search box to find the application, and then select it.
108+
1. Click **Select**.
114109

115110
## Next steps
116111

0 commit comments

Comments
 (0)