Step 2—Configure connectivity to SuccessFactors ODATA API server
Azure AD needs to be configured with the account that has permissions to read data from SuccessFactors.
If you’re configuring integration with on-premises AD, there is an additional step of installing and configuring Azure AD Connect provisioning agent that is capable of provisioning to multiple AD domains. Refer to the integration tutorial for detailed steps.
Step 3—Configure scoping to define identities that will be managed with this integration
Identify which users should be provisioned from SuccessFactors to Azure AD or on-premises AD. If you want to rollout SuccessFactors HR integration gradually based on location, department or division, then you can use the scoping filters to determine which users should be provisioned.
The example below uses a scoping filter based on the department attribute:
Step 4—Configure attribute mappings
The pre-built SuccessFactors provisioning connector supports mapping 70+ different attributes from SuccessFactors. With expression mapping functions, you can apply attribute transformations such as replacing strings, concatenating values and generating unique identifiers.
Step 5—Turn on the provisioning cycle
Start the provisioning cycle and use the progress bar and provisioning logs to track the provisioning process.