Skip to content

Commit d336846

Browse files
Merge pull request #230820 from kenwith/patch-48
Updates for acrolinx.
2 parents 07e1678 + 1fb9960 commit d336846

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: app-provisioning
99
ms.workload: identity
1010
ms.topic: tutorial
11-
ms.date: 03/14/2023
11+
ms.date: 03/15/2023
1212
ms.author: kenwith
1313
ms.reviewer: arvinh
1414
---
@@ -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
@@ -1304,7 +1304,7 @@ Check with your application provider, or your application provider's documentati
13041304

13051305
### Getting started
13061306

1307-
Applications that support the SCIM profile described in this article can be connected to Azure AD using the "non-gallery application" feature in the Azure AD application gallery. Once connected, Azure AD runs a synchronization process every 40 minutes where it queries the application's SCIM endpoint for assigned users and groups, and creates or modifies them according to the assignment details.
1307+
Applications that support the SCIM profile described in this article can be connected to Azure AD using the "non-gallery application" feature in the Azure AD application gallery. Once connected, Azure AD runs a synchronization process. The process runs every 40 minutes. The process queries the application's SCIM endpoint for assigned users and groups, and creates or modifies them according to the assignment details.
13081308

13091309
**To connect an application that supports SCIM:**
13101310

@@ -1398,7 +1398,7 @@ The provisioning service supports the [authorization code grant](https://tools.i
13981398
> [!NOTE]
13991399
> OAuth v1 is not supported due to exposure of the client secret. OAuth v2 is supported.
14001400

1401-
It is recommended, but not required, that you support multiple secrets for easy renewal without downtime.
1401+
It's recommended, but not required, that you support multiple secrets for easy renewal without downtime.
14021402

14031403
#### How to set up OAuth code grant flow
14041404

0 commit comments

Comments
 (0)