Skip to content

Commit 257b90e

Browse files
Update export-import-provisioning-configuration.md
1 parent 9d9ed71 commit 257b90e

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

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

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: 'Export or import your provisioning configuration by using the Microsoft Graph API | Microsoft Docs'
3-
description: Learn how to export and import provisioning configuration using the Microsoft Graph API.
2+
title: 'Export your provisioning configuration and roll back to a known good state for disaster recovery.| Microsoft Docs'
3+
description: Learn how to export your provisioning configuration and roll back to a known good state for disaster recovery.
44
services: active-directory
55
author: cmmdesai
66
documentationcenter: na
@@ -13,12 +13,13 @@ ms.devlang: na
1313
ms.topic: article
1414
ms.tgt_pltfrm: na
1515
ms.workload: identity
16-
ms.date: 09/09/2019
16+
ms.date: 03/19/2020
1717
ms.author: chmutali
1818

1919
ms.collection: M365-identity-device-management
2020
---
2121
# Export your provisioning configuration and roll back to a known good state
22+
2223
## Export and import your provisioning configuration from the Azure portal
2324

2425
### How can I export my provisioning configuration?
@@ -37,14 +38,14 @@ Exporting and saving your configuration allows you to roll back to a previous ve
3738
## Export and import your provisioning configuration by using the Microsoft Graph API
3839
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.
3940

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

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.
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.
4344
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.
4445

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

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

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

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

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

5859
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).
5960

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

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

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

8081
> [!CAUTION]
8182
> 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)