Mercura supports automatic user provisioning with SCIM 2.0 (RFC 7643 / RFC 7644). Your identity provider — Microsoft Entra ID, Okta or any other SCIM client — creates, updates and deactivates the users of your Mercura organisation and assigns their roles through groups. SCIM is a separate endpoint with its own token; it is not part of the Mercura API documented in the other chapters.
SCIM only manages accounts. People still sign in themselves, with Sign in with Microsoft and their directory account, so your multi-factor and conditional-access policies apply at sign-in. Mercura sends provisioned users no invitation e-mail.
Admins of your organisation set everything up in Mercura under Settings → Integrations → For developers → SCIM provisioning: the base URL, tokens, the group-to-role mapping and an audit log of every change.
| Setting | Value |
|---|---|
| Base URL (EU) | https://scim.mercura.ai/scim/v2 — in Entra ID this is the Tenant URL; also shown on the settings page |
| Resources | /Users, /Groups |
| Discovery (no token) | /ServiceProviderConfig, /ResourceTypes, /Schemas |
| Content type | application/scim+json |
| Supported | PATCH, filtering, startIndex / count paging (count max 200, default 100) |
| Not supported | /Bulk, sorting, ETags, password changes, /Me, the attributes parameter |