Configure Server-Side Filtering in Entra ID (AAD)¶
Privacera supports server-side filtering when syncing users and groups from Azure Active Directory (AAD). When using server-side filtering, UserSync can not use incremental sync and will perform a full search every sync cycle.
Setup¶
Go to the Privacera Manager host and navigate to the Privacera Manager installation directory:
Ensure that incremental search is disabled:
| YAML | |
|---|---|
Add or update the following variables based on desired configuration:
Values are formatted as operator;filter,filter,filter. The operator can be eq (equals) or sw (starts with). The filter is the value to filter on. Multiple filters can be specified by separating them with a comma.
Because Microsoft Graph filters in this connector only support eq and sw (see above), patterns such as "ends with" or mid-string wildcards cannot be expressed in the server-side variables alone. Use a manage list (AZURE_AD_MANAGE_GROUP_LIST, AZURE_AD_MANAGE_USER_LIST, or AZURE_AD_MANAGE_SERVICEPRINCIPAL_LIST) when you need wildcard or other pattern matching.
Entra ID returns objects that match the server-side filter; UserSync then keeps only those that also match the manage list. When a manage list is set, objects that do not match any entry (including wildcard entries) on that list are ignored.
For example, to sync groups whose names start with Group_ and end with Admin, narrow the Graph request with a starts-with filter and restrict results with a wildcard on the manage list:
Restart Privacera Services¶
- Prev topic: Advanced Configuration