Skip to content

Commit dedecad

Browse files
authored
Update harness-provisioning-tutorial.md
1 parent 1389a5a commit dedecad

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/active-directory/saas-apps/harness-provisioning-tutorial.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Before you configure and enable automatic user provisioning, decide which users
7070

7171
1. Select **Submit**.
7272

73-
1. Copy the **Key**. You'll enter this value in the Secret Token field in the Provisioning tab of your Harness application in the Azure portal.
73+
1. Copy the **Key** for later use in this tutorial.
7474

7575
![Harness Create Token](media/harness-provisioning-tutorial/token.png)
7676

@@ -126,8 +126,8 @@ To configure automatic user provisioning for Harness in Azure AD, do the followi
126126

127127
![Tenant URL + Token](common/provisioning-testconnection-tenanturltoken.png)
128128

129-
a. In the **Tenant URL** box, enter **https://app.harness.io/gateway/api/scim/account/XCPzWkCIQ46ypIu2DeT7yw**.
130-
b. In the **Secret Token** box, enter the SCIM Authentication Token value that you saved earlier.
129+
a. In the **Tenant URL** box, enter **`https://app.harness.io/gateway/api/scim/account/XCPzWkCIQ46ypIu2DeT7yw`**.
130+
b. In the **Secret Token** box, enter the SCIM Authentication Token value that you saved in step 6 of the "Set up Harness for provisioning" section.
131131
c. Click **Test Connection** to ensure that Azure AD can connect to Harness. If the connection fails, ensure that your Harness account has *Admin* permissions, and then try again.
132132

133133
1. In the **Notification Email** box, enter the email address of a person or group that should receive the provisioning error notifications, and then select the **Send an email notification when a failure occurs** check box.
@@ -166,7 +166,7 @@ To configure automatic user provisioning for Harness in Azure AD, do the followi
166166

167167
![The provisioning Save button](common/provisioning-configuration-save.png)
168168

169-
This operation starts the initial synchronization of all users or groups defined in **Scope** in the **Settings** section. The initial sync takes longer to perform than subsequent syncs, Syncs occur approximately every 40 minutes, as long as the Azure AD provisioning service is running. You can use the **Synchronization Details** section to monitor progress. You can also follow links to a provisioning activity report, which describes all actions performed by the Azure AD provisioning service on Harness.
169+
This operation starts the initial sync of the users or groups you're provisioning. The initial sync takes longer to perform than later ones. Syncs occur approximately every 40 minutes, as long as the Azure AD provisioning service is running. To monitor progress, go to the **Synchronization Details** section. You can also follow links to a provisioning activity report, which describes all actions performed by the Azure AD provisioning service on Harness.
170170

171171
For more information about how to read the Azure AD provisioning logs, see [Report on automatic user account provisioning](../manage-apps/check-status-user-account-provisioning.md).
172172

0 commit comments

Comments
 (0)