Skip to content

Commit f512bd4

Browse files
authored
Updates for clarity.
1 parent db7978f commit f512bd4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1202,7 +1202,7 @@ In the example of a request, to retrieve the current state of a user, the values
12021202

12031203
***Example 4. Query the value of a reference attribute to be updated***
12041204

1205-
If a reference attribute is to be updated, then Azure AD queries the service to determine whether the current value of the reference attribute in the identity store fronted by the service already matches the value of that attribute in Azure AD. For users, the only attribute of which the current value is queried in this way is the manager attribute. Here's an example of a request to determine whether the manager attribute of a user object currently has a certain value:
1205+
Azure AD checks the current attribute value in the identity store before updating it. However, only the manager attribute is the checked first for users. Here's an example of a request to determine whether the manager attribute of a user object currently has a certain value:
12061206
In the sample code, the request is translated into a call to the QueryAsync method of the services provider. The value of the properties of the object provided as the value of the parameters argument are as follows:
12071207

12081208
* parameters.AlternateFilters.Count: 2

0 commit comments

Comments
 (0)