Skip to content

Commit 9954552

Browse files
Update export-import-provisioning-configuration.md
1 parent 0df8425 commit 9954552

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

articles/active-directory/app-provisioning/export-import-provisioning-configuration.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,6 @@ ms.author: chmutali
1919
ms.collection: M365-identity-device-management
2020
---
2121
# Export your provisioning configuration and roll back to a known good state
22-
2322
## Export and import your provisioning configuration from the Azure portal
2423

2524
### How can I export my provisioning configuration?
@@ -38,14 +37,14 @@ Exporting and saving your configuration allows you to roll back to a previous ve
3837
## Export and import your provisioning configuration by using the Microsoft Graph API
3938
You can use the Microsoft Graph API and the Microsoft Graph Explorer to export your User Provisioning attribute mappings and schema to a JSON file and import it back into Azure AD. You can also use the steps captured here to create a backup of your provisioning configuration.
4039

41-
### Step 1: Retrieve your Provisioning App Service Principal ID (Object ID)
40+
## Step 1: Retrieve your Provisioning App Service Principal ID (Object ID)
4241

43-
1. Launch the [Azure portal](https://portal.azure.com), and navigate to the Properties section of your provisioning application. For example, if you want to export your *Workday to AD User Provisioning application* mapping navigate to the Properties section of that app.
42+
1. Launch the [Azure portal](https://portal.azure.com), and navigate to the Properties section of your provisioning application. For e.g., if you want to export your *Workday to AD User Provisioning application* mapping navigate to the Properties section of that app.
4443
1. In the Properties section of your provisioning app, copy the GUID value associated with the *Object ID* field. This value is also called the **ServicePrincipalId** of your App and it will be used in Microsoft Graph Explorer operations.
4544

4645
![Workday App Service Principal ID](./media/export-import-provisioning-configuration/wd_export_01.png)
4746

48-
### Step 2: Sign into Microsoft Graph Explorer
47+
## Step 2: Sign into Microsoft Graph Explorer
4948

5049
1. Launch [Microsoft Graph Explorer](https://developer.microsoft.com/graph/graph-explorer)
5150
1. Click on the "Sign-In with Microsoft" button and sign-in using Azure AD Global Admin or App Admin credentials.
@@ -54,7 +53,7 @@ You can use the Microsoft Graph API and the Microsoft Graph Explorer to export y
5453

5554
1. Upon successful sign-in, you will see the user account details in the left-hand pane.
5655

57-
### Step 3: Retrieve the Provisioning Job ID of the Provisioning App
56+
## Step 3: Retrieve the Provisioning Job ID of the Provisioning App
5857

5958
In the Microsoft Graph Explorer, run the following GET query replacing [servicePrincipalId] with the **ServicePrincipalId** extracted from the [Step 1](#step-1-retrieve-your-provisioning-app-service-principal-id-object-id).
6059

@@ -76,7 +75,7 @@ In the Microsoft Graph Explorer, run the following GET query, replacing [service
7675

7776
Copy the JSON object from the response and save it to a file to create a backup of the schema.
7877

79-
### Step 5: Import the Provisioning Schema
78+
## Step 5: Import the Provisioning Schema
8079

8180
> [!CAUTION]
8281
> Perform this step only if you need to modify the schema for configuration that cannot be changed using the Azure portal or if you need to restore the configuration from a previously backed up file with valid and working schema.

0 commit comments

Comments
 (0)