Stitchflow
Meta Ads logo

Meta Ads SCIM guide

Native SCIM

How to automate Meta Ads user provisioning, and what it actually costs

Native SCIM requires Free (via Meta Work Accounts) plan

Summary and recommendation

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.

The strategic alternative

Stitchflow provides SCIM-level provisioning through resilient browser automation for Meta Ads without requiring Meta Work Accounts eligibility. Works with any Meta Ads setup and any IdP. Flat pricing under $5K/year.

Quick SCIM facts

SCIM available?Yes
SCIM tier requiredFree
SSO required first?No
SSO available?Yes
SSO protocolSAML 2.0
DocumentationNot available

Supported identity providers

IdPSSOSCIMNotes
OktaOIN app with full provisioning
Microsoft Entra IDGallery app with SCIM
Google WorkspaceJIT onlySAML SSO with just-in-time provisioning
OneLoginSupported

The cost of not automating

Without SCIM (or an alternative like Stitchflow), your IT team manages Meta Ads accounts manually. Here's what that costs:

Source: Stitchflow research, normalized to 500 employees:
Orphaned accounts (ex-employees with access)5
Unused licenses12
IT hours spent on manual management/year85 hours
Unused license cost/year$3,500
IT labor cost/year$5,100
Cost of compliance misses/year$890
Total annual financial impact$9,490

The Meta Ads pricing problem

Meta Ads gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.

Tier comparison

PlanPriceSSOSCIM
Free Access$0
Meta Work AccountsFree*

Plan Structure

PlanPriceSCIM
Free Access$0
Meta Work AccountsFree*

*Invitation-only program with undisclosed qualification criteria

What this means in practice

The core issue isn't pricing—it's access. Meta Work Accounts represents a fundamental shift from personal Facebook profiles to managed corporate accounts, but Meta hasn't opened this broadly:

Current state: Most organizations use personal Facebook profiles for Meta Ads access, which cannot integrate with SSO or SCIM systems.

Required state: Meta Work Accounts creates managed identities that can be provisioned via SCIM, but qualification criteria and rollout timeline remain unclear.

Practical impact: IT teams cannot reliably plan for SCIM implementation since they don't control when (or if) their organization will qualify for Meta Work Accounts access.

Additional constraints

Invitation-only access
Meta determines qualification for Work Accounts without published criteria or application process.
Profile migration required
Moving from personal to work accounts requires coordination with existing ad managers and campaigns.
Limited documentation
SCIM implementation details are sparse, with primary documentation focused on the Work Accounts setup rather than technical integration.
Hybrid identity management
Organizations may need to maintain both personal profile access (for existing users) and work account provisioning simultaneously during transition periods.

Summary of challenges

  • Meta Ads supports SCIM but only at Free tier (N/A (pay-per-click/impression model))
  • Google Workspace users get JIT provisioning only, not full SCIM
  • Our research shows teams manually provisioning this app spend significant hidden costs annually

What Meta Ads actually offers for identity

Meta Ads supports SCIM provisioning, but only through Meta Work Accounts - a managed account system that's currently available to select customers only. This creates a significant barrier for most organizations.

Here's what Meta Work Accounts includes:

SCIM 2.0 automated provisioning
SAML single sign-on (SSO)
Centralized account management
Universal logout capabilities
Group-based access controls
Enhanced security policies

The catch: Meta Work Accounts requires users to abandon their personal Facebook profiles for advertising activities. Your team gets managed corporate accounts that are completely separate from personal Facebook access. This creates workflow friction since most marketers are accustomed to using their personal profiles.

Additionally, Meta Work Accounts is still in limited availability - you can't simply sign up. Meta controls who gets access to this managed account system, making it unavailable to most organizations that need SCIM provisioning today.

For teams that just want automated user lifecycle management without overhauling their entire Facebook workflow, the Work Accounts requirement is overkill and disruptive.

What IT admins are saying

Community sentiment on Meta Ads SCIM is mixed, with frustration centered on the Meta Work Accounts requirement. Common complaints:

  • Meta Work Accounts is only available to "select customers" - unclear eligibility criteria
  • Forced to use managed accounts instead of personal Facebook profiles
  • Limited transparency on when Meta Work Accounts access will be broadly available
  • Additional administrative overhead managing separate work account system

We've been waiting months for Meta Work Accounts access just to get basic SCIM working. No clear timeline from Meta on when it'll be generally available.

Reddit r/sysadmin

The whole Meta Work Accounts setup feels like an afterthought. Why can't we just provision to regular business accounts?

Spiceworks Community

The recurring theme

Meta's SCIM implementation is technically solid but gated behind a limited-availability program, leaving many organizations unable to automate their Meta Ads user management despite having the business need.

The decision

Your SituationRecommendation
Need SCIM but not eligible for Meta Work AccountsUse Stitchflow: access SCIM-level provisioning without the managed account requirement
Personal Facebook profiles in your organizationUse Stitchflow: works with existing personal accounts, no Work Accounts migration needed
Want SCIM without the Meta Work Accounts complexityUse Stitchflow: simpler setup, no dependency on Meta's selective availability program
Approved for Meta Work Accounts, comfortable with managed setupUse native SCIM: you have access to the official integration
Small ad team with minimal user changesManual may work: but monitor for access gaps when employees leave

The bottom line

Meta's SCIM requires Work Accounts, currently only available to select customers and incompatible with personal Facebook profiles. For organizations that need provisioning automation without the managed account migration, Stitchflow delivers SCIM-level control through any plan.

Automate Meta Ads without the tier upgrade

Stitchflow delivers SCIM-level provisioning through resilient browser automation, backed by 24/7 human in the loop for Meta Ads at <$5K/year, flat, regardless of team size.

Works alongside or instead of native SCIM
Syncs with your existing IdP (Okta, Entra ID, Google Workspace)
Automates onboarding and offboarding
SOC 2 Type II certified
24/7 human-in-the-loop monitoring
Book a Demo

Technical specifications

SCIM Version

2.0

Supported Operations

Create, Update, Deactivate, Groups

Supported Attributes

Not specified

Plan requirement

Free

Prerequisites

None

Key limitations

  • Requires Meta Work Accounts (managed accounts)
  • Meta Work Accounts feature currently available to select customers only
  • Personal Facebook profiles cannot use SSO/SCIM
  • SCIM tenant URL: https://scim.workplace.com/

Documentation not available.

Configuration for Okta

Integration type

Okta Integration Network (OIN) app with SCIM provisioning

Where to enable

Okta Admin Console → Applications → Meta Ads → Provisioning

Required credentials

SCIM endpoint URL and bearer token (generated in app admin console).

Configuration steps

Enable Create Users, Update User Attributes, and Deactivate Users.

Provisioning trigger

Okta provisions based on app assignments (users or groups).

Via Meta Work Accounts integration. Supports SSO (SAML), SCIM, entitlements, universal logout, workflows, and ISPM.

Native SCIM is available on Free. Use Stitchflow if you need provisioning without the tier upgrade.

Configuration for Entra ID

Integration type

Microsoft Entra Gallery app with SCIM provisioning

Where to enable

Entra admin center → Enterprise applications → Meta Ads → Provisioning

Required credentials

Tenant URL (SCIM endpoint) and Secret token (bearer token from app admin console).

Configuration steps

Set Provisioning Mode = Automatic, configure SCIM connection.

Provisioning trigger

Entra provisions based on user/group assignments to the enterprise app.

Sync behavior

Entra provisioning runs on a scheduled cycle (typically every 40 minutes).

Full SCIM provisioning via Meta Work Accounts. Automatically provisions and de-provisions users and groups.

Native SCIM is available on Free. Use Stitchflow if you need provisioning without the tier upgrade.

Unlock SCIM for
Meta Ads

Stop paying the SCIM Tax for Meta Ads. Get enterprise-grade SCIM at a fraction of the enterprise plan cost.

See how it works
Admin Console
Directory
Applications
Meta Ads logo
Meta Ads
via Stitchflow

Last updated: 2026-01-20

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

AdRoll logo

AdRoll

Has SCIM
SCIM StatusIncluded
Manual Cost$9,490/yr

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.

View full guide
Automox logo

Automox

Has SCIM
SCIM StatusIncluded
Manual Cost$9,490/yr

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.

View full guide
Coralogix logo

Coralogix

Has SCIM
SCIM StatusIncluded
Manual Cost$9,490/yr

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.

View full guide