Skip to content

Commit 647dacc

Browse files
Merge pull request #249891 from davidmu1/updatesteps18
Updatesteps18
2 parents 0b46281 + 951b86d commit 647dacc

File tree

2 files changed

+23
-23
lines changed

2 files changed

+23
-23
lines changed

articles/active-directory/develop/howto-call-a-web-api-with-postman.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ zone_pivot_groups: web-api-howto-prereq
1818

1919
::: zone pivot="no-api"
2020

21-
This article shows you how to call a protected ASP.NET Core web API using [Postman](https://www.postman.com/). Postman is an application that lets you send HTTP requests to a web API to test its authorization and access control (authentication) policies. In this article, you'll register a web app and a web API in a tenant on the Azure portal. The web app is used to get an access token generated by the Microsoft identity platform. Next, you'll use the token to make an authorized call to the web API using Postman.
21+
This article shows you how to call a protected ASP.NET Core web API using [Postman](https://www.postman.com/). Postman is an application that lets you send HTTP requests to a web API to test its authorization and access control (authentication) policies. In this article, you'll register a web app and a web API in a tenant. The web app is used to get an access token generated by the Microsoft identity platform. Next, you'll use the token to make an authorized call to the web API using Postman.
2222

2323
::: zone-end
2424

@@ -69,10 +69,10 @@ The Microsoft identity platform requires your application to be registered befor
6969

7070
Follow these steps to create the web API registration:
7171

72-
1. Sign in to the [Azure portal](https://portal.azure.com).
72+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Application Developer](../roles/permissions-reference.md#application-developer).
7373
1. If access to multiple tenants is available, use the **Directories + subscriptions** filter :::image type="icon" source="media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which you want to register the application.
74-
1. Search for and select **Azure Active Directory**.
75-
1. Under **Manage**, select **App registrations > New registration**.
74+
1. Browse to **Identity** > **Applications** > **Application registrations**.
75+
1. Select **New registration**.
7676
1. Enter a **Name** for the application, such as _NewWebAPI1_.
7777
1. For **Supported account types**, select **Accounts in this organizational directory only**. For information on different account types, select **Help me choose** option.
7878
1. Select **Register**.
@@ -116,8 +116,8 @@ Follow these steps to create the web app registration:
116116

117117
::: zone pivot="no-api"
118118

119-
1. Select **Home** to return to the home page. Search for and select **Azure Active Directory**.
120-
1. Under **Manage**, select **App registrations** > **New registration**.
119+
Select **Home** to return to the home page. Browse to **Identity** > **Applications** > **Application registrations**.
120+
1. Select **New registration**.
121121
1. Enter a **Name** for the application, such as `web-app-calls-web-api`.
122122
1. For **Supported account types**, select **Accounts in this organizational directory only**. For information on different account types, select the **Help me choose** option.
123123
1. Under **Redirect URI (optional)**, select **Web**, and then enter `http://localhost` in the URL text box.
@@ -127,26 +127,26 @@ Follow these steps to create the web app registration:
127127

128128
::: zone pivot="api"
129129

130-
1. Sign in to the [Azure portal](https://portal.azure.com).
131-
1. If access to multiple tenants is available, use the Directories + subscriptions filter :::image type="icon" source="media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which you want to register the application.
132-
1. Search for and select **Azure Active Directory**.
133-
1. Under **Manage**, select **App registrations** > **New registration**.
130+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Application Developer](../roles/permissions-reference.md#application-developer).
131+
1. If access to multiple tenants is available, use the **Directories + subscriptions** filter :::image type="icon" source="media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which you want to register the application.
132+
1. Browse to **Identity** > **Applications** > **Application registrations**.
133+
1. Select **New registration**.
134134
1. Enter a Name for the application, such as `web-app-calls-web-api`.
135135
1. For **Supported account types**, select **Accounts in this organizational directory only**. For information on different account types, select the **Help me choose** option.
136136
1. Under **Redirect URI (optional)**, select **Web**, and then enter `http://localhost` in the URL text box.
137137
1. Select **Register**.
138138

139139
::: zone-end
140140

141-
When registration is complete, the Azure portal displays the app registration's **Overview** pane. Record the **Directory (tenant) ID** and the **Application (client) ID** to be used in later steps.
141+
The application's **Overview** pane is displayed when registration is complete. Record the **Directory (tenant) ID** and the **Application (client) ID** to be used in later steps.
142142

143143
#### Add a client secret
144144

145145
A client secret is a string value your app can use to identity itself, and is sometimes referred to as an _application password_. The web app uses the client secret to prove its identity when it requests tokens.
146146

147147
Follow these steps to configure a client secret:
148148

149-
1. From the **Overview** pane in the Azure portal, under **Manage**, select **Certificates & secrets** > **Client secrets** > **New client secret**.
149+
1. From the **Overview** pane, under **Manage**, select **Certificates & secrets** > **Client secrets** > **New client secret**.
150150
1. Add a description for your client secret, for example _My client secret_.
151151
1. Select an expiration for the secret or specify a custom lifetime.
152152

@@ -162,14 +162,14 @@ By specifying a web API's scopes, the web app can obtain an access token contain
162162

163163
Follow these steps to configure client's permissions to the web API:
164164

165-
1. From the **Overview** pane of your application in the Azure portal, under **Manage**, select **API permissions** > **Add a permission** > **My APIs**.
165+
1. From the **Overview** pane of your application, under **Manage**, select **API permissions** > **Add a permission** > **My APIs**.
166166
1. Select **NewWebAPI1** or the API that you wish to add permissions to.
167167
1. Under **Select permissions**, check the box next to **Forecast.Read**. You may need to expand the **Permission** list. This selects the permissions the client app should have on behalf of the signed-in user.
168168
1. Select **Add permissions** to complete the process.
169169

170170
After adding these permissions to your API, you should see the selected permissions under **Configured permissions**.
171171

172-
You may also notice the **User.Read** permission for the Microsoft Graph API. This permission is added automatically when you register an app in the Azure portal.
172+
You may also notice the **User.Read** permission for the Microsoft Graph API. This permission is added automatically when you register an app.
173173

174174
::: zone pivot="no-api"
175175

@@ -183,8 +183,8 @@ You may also notice the **User.Read** permission for the Microsoft Graph API. Th
183183

184184
1. Navigate to `ms-identity-docs-code-dotnet/web-api` folder and open `appsettings.json`, replace the `{APPLICATION_CLIENT_ID}` and `{DIRECTORY_TENANT_ID}` with:
185185

186-
- `{APPLICATION_CLIENT_ID}` is the web API **Application (client) ID** on the app's **Overview** pane **App registrations** in the Azure portal.
187-
- `{DIRECTORY_TENANT_ID}` is the web API **Directory (tenant) ID** on the app's **Overview** pane **App registrations** in the Azure portal.
186+
- `{APPLICATION_CLIENT_ID}` is the web API **Application (client) ID** on the app's **Overview** pane **App registrations**.
187+
- `{DIRECTORY_TENANT_ID}` is the web API **Directory (tenant) ID** on the app's **Overview** pane **App registrations**.
188188

189189
1. Execute the following command to start the app:
190190

articles/active-directory/develop/howto-configure-app-instance-property-locks.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -34,19 +34,19 @@ The following property usage scenarios are considered as sensitive:
3434

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

37-
To configure an app instance lock using the Azure portal:
37+
To configure an app instance lock:
3838

39-
1. Sign in to the <a href="https://portal.azure.com/" target="_blank">Azure portal</a>.
40-
1. If you have access to multiple tenants, use the **Directories + subscriptions** filter :::image type="icon" source="./media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant that contains the app registration you want to configure.
41-
1. Search for and select **Azure Active Directory**.
42-
1. Under **Manage**, select **App registrations**, and then select the application you want to configure.
39+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
40+
1. If access to multiple tenants is available, use the **Directories + subscriptions** filter :::image type="icon" source="media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which you want to register the application.
41+
1. Browse to **Identity** > **Applications** > **Application registrations**.
42+
1. Select the application you want to configure.
4343
1. Select **Authentication**, and then select **Configure** under the *App instance property lock* section.
4444

45-
:::image type="content" source="media/howto-configure-app-instance-property-locks/app-instance-lock-configure-overview.png" alt-text="Screenshot of an app registration's app instance lock in the Azure portal.":::
45+
:::image type="content" source="media/howto-configure-app-instance-property-locks/app-instance-lock-configure-overview.png" alt-text="Screenshot of an app registration's app instance lock.":::
4646

4747
2. In the **App instance property lock** pane, enter the settings for the lock. The table following the image describes each setting and their parameters.
4848

49-
:::image type="content" source="media/howto-configure-app-instance-property-locks/app-instance-lock-configure-properties.png" alt-text="Screenshot of an app registration's app instance property lock context pane in the Azure portal.":::
49+
:::image type="content" source="media/howto-configure-app-instance-property-locks/app-instance-lock-configure-properties.png" alt-text="Screenshot of an app registration's app instance property lock context pane.":::
5050

5151
| Field | Description |
5252
| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

0 commit comments

Comments
 (0)