Closed mrmueller closed 4 years ago
Hello @mrmueller ,
Thank you for your feedback! We will review and provide an update as appropriate.
@mrmueller if you're referring to the settings in SuccessFactors then it might be better to ask them. I don't see any reason why the functionality would be different but I believe the settings you referenced are on their side.
@cmmdesai thoughts?
I have reached out to the product team on my end about this as well and am awaiting their response.
@mrmueller if you're referring to the settings in SuccessFactors then it might be better to ask them. I don't see any reason why the functionality would be different but I believe the settings you referenced are on their side.
@cmmdesai thoughts?
@MarileeTurscak-MSFT The settings I am referencing are in Azure AD on the "SuccessFactors to Active Directory User Provisioning" application.
I have reached out to the product team to ask. I don't think the functionality would be different as otherwise that probably would have been noted, but hopefully someone can confirm.
If the goal is to fine tune the scope of users that'll write back the "mail" attribute to SF, you should define a set of attribute-based filters in "Source Object Scope" field.
The attribute mappings only allow changing the "matching ID" attribute and the source Azure AD attribute for the "mail" value.
This section of the tutorial contains the details:
@mrmueller Hope you are good. Please let us know if you have any residual queries on the above explanation . If not we will proceed with closure of this thread by EOD tomorrow.
Thank you.
Hi,
Can someone please elaborate on the scoping settings. I can do it as described here (in the synchronization mappings) or i can choose to only sync assigned users under the provisioning settings (scope). What are the differences?
Obviously i can use groups to assign users to the application which i cant do in the mappings. But are there differences in functionality regarding the sync?
Thanks Martin
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.