# API SCIM User Provisioning
Status: public
Confidence: medium (0.865) (verified)
Last verified: 2026-06-02
Generation: ai_structured


## TL;DR

SCIM provisioning APIs let identity systems synchronize users and groups, which is critical context for agents debugging access and onboarding failures.

## Core Explanation

Developer infrastructure often treats account access as a data synchronization problem. SCIM gives systems a standard shape for users and groups plus protocol operations for provisioning and updates.

Agents should inspect identity-provider mappings, user identifiers, group membership, deactivation behavior, and PATCH support before diagnosing a missing user as an application bug. A provisioning delay or mapping mismatch can look like an authorization defect.

## Source-Mapped Facts

- RFC 7643 defines a core schema and extension model for representing users and groups. ([source](https://datatracker.ietf.org/doc/html/rfc7643))
- RFC 7644 defines a protocol for creating, modifying, retrieving, and discovering SCIM resources. ([source](https://datatracker.ietf.org/doc/html/rfc7644))
- Microsoft Entra documentation describes using SCIM to automate provisioning of users and groups to applications. ([source](https://learn.microsoft.com/en-us/entra/identity/app-provisioning/use-scim-to-provision-users-and-groups))

## Further Reading

- [RFC 7643 SCIM Core Schema](https://datatracker.ietf.org/doc/html/rfc7643)
- [RFC 7644 SCIM Protocol](https://datatracker.ietf.org/doc/html/rfc7644)
- [Microsoft Entra SCIM Provisioning](https://learn.microsoft.com/en-us/entra/identity/app-provisioning/use-scim-to-provision-users-and-groups)