Stitchflow
ServiceNow logo

ServiceNow SCIM guide

Native SCIM

How to automate ServiceNow user provisioning, and what it actually costs

Native SCIM requires Enterprise plan

Summary and recommendation

ServiceNow supports native SCIM provisioning, but it requires Enterprise plans ($50-75/user/month at scale) and comes with configuration complexity that creates real operational risk. The Azure gallery app uses SOAP instead of true SCIM—you need to configure a non-gallery Enterprise app for SCIM compliance. Additionally, you must disable SAML auto-provisioning when using SCIM to avoid conflicts between the two systems.

This creates a critical gap for IT teams managing ServiceNow across departments (IT, HR, facilities). Without proper user pre-provisioning, incident tickets can't be automatically assigned to users who haven't logged in yet, forcing manual intervention and creating service delays. The configuration complexity around SAML/SCIM conflicts means many organizations either stick with manual provisioning or risk misconfigurations that break authentication flows.

The strategic alternative

ServiceNow gates SCIM behind Enterprise. Skip the Enterprise plan upgrade and automate complete outcomes across your stack. We maintain the integration layer underneath. You focus on judgment, not plumbing.

Quick SCIM facts

SCIM available?Yes
SCIM tier requiredEnterprise
SSO required first?Yes
SSO available?Yes
SSO protocolSAML 2.0, OAuth, OIDC
DocumentationOfficial docs

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 ServiceNow accounts manually. Here's what that costs:

Source: Stitchflow aggregate data across apps with 2+ instances, normalized to 500 employees
Orphaned accounts (ex-employees with access)7
Unused licenses12
IT hours spent on manual management/year101 hours
Unused license cost/year$3,925
IT labor cost/year$6,088
Cost of compliance misses/year$1,741
Total annual financial impact$11,754

The ServiceNow pricing problem

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

Tier comparison

PlanPriceSSOSCIM
Standard ITSM$100/user/mo
Pro (with AI)$160+/user/mo
Enterprise$50-75/user/mo at scale (1000+ users)

Plan Structure

PlanPriceSCIM
Standard ITSM$100/user/mo
Pro (with AI)$160+/user/mo
Enterprise$50-75/user/mo at scale (1000+ users)

Note: Enterprise pricing requires volume commitments (typically 1000+ users). Smaller organizations face significantly higher per-user costs or must purchase minimum seat blocks.

What this means in practice

ServiceNow's Enterprise requirement creates a high barrier to entry for SCIM access:

Team SizeEstimated Annual CostMonthly Commitment
100 users$180,000-240,000/year$15,000-20,000/mo
500 users$450,000-600,000/year$37,500-50,000/mo
1000+ users$600,000-900,000/year$50,000-75,000/mo

Average ServiceNow contract: $130,080/year (though this likely includes smaller deployments without SCIM access)

Additional constraints

Volume requirements
Enterprise tier pricing assumes significant user counts, making it cost-prohibitive for smaller teams needing SCIM.
Configuration complexity
Azure's gallery app uses SOAP instead of SCIM—organizations must use non-gallery Enterprise applications for true SCIM compliance.
Provisioning conflicts
SAML auto-provisioning must be disabled when implementing SCIM to avoid user management conflicts.
Annual uplift
ServiceNow contracts typically include 5-10% annual price increases.
AI consumption costs
Pro tier AI features now use usage-based billing on top of seat costs.

Summary of challenges

  • ServiceNow supports SCIM but only at Enterprise tier ($50-75/user/mo at scale (1000+ users))
  • Google Workspace users get JIT provisioning only, not full SCIM
  • Our research shows teams manually provisioning this app spend significant hidden costs annually

What the upgrade actually includes

ServiceNow doesn't sell SCIM separately. It's bundled with Enterprise platform features at $50-75/user/month for large deployments:

SCIM 2.0 automated provisioning (native endpoint)
SAML 2.0 single sign-on
Advanced workflow automation
IT service management suite
HR service delivery modules
Custom application development platform
Advanced reporting and analytics
Enterprise-grade security controls
Premium support tiers

Additional complexity: Microsoft Entra's gallery app uses SOAP (not true SCIM), requiring a non-gallery Enterprise application setup for SCIM compliance. You'll also need to disable SAML auto-provisioning to avoid conflicts—adding configuration overhead to an already expensive upgrade.

Stitchflow Insight

The challenge: ServiceNow is an enterprise service management platform, not just an identity target. You're paying for ITSM, HRSD, and development capabilities that most organizations using ServiceNow as a secondary app won't fully utilize. We estimate ~60% of Enterprise features are overkill for teams that primarily need ServiceNow for basic IT ticketing with automated user provisioning.

What IT admins are saying

Community sentiment on ServiceNow's SCIM implementation is mixed, with frustration centered on configuration complexity and Microsoft integration issues. Common complaints:

  • Azure gallery app uses SOAP instead of proper SCIM, requiring non-gallery setup
  • Configuration conflicts between SAML auto-provisioning and SCIM that must be manually disabled
  • Complex endpoint URL requirements and careful planning needed to avoid setup failures
  • Enterprise pricing requirements that can reach $100+/user/month for basic ITSM

The Azure gallery app not being truly SCIM compliant is a major pain point - you have to use the non-gallery Enterprise app and disable SAML provisioning to avoid conflicts.

ServiceNow Community

Setting up SCIM requires disabling SAML auto-provisioning, but this isn't clearly documented upfront, leading to provisioning conflicts.

Reddit IT Admin

The recurring theme

ServiceNow has native SCIM, but Microsoft integrations are problematic and the setup process requires deep technical knowledge to avoid common pitfalls.

The decision

Your SituationRecommendation
On Standard ITSM, need SCIMUse Stitchflow: avoid the Enterprise upgrade costs
Using Azure/Entra IDUse Stitchflow: avoid the SOAP vs SCIM complexity
Need SCIM but under 1,000 usersUse Stitchflow: Enterprise pricing only scales at volume
Already on Enterprise at scaleUse native SCIM: you're paying for it
Small IT team, manual user management worksManual may suffice: but consider incident assignment delays

The bottom line

ServiceNow's Enterprise pricing requirement means SCIM costs significantly more for smaller teams, while Azure's gallery app creates technical complexity with SOAP instead of true SCIM. Stitchflow delivers proper SCIM provisioning without the Enterprise upgrade or integration headaches.

Make ServiceNow workflows AI-native

ServiceNow gates SCIM behind Enterprise. We build complete offboarding, user access reviews, and license workflows without that SCIM Tax upgrade.

No Enterprise upgrade required
Less than a week, start to finish (~2 hours of your time)
We maintain the integration layer underneath
Book a Demo

Technical specifications

SCIM Version

2.0

Supported Operations

Create, Update, Deactivate, Groups

Supported Attributes

Not specified

Plan requirement

Enterprise

Prerequisites

SSO must be configured first

Key limitations

  • Azure gallery app uses SOAP not SCIM - use non-gallery for SCIM compliance
  • Must disable SAML auto-provisioning when using SCIM to avoid conflicts
  • SCIM endpoint URL format specific: /api/now/scim

Configuration for Okta

Integration type

Okta Integration Network (OIN) app with SCIM provisioning

Prerequisite

SSO must be configured before enabling SCIM.

Where to enable

Okta Admin Console → Applications → ServiceNow → 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).

Enterprise required for SCIM

ServiceNow gates SCIM behind Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.

Configuration for Entra ID

Integration type

Microsoft Entra Gallery app with SCIM provisioning

Prerequisite

SSO must be configured before enabling SCIM.

Where to enable

Entra admin center → Enterprise applications → ServiceNow → 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).

Enterprise required for SCIM

ServiceNow gates SCIM behind Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.

Unlock SCIM for
ServiceNow

ServiceNow gates SCIM behind Enterprise plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade, avoiding a 900% markup.

See how it works
Admin Console
Directory
Applications
ServiceNow logo
ServiceNow
via Stitchflow

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

8x8 logo

8x8

SCIM Tax

UCaaS / Business Communications

SCIM StatusIncluded
Manual Cost$11,754/yr

8x8 supports SCIM 2.0 for automated user provisioning, but only on their quote-based X Series plans (previously $24-44/user/month range before they moved to custom pricing). While SCIM can create, update, and deactivate users, it has critical gaps that create ongoing manual overhead: license assignment must be done manually after every user is provisioned, users can't be deleted (only deactivated), and provisioned users don't automatically appear in the Company Directory. For IT teams managing a unified communications platform that typically covers all employees, these limitations defeat much of SCIM's purpose. You're still manually touching every user account to assign licenses and ensure directory visibility. The lack of user deletion support also creates compliance headaches when employees leave - accounts accumulate as "deactivated" rather than being properly removed.

View full guide
Absorb LMS logo

Absorb LMS

SCIM Tax

Learning Management System (LMS)

SCIM StatusIncluded
Manual Cost$11,754/yr

Absorb LMS supports native SCIM provisioning, but only on Enterprise plans with SSO as a required paid add-on. Even with SCIM enabled, the implementation has critical limitations: SAML provisioning only creates accounts on first login and never updates existing users, and full user provisioning requires the specific "Absorb 5 - New Learner Experience" version. For organizations managing compliance training across hundreds or thousands of learners, these gaps create ongoing manual work. The SSO-as-add-on model means you're paying extra fees on top of already custom Enterprise pricing ($6-12/user/month base, but varies significantly). For learning management systems handling external partners, contractors, and employees across different access levels, the inability to update existing user attributes through SAML provisioning forces IT teams into manual account management—exactly what automated provisioning should eliminate.

View full guide
Airbase logo

Airbase

SCIM Tax

Spend Management / Corporate Cards

SCIM StatusIncluded
Manual Cost$11,754/yr

Airbase supports SCIM provisioning, but only on Enterprise plans starting around $8,500/year. While SCIM works with all major identity providers (Okta, Entra ID, Google Workspace), the Enterprise requirement creates a significant barrier for smaller finance teams who need automated provisioning for spend management but can't justify enterprise-level spend management software costs. This creates a particular challenge in finance applications where rapid provisioning and deprovisioning is critical for corporate card access and financial controls. Manual user management means delayed access for new employees needing corporate cards, and more critically, potential security gaps when departing employees retain access to spend management systems. For finance teams handling sensitive financial data and corporate spending, these delays and oversights create both operational friction and compliance risks.

View full guide