Automox 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.

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.

Meta Ads supports SCIM 2.0 provisioning through Meta Work Accounts, which is free to access. However, Meta Work Accounts is currently only available to "select customers" - meaning most organizations can't access this functionality despite it being technically free. Even when available, SCIM only works with managed Meta Work Accounts, not personal Facebook profiles, creating a complex dual-account management scenario for many teams. This selective availability creates a significant operational gap. Without automated provisioning, IT teams must manually manage Meta Ads access for marketing teams, often dealing with personal Facebook accounts that can't be centrally controlled. When employees leave, their personal accounts retain access to company ad accounts and sensitive campaign data, creating compliance and security risks that SSO alone can't address.