Content Deep Dive

When Does Entra Run SCIM? The Provisioning Cycle Explained

Blog post from SSOJet

Post Details
Company
Date Published
Author
-
Word Count
3,631
Company Posts That Month
42
Language
English
Hacker News Points
-
Post removed?
No
Summary

Microsoft Entra ID provisions SCIM applications through an initial full synchronization followed by scheduled incremental cycles that process directory changes, typically about every 40 minutes for custom non-gallery applications, while gallery-app intervals may vary. Provision on demand can synchronize an individual user or a small group in seconds for testing or troubleshooting, but it is not intended to replace regular production synchronization. Changes to mappings or scoping filters, as well as a manual restart, trigger another full initial cycle, which re-evaluates all in-scope objects and can generate substantial lookup and update traffic. Provisioning can be delayed by large workloads, endpoint throttling, retries, dynamic-group evaluation, and quarantine, which occurs after widespread failures and progressively reduces runs to daily before disabling the job after four weeks. Administrators can inspect completed cycles, errors, and quarantine status in the Entra portal or through Microsoft Graph, although the next execution time must be estimated from the prior cycle’s completion and configured interval. Deprovisioning generally sends a SCIM PATCH setting a user’s active status to false at the next cycle, while DELETE requests occur only after a hard deletion, often 30 days after a soft deletion.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Real-time 2 2,428 550 179 -42%
Platform Engineering 1 1,145 237 66 -43%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.