Skip to content

Commit aa79496

Browse files
committed
More step updates
1 parent 088ae51 commit aa79496

6 files changed

+12
-12
lines changed

articles/active-directory/app-provisioning/inbound-provisioning-api-configure-app.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: app-provisioning
99
ms.workload: identity
1010
ms.topic: how-to
11-
ms.date: 07/07/2023
11+
ms.date: 09/15/2023
1212
ms.author: jfields
1313
ms.reviewer: cmmdesai
1414
---
@@ -35,7 +35,7 @@ If you're configuring inbound user provisioning to on-premises Active Directory,
3535

3636
## Create your API-driven provisioning app
3737

38-
1. Log in to the [Microsoft Entra admin center](<https://entra.microsoft.com>).
38+
1. Log in to the [Microsoft Entra admin center](<https://entra.microsoft.com>) as at least an [Application Administrator](https://go.microsoft.com/fwlink/?linkid=2247823).
3939
2. Browse to **Azure Active Directory** > **Applications** > **Enterprise applications**.
4040
3. Click on **New application** to create a new provisioning application.
4141
[![Screenshot of Entra Admin Center.](media/inbound-provisioning-api-configure-app/provisioning-entra-admin-center.png)](media/inbound-provisioning-api-configure-app/provisioning-entra-admin-center.png#lightbox)

articles/active-directory/app-provisioning/inbound-provisioning-api-curl-tutorial.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ ms.reviewer: cmmdesai
4040
4141
## Verify processing of the bulk request payload
4242
43-
1. Log in to [Microsoft Entra admin center](https://entra.microsoft.com) with *global administrator* or *application administrator* login credentials.
43+
1. Log in to [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Application Administrator](https://go.microsoft.com/fwlink/?linkid=2247823).
4444
1. Browse to **Azure Active Directory -> Applications -> Enterprise applications**.
4545
1. Under all applications, use the search filter text box to find and open your API-driven provisioning application.
4646
1. Open the Provisioning blade. The landing page displays the status of the last run.

articles/active-directory/app-provisioning/inbound-provisioning-api-custom-attributes.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: app-provisioning
99
ms.workload: identity
1010
ms.topic: how-to
11-
ms.date: 07/24/2023
11+
ms.date: 09/15/2023
1212
ms.author: jfields
1313
ms.reviewer: cmmdesai
1414
---
@@ -28,8 +28,8 @@ You have configured API-driven provisioning app. You're provisioning app is succ
2828

2929
In this step, we'll add the two attributes "HireDate" and "JobCode" that are not part of the standard SCIM schema to the provisioning app and use them in the provisioning data flow.
3030

31-
1. Log in to Microsoft Entra admin center with application administrator role.
32-
1. Go to **Enterprise applications** and open your API-driven provisioning app.
31+
1. Log in to your [Microsoft Entra admin center](https://entra.micsrosoft.com) as at least an [Application Administrator](https://go.microsoft.com/fwlink/?linkid=2247823).
32+
1. Browse to **Enterprise applications** and open your API-driven provisioning app.
3333
1. Open the **Provisioning** blade.
3434
1. Click on the **Edit Provisioning** button.
3535
1. Expand the **Mappings** section and click on the attribute mapping link. <br>

articles/active-directory/app-provisioning/inbound-provisioning-api-grant-access.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: app-provisioning
99
ms.workload: identity
1010
ms.topic: how-to
11-
ms.date: 07/07/2023
11+
ms.date: 09/15/2023
1212
ms.author: jfields
1313
ms.reviewer: cmmdesai
1414
---
@@ -27,7 +27,7 @@ Depending on how your API client authenticates with Azure AD, you can select bet
2727
## Configure a service principal
2828
This configuration registers an app in Azure AD that represents the external API client and grants it permission to invoke the inbound provisioning API. The service principal client id and client secret can be used in the OAuth client credentials grant flow.
2929

30-
1. Log in to Microsoft Entra admin center (https://entra.microsoft.com) with global administrator or application administrator login credentials.
30+
1. Log in to Microsoft Entra admin center (https://entra.microsoft.com) with at least [Application Administrator](https://go.microsoft.com/fwlink/?linkid=2247823) login credentials.
3131
1. Browse to **Azure Active Directory** -> **Applications** -> **App registrations**.
3232
1. Click on the option **New registration**.
3333
1. Provide an app name, select the default options, and click on **Register**.

articles/active-directory/app-provisioning/inbound-provisioning-api-graph-explorer.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: app-provisioning
99
ms.workload: identity
1010
ms.topic: how-to
11-
ms.date: 07/18/2023
11+
ms.date: 09/15/2023
1212
ms.author: jfields
1313
ms.reviewer: cmmdesai
1414
---
@@ -51,7 +51,7 @@ This tutorial describes how you can quickly test [API-driven inbound provisionin
5151
You can verify the processing either from the Microsoft Entra admin center or using Graph Explorer.
5252

5353
### Verify processing from Microsoft Entra admin center
54-
1. Log in to [Microsoft Entra admin center](https://entra.microsoft.com) with *global administrator* or *application administrator* login credentials.
54+
1. Log in to [Microsoft Entra admin center](https://entra.microsoft.com) with at least [Application Administrator](https://go.microsoft.com/fwlink/?linkid=2247823) login credentials.
5555
1. Browse to **Azure Active Directory -> Applications -> Enterprise applications**.
5656
1. Under all applications, use the search filter text box to find and open your API-driven provisioning application.
5757
1. Open the Provisioning blade. The landing page displays the status of the last run.

articles/active-directory/app-provisioning/inbound-provisioning-api-postman.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: app-provisioning
99
ms.workload: identity
1010
ms.topic: how-to
11-
ms.date: 07/19/2023
11+
ms.date: 09/15/2023
1212
ms.author: jfields
1313
ms.reviewer: cmmdesai
1414
---
@@ -65,7 +65,7 @@ If the API invocation is successful, you see the message `202 Accepted.` Under H
6565
You can verify the processing either from the Microsoft Entra admin center or using Postman.
6666

6767
### Verify processing from Microsoft Entra admin center
68-
1. Log in to [Microsoft Entra admin center](https://entra.microsoft.com) with *global administrator* or *application administrator* login credentials.
68+
1. Log in to [Microsoft Entra admin center](https://entra.microsoft.com) with at least [Application Administrator](https://go.microsoft.com/fwlink/?linkid=2247823) level credentials.
6969
1. Browse to **Azure Active Directory -> Applications -> Enterprise applications**.
7070
1. Under all applications, use the search filter text box to find and open your API-driven provisioning application.
7171
1. Open the Provisioning blade. The landing page displays the status of the last run.

0 commit comments

Comments
 (0)