Stitchflow
xMatters logo

xMatters SCIM guide

Native SCIM

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

Native SCIM requires Enterprise plan

Summary and recommendation

xMatters supports SCIM 2.0 for automated user provisioning, but only on Enterprise plans with custom pricing. The SCIM implementation has notable technical quirks: tokens for Entra ID aren't refreshable (creating ongoing maintenance overhead), SCIM endpoints must end in 'tokens' with an 's' (easy to misconfigure), and native login requires special role assignment after SSO is enabled.

For incident management platforms like xMatters, provisioning accuracy is critical—outdated contact information or missing user accounts can delay incident response when every minute counts. The Enterprise pricing requirement means most teams face a significant cost barrier to access automated provisioning, leaving them with manual user management that's both time-intensive and error-prone during critical incidents.

The strategic alternative

xMatters 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
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 xMatters 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 xMatters pricing problem

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

Tier comparison

PlanPriceSSOSCIM
Starter$16/user/mo
Base$39/user/mo
Advanced$59/user/mo
EnterpriseCustom pricing

Plan Structure

PlanPriceSCIM
Starter$16/user/mo
Base$39/user/mo
Advanced$59/user/mo
EnterpriseCustom pricing

Note: xMatters provides full SCIM 2.0 support in Enterprise, including user lifecycle management and group provisioning with OAuth authentication.

What this means in practice

Without published Enterprise pricing, organizations must:

Enter sales negotiations
for what should be a standard IT capability
Accept bundled enterprise features
they may not need
Navigate custom contract terms
that can extend procurement cycles by months

For incident management platforms, this pricing model is particularly problematic because accurate user provisioning directly impacts service reliability - you can't afford to have outdated on-call rosters during critical incidents.

Additional constraints

Custom enterprise pricing
No transparent pricing means lengthy procurement cycles and budget uncertainty.
IdP limitations
Native SCIM only works with Okta and Azure AD - no support for Google Workspace or OneLogin despite being enterprise-tier.
Token refresh issues
SCIM tokens for Entra ID are not refreshable, creating potential authentication failures.
Endpoint specificity
SCIM endpoint URLs must end in 'tokens' (with s) - a technical quirk that can cause integration failures.

Summary of challenges

  • xMatters supports SCIM but only at Enterprise tier (custom pricing)
  • 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

xMatters doesn't sell SCIM standalone. It requires their Enterprise plan, which bundles SCIM with incident management features:

SCIM 2.0 automated provisioning
SAML single sign-on (SSO)
Advanced on-call scheduling
Escalation rules and workflows
Multi-channel alerting (voice, SMS, email, push)
Integration hub with monitoring tools
Advanced reporting and analytics
Dedicated customer success manager

The pricing jump is significant—from $59/user/month (Advanced) to custom Enterprise pricing that typically starts around $100+/user/month for full SCIM access.

Stitchflow Insight

If you're already using xMatters for incident response, the Enterprise upgrade makes sense. But if you just need SCIM for basic user provisioning, you're paying enterprise prices for incident management capabilities you may not need. We estimate ~80% of Enterprise features are specific to on-call operations and service reliability workflows.

What IT admins are saying

Community sentiment on xMatters's SCIM implementation reveals specific technical frustrations despite strong feature support. Common complaints:

  • Non-refreshable SCIM tokens in Entra ID requiring manual rotation
  • Confusing endpoint naming requirements (must end with 'tokens' plural)
  • Enterprise-only pricing barrier for smaller DevOps teams
  • Complex role requirements just to configure SSO and provisioning

The SCIM token issue with Azure AD is a real pain point - you have to manually regenerate tokens instead of them refreshing automatically like other apps.

Reddit r/sysadmin

Love the incident management features, but why do I need Company Supervisor role just to set up SSO? Makes delegation impossible.

xMatters Community Forum

The recurring theme

xMatters delivers robust SCIM functionality but creates operational overhead through token management issues and restrictive role requirements that complicate enterprise deployments.

The decision

Your SituationRecommendation
On Starter ($16/user), need SCIMUse Stitchflow: avoid the Enterprise upgrade entirely
Evaluating xMatters but Enterprise pricing is prohibitiveUse Stitchflow: get provisioning automation at any tier
Already on Enterprise with SCIMUse native SCIM: you're paying for it
Using Entra ID and need reliable token managementUse Stitchflow: avoid the non-refreshable token limitation
Small on-call team, infrequent user changesManual may work: but monitor for stale contact data during incidents

The bottom line

xMatters requires Enterprise pricing for SCIM, creating a significant cost barrier from their $16/user Starter plan. For teams that need reliable user provisioning for incident response without the Enterprise upgrade, Stitchflow delivers the automation at a fraction of the cost.

Make xMatters workflows AI-native

xMatters 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

  • SCIM tokens for Entra are not refreshable
  • SCIM endpoint must end in 'tokens' (with s)
  • Native login requires special role after SSO enabled

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 → xMatters → 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).

Full SCIM 2.0 support. Uses SCIM 2.0 Test App (Basic Auth) template. Supports user and group sync.

xMatters 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 → xMatters → 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).

Non-gallery app setup required. Sync every 40 minutes. Some attributes need manual creation.

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

Unlock SCIM for
xMatters

xMatters gates SCIM behind Enterprise plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade.

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

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

VictorOps logo

VictorOps

No SCIM

DevOps / Incident Management

ProvisioningNot Supported
Manual Cost$11,754/yr

Splunk On-Call (formerly VictorOps) offers limited SCIM provisioning exclusively on Enterprise plans, but with significant restrictions that make it impractical for most IT teams. While the integration can create and deactivate users through Okta, it cannot update user profiles or attributes—meaning any changes to names, contact information, or roles in your IdP won't sync to On-Call. Worse, the SCIM setup requires opening a support ticket rather than self-service configuration, and deprovisioning permanently deletes critical incident response data including contact methods and escalation policy assignments. This creates a dangerous gap for incident management teams. On-call rotations depend on accurate, up-to-date contact information and team assignments. When profile updates don't sync automatically, engineers may miss critical alerts due to outdated phone numbers or email addresses. The permanent data deletion during deprovisioning means you lose historical escalation patterns and must manually rebuild contact methods if someone rejoins the team—exactly the opposite of what you need during high-pressure incident scenarios.

View full guide
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