Skip to content

Commit baac441

Browse files
authored
Merge pull request #195841 from henrymbuguakiarie/msid-content-health-quickstart-configure-app-access-web-apis
[msid][content-health] updating docs and freshness
2 parents d724823 + f180568 commit baac441

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/active-directory/develop/quickstart-configure-app-access-web-apis.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: develop
1010
ms.topic: quickstart
1111
ms.workload: identity
12-
ms.date: 09/03/2020
12+
ms.date: 05/05/2022
1313
ms.author: marsma
1414
ms.custom: aaddev, contperf-fy21q1, mode-api
1515
ms.reviewer: lenalepa, aragra, sureshja
@@ -39,7 +39,7 @@ This diagram shows how the two app registrations relate to one another. In this
3939
Once you've registered both your client app and web API and you've exposed the API by creating scopes, you can configure the client's permissions to the API by following these steps:
4040

4141
1. Sign in to the <a href="https://portal.azure.com/" target="_blank">Azure portal</a>.
42-
1. If you have access to multiple tenants, use the **Directory + subscription** filter :::image type="icon" source="./media/quickstart-configure-app-access-web-apis/portal-01-directory-subscription-filter.png" border="false"::: in the top menu to select the tenant containing your client app's registration.
42+
1. If you have access to multiple tenants, use the **Directories + subscriptions** filter :::image type="icon" source="./media/quickstart-configure-app-access-web-apis/portal-01-directory-subscription-filter.png" border="false"::: in the top menu to select the tenant containing your client app's registration.
4343
1. Select **Azure Active Directory** > **App registrations**, and then select your client application (*not* your web API).
4444
1. Select **API permissions** > **Add a permission** > **My APIs**.
4545
1. Select the web API you registered as part of the prerequisites.
@@ -68,7 +68,7 @@ In addition to accessing your own web API on behalf of the signed-in user, your
6868
Configure delegated permission to Microsoft Graph to enable your client application to perform operations on behalf of the logged-in user, for example reading their email or modifying their profile. By default, users of your client app are asked when they sign in to consent to the delegated permissions you've configured for it.
6969

7070
1. Sign in to the <a href="https://portal.azure.com/" target="_blank">Azure portal</a>.
71-
1. If you have access to multiple tenants, use the **Directory + subscription** filter :::image type="icon" source="./media/quickstart-configure-app-access-web-apis/portal-01-directory-subscription-filter.png" border="false"::: in the top menu to select the tenant containing your client app's registration.
71+
1. If you have access to multiple tenants, use the **Directories + subscriptions** filter :::image type="icon" source="./media/quickstart-configure-app-access-web-apis/portal-01-directory-subscription-filter.png" border="false"::: in the top menu to select the tenant containing your client app's registration.
7272
1. Select **Azure Active Directory** > **App registrations**, and then select your client application.
7373
1. Select **API permissions** > **Add a permission** > **Microsoft Graph**
7474
1. Select **Delegated permissions**. Microsoft Graph exposes many permissions, with the most commonly used shown at the top of the list.
@@ -93,7 +93,7 @@ Configure application permissions for an application that needs to authenticate
9393
In the following steps, you grant permission to Microsoft Graph's *Files.Read.All* permission as an example.
9494

9595
1. Sign in to the <a href="https://portal.azure.com/" target="_blank">Azure portal</a>.
96-
1. If you have access to multiple tenants, use the **Directory + subscription** filter :::image type="icon" source="./media/quickstart-configure-app-access-web-apis/portal-01-directory-subscription-filter.png" border="false"::: in the top menu to select the tenant containing your client app's registration.
96+
1. If you have access to multiple tenants, use the **Directories + subscriptions** filter :::image type="icon" source="./media/quickstart-configure-app-access-web-apis/portal-01-directory-subscription-filter.png" border="false"::: in the top menu to select the tenant containing your client app's registration.
9797
1. Select **Azure Active Directory** > **App registrations**, and then select your client application.
9898
1. Select **API permissions** > **Add a permission** > **Microsoft Graph** > **Application permissions**.
9999
1. All permissions exposed by Microsoft Graph are shown under **Select permissions**.
@@ -142,7 +142,7 @@ The **Grant admin consent** button is *disabled* if you aren't an admin or if no
142142

143143
## Next steps
144144

145-
Advance to the next quickstart in the series to learn how to configure which account types can access your application. For example, you might want to limit access only to those users in your organization (single-tenant) or allow users in other Azure AD tenants (multi-tenant) and those with personal Microsoft accounts (MSA).
145+
Advance to the next quickstart in the series to learn how to configure which account types can access your application. For example, you might want to limit access only to those users in your organization (single-tenant) or allow users in other Azure Active Directory (Azure AD) tenants (multi-tenant) and those with personal Microsoft accounts (MSA).
146146

147147
> [!div class="nextstepaction"]
148148
> [Modify the accounts supported by an application](./howto-modify-supported-accounts.md)

0 commit comments

Comments
 (0)