0
How SCIM Push Provisioning Works

Unlike SAML or OIDC (which authenticate users at login time), SCIM handles identity lifecycle management in the background: accounts are provisioned before users ever attempt to log in, and deprovisioned immediately when they leave. Here is the standard protocol sequence:

  1. Discovery & Feature Handshake: When setting up provisioning, the IdP sends GET /ServiceProviderConfig, GET /Schemas, and GET /ResourceTypes to discover which capabilities the server supports (e.g., authentication schemes, maximum filter results, bulk limits, and PATCH support).
  2. Pre-flight Existence Check: Before creating an account, the IdP queries GET /Users?filter=userName eq "john@example.com". If the user does not exist (totalResults: 0), it moves to creation. If the user already exists, the IdP captures the server's id to synchronize attributes rather than producing a duplicate.
  3. User Provisioning: The IdP issues POST /Users with the standardized SCIM JSON payload (names, emails, active status, and optional enterprise extensions like department or manager). The server creates the identity and returns HTTP 201 Created with a server-generated unique id.
  4. Incremental Updates (Delta Sync): When an employee's title, department, or status changes, Entra avoids full-object replaces. Instead, it sends a PATCH /Users/{id} containing fine-grained Operations (e.g., replace: {"title": "Staff Engineer"}).
  5. Group & Membership Synchronization: Groups are managed via POST /Groups, and members are added or removed dynamically using PATCH /Groups/{id} by referencing each user's SCIM id.
  6. Deprovisioning (Lifecycle Termination): When an account is disabled or unassigned in Entra, the IdP typically performs a soft-delete first by sending PATCH /Users/{id} with active: false. If hard deletion is configured, it subsequently sends DELETE /Users/{id}.
πŸ”’ Authentication & Security: Every request is authenticated using a Bearer token in the Authorization: Bearer <token> header. Passwords sent during creation are masked in the audit log and never written to persistent storage.
1
Your SCIM Endpoint

Generate an isolated, private SCIM 2.0 server instance. The generator provisions a unique endpoint identifier (EID) and an unguessable 256-bit cryptographic bearer token.

2
Connect Entra ID (or Test via curl)

Configure an Enterprise Application in Microsoft Entra to push identities to your new endpoint:

  1. Create Enterprise App: In Entra admin center → Enterprise applications → New application → Create your own application (select "Integrate any other application you don't find in the gallery (Non-gallery)").
  2. Configure Provisioning: Open the app → Provisioning → Get started. Set Provisioning Mode to Automatic.
  3. Authorize Endpoint: Expand Admin Credentials, paste the Tenant URL and Secret Token from Step 1, then click Test Connection. Notice in Step 3 below that Entra immediately executes a test query (GET /Users?filter=...) to verify reachability.
  4. Assign Users & Groups: Under Users and groups, assign test accounts you wish to provision.
  5. Run Provisioning: Use Provision on demand to immediately push a single user through Entra's evaluation pipeline, or click Start provisioning to initiate scheduled background cycles (runs every ~40 minutes).

Manual Testing: If you don't have access to an Entra tenant right now, execute this curl command in your terminal to simulate an identity provider pushing a newly created user:

POSTcurl example
// Create an endpoint first
3
Received Requests (Audit Log)

Real-time audit log of all inbound SCIM requests received by your endpoint (newest first). Click any request row to inspect the exact HTTP headers, payload schemas, and response status returned by the server.

Create an endpoint to start receiving requests.
4
Provisioned State (Target Database)

This view represents the target application's local identity database. As Entra ID processes lifecycle events, the server maintains the correlation between the IdP's source directory object ID (externalId) and this Service Provider's internal primary key (id). Click any user or group row to view its complete SCIM 2.0 JSON document.

No users.
No groups.