A cloud-based identity and access management service for securing user authentication and resource access
Hi @VaishnaviAjitKumar-6022 - the way that our provisioning service works is that whenever a new object is being processed for the first time, our service tries to determine if a matching object exists in the connected SCIM directory. For users, we will send GET /Users?filter=userName eq "xyz" (or potentially filtering on emails[type eq "work"].value or externalId instead), and for groups we must identify between systems using either displayName or externalId. Once we've identified if there is a group or not, we either match and send any required updates, or we create a new group via POST.
In either case, matching or creating a new object, at the end we will know the SCIM id value and store that in the provisioning system. After that, we will always make calls to known resources such as GET /Groups/123?excludedAttributes=members. That id value - "123" - isn't something we can know immediately, and the use of filters on friendly names that would be shared across systems (userName, displayName, etc..) is required for the system to work.
This behavior is not changeable. You can alter what attribute is used as a matching attribute, but you cannot avoid having a matching attribute.