Skip to content

Commit 76bd934

Browse files
Update export-import-provisioning-configuration.md
1 parent b95d5dd commit 76bd934

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,23 +22,23 @@ ms.collection: M365-identity-device-management
2222

2323
## Export and import your provisioning configuration from the Azure portal
2424

25-
### How can I export my provisioning configration?
25+
### How can I export my provisioning configuration?
2626
To export your configuration:
2727
1. In the [Azure portal](https://portal.azure.com/), on the left navigation panel, select **Azure Active Directory**.
2828
2. In the **Azure Active Directory** pane, select **Enterprise applications** and choose your application.
29-
3. In the left navigation pane, select **provisioning**. From the provisioning configuration page, click on on **attribute mappings**, then **show advanced options**, and finally **review your schema**. This will take you to the scehma editor.
29+
3. In the left navigation pane, select **provisioning**. From the provisioning configuration page, click on **attribute mappings**, then **show advanced options**, and finally **review your schema**. This will take you to the schema editor.
3030
5. Click on download in the command bar at the top of the page to download your schema.
3131

3232
### Disaster recovery - roll back to a known good state
33-
Exporting and saving your configuration allows you to roll back to a previous version of your configuration. We recommend exporting your provisioning configuration and saving it for later use any time you make a change to your attribute mappings or scoping filters. All you need to do is open up the JSON file that you downloaded in the steps above, copy the entire contents of the JSON file, replace the entire contents of the JSON payload in the schema editor, and then save. If there is an active provisioning cycle, it will complete and the next cycle will use the updated schema. The next cycle will also be an initial cycle which reevaluates every user and group based on the new configuration.
33+
Exporting and saving your configuration allows you to roll back to a previous version of your configuration. We recommend exporting your provisioning configuration and saving it for later use anytime you make a change to your attribute mappings or scoping filters. All you need to do is open up the JSON file that you downloaded in the steps above, copy the entire contents of the JSON file, replace the entire contents of the JSON payload in the schema editor, and then save. If there is an active provisioning cycle, it will complete and the next cycle will use the updated schema. The next cycle will also be an initial cycle, which reevaluates every user and group based on the new configuration.
3434

3535

3636
## Export and import your provisioning configuration by using the Microsoft Graph API
3737
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.
3838

3939
### Step 1: Retrieve your Provisioning App Service Principal ID (Object ID)
4040

41-
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.
41+
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.
4242
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.
4343

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

0 commit comments

Comments
 (0)