Microsoft 365 SCIM guide

AdRoll supports native SCIM 2.0 provisioning, but only on Enterprise plans with custom pricing. The implementation requires SAML SSO to be configured first, and setup involves working directly with AdRoll support to obtain bearer tokens and complete the integration. For teams on Pro ($36/month) or Business plans, there's no automated user provisioning available—IT admins must manually manage user accounts and access. This creates a significant operational burden for growing marketing teams. Without automated provisioning, every new hire requires manual account creation, role assignment, and access configuration across AdRoll's advertising campaigns and audiences. When employees leave, IT teams risk leaving orphaned accounts with access to sensitive advertising data and campaign budgets. The gap between affordable plans and Enterprise pricing forces many organizations to choose between manual overhead and potentially expensive upgrades.

Automox offers native SCIM 2.0 provisioning, but only on their Enterprise plan with custom pricing. Lower tiers (Pro starting at $1/endpoint/month and Automate Essentials) are limited to JIT provisioning through SAML, which creates users only on first login with default Read Only permissions. This forces manual role adjustments for every new user and creates a gap between when access is granted in your IdP and when users can actually perform their job functions in Automox. The JIT-only approach on lower tiers creates compliance headaches for IT teams. Users appear "provisioned" in your identity provider but remain non-functional until they log in and administrators manually adjust their permissions. For patch management and endpoint security tools like Automox, this delay can leave critical systems unmanaged while you wait for manual intervention.

Coralogix supports native SCIM 2.0 provisioning on all paid plans (Business and Enterprise), but requires SSO configuration as a prerequisite. While this seems straightforward, Coralogix's custom pricing model means you'll need to negotiate directly with sales to understand the true cost of SCIM-enabled plans, creating procurement friction for what should be standard identity management functionality. The SSO-first requirement creates an additional deployment dependency that can complicate rollouts, especially in organizations where SCIM provisioning and SSO implementation are managed by different teams or have different timelines. This architectural coupling means you can't implement automated user lifecycle management without first configuring federated authentication, even if your immediate need is just provisioning automation.