Microsoft Entra ID
Configure automatic provisioning from a Microsoft Entra enterprise application.
1. Create the connection
- In Entra admin center, open an enterprise application and select Provisioning.
- Choose automatic provisioning.
- Set Tenant URL to
https://api.niah.si/scim/v2. - Set Secret Token to a Niah organization API key with
scim:readandscim:write. - Run Test Connection and save.
2. Configure user mappings
| Microsoft Entra attribute | SCIM target | Notes |
|---|---|---|
userPrincipalName or mail | userName | Required matching property; use an email-form value |
givenName | name.givenName | Optional |
surname | name.familyName | Optional |
mail | emails[type eq "work"].value | Use the same address as userName |
Switch([IsSoftDeleted], ...) | active | Keep Entra's generated active-status expression |
Enable Create and Update for users. Niah accepts PATCH operation names without regard to casing, including Entra's Replace form.
3. Scope and start provisioning
Assign users and groups to the enterprise application, choose “Sync only assigned users and groups” unless tenant-wide provisioning is intended, and start provisioning. Use Provision on demand for a first user before the full cycle.
Groups
Enable group Create, Update, and Delete mappings when assigned groups should become Niah teams. Map displayName to displayName and members to members.
Deprovisioning
Disabling or unassigning a user must produce active=false. Niah deactivates organization membership and retains identity data for reactivation. User DELETE is unsupported; a later hard-delete attempt may be reported as a non-fatal provisioning error by Entra.