Skip to content

Commit 839b1ee

Browse files
authored
Merge pull request #101675 from shashishailaj/patch-73
(Azure CXP) Update document.
2 parents b03cf06 + 93fbb31 commit 839b1ee

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/active-directory/saas-apps/sap-successfactors-inbound-provisioning-tutorial.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -340,15 +340,15 @@ Once your attribute mapping configuration is complete, you can now [enable and l
340340
Once the SuccessFactors provisioning app configurations have been completed, you can turn on the provisioning service in the Azure portal.
341341

342342
> [!TIP]
343-
> By default when you turn on the provisioning service, it will initiate provisioning operations for all users in scope. If there are errors in the mapping or Workday data issues, then the provisioning job might fail and go into the quarantine state. To avoid this, as a best practice, we recommend configuring **Source Object Scope** filter and testing your attribute mappings with a few test users before launching the full sync for all users. Once you have verified that the mappings work and are giving you the desired results, then you can either remove the filter or gradually expand it to include more users.
343+
> By default when you turn on the provisioning service, it will initiate provisioning operations for all users in scope. If there are errors in the mapping or SuccessFactors data issues, then the provisioning job might fail and go into the quarantine state. To avoid this, as a best practice, we recommend configuring **Source Object Scope** filter and testing your attribute mappings with a few test users before launching the full sync for all users. Once you have verified that the mappings work and are giving you the desired results, then you can either remove the filter or gradually expand it to include more users.
344344
345345
1. In the **Provisioning** tab, set the **Provisioning Status** to **On**.
346346

347347
2. Click **Save**.
348348

349349
3. This operation will start the initial sync, which can take a variable number of hours depending on how many users are in the SuccessFactors tenant. You can check the progress bar to the track the progress of the sync cycle.
350350

351-
4. At any time, check the **Audit logs** tab in the Azure portal to see what actions the provisioning service has performed. The audit logs lists all individual sync events performed by the provisioning service, such as which users are being read out of Workday and then subsequently added or updated to Active Directory.
351+
4. At any time, check the **Audit logs** tab in the Azure portal to see what actions the provisioning service has performed. The audit logs lists all individual sync events performed by the provisioning service, such as which users are being read out of SuccessFactors and then subsequently added or updated to Active Directory.
352352

353353
5. Once the initial sync is completed, it will write an audit summary report in the **Provisioning** tab, as shown below.
354354

0 commit comments

Comments
 (0)