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 required | Enterprise |
| SSO required first? | Yes |
| SSO available? | Yes |
| SSO protocol | SAML 2.0, OAuth, OIDC |
| Documentation | Official docs |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | ✓ | ✓ | OIN app with full provisioning |
| Microsoft Entra ID | ✓ | ✓ | Gallery app with SCIM |
| Google Workspace | ✓ | JIT only | SAML SSO with just-in-time provisioning |
| OneLogin | ✓ | ✓ | Supported |
The cost of not automating
Without SCIM (or an alternative like Stitchflow), your IT team manages ServiceNow accounts manually. Here's what that costs:
The ServiceNow pricing problem
ServiceNow gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Standard ITSM | $100/user/mo | ||
| Pro (with AI) | $160+/user/mo | ||
| Enterprise | $50-75/user/mo at scale (1000+ users) |
Plan Structure
| Plan | Price | SCIM |
|---|---|---|
| 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 Size | Estimated Annual Cost | Monthly 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
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:
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.
Setting up SCIM requires disabling SAML auto-provisioning, but this isn't clearly documented upfront, leading to provisioning conflicts.
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 Situation | Recommendation |
|---|---|
| On Standard ITSM, need SCIM | Use Stitchflow: avoid the Enterprise upgrade costs |
| Using Azure/Entra ID | Use Stitchflow: avoid the SOAP vs SCIM complexity |
| Need SCIM but under 1,000 users | Use Stitchflow: Enterprise pricing only scales at volume |
| Already on Enterprise at scale | Use native SCIM: you're paying for it |
| Small IT team, manual user management works | Manual 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.
Technical specifications
SCIM Version
2.0
Supported Operations
Create, Update, Deactivate, Groups
Supported Attributes
Not specifiedPlan 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
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
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


