Stitchflow
Atlassian logo

Atlassian SCIM guide

Native SCIM

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

Native SCIM requires Atlassian Guard subscription plan

Summary and recommendation

Atlassian supports SCIM (the protocol that lets your identity provider automatically create, update, and remove user accounts), but requires a separate Atlassian Guard subscription on top of your existing product licenses. Guard Standard costs $3-4/user/month additional, meaning a 100-person organization pays $3,600-4,800/year extra just for provisioning capabilities. The hidden complexity: Guard billing is per "managed user" across your entire Atlassian organization, not per active product license.

Recent changes make this even more operationally burdensome. As of January 2025, SCIM API keys now expire after one year, requiring mandatory annual rotation. Plus, portal-only accounts (common in Jira Service Management for external users) won't support SCIM until Q2 2025, leaving a provisioning gap for customer support workflows.

The strategic alternative

Atlassian gates SCIM behind Atlassian Guard subscription. Skip the Atlassian Guard subscription 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 Atlassian accounts manually. Here's what that costs:

Source: Stitchflow customers using Atlassian, normalized to 500 employees:
Orphaned accounts (ex-employees with access)16
Unused licenses16
IT hours spent on manual management/year96 hours
Unused license cost/year$2,338
IT labor cost/year$5,784
Cost of compliance misses/year$3,825
Total annual financial impact$11,946

The Atlassian pricing problem

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

Tier comparison

PlanPriceSSOSCIM
Standard ProductsVaries by product
+ Guard Standard+$3-4/user/month
+ Guard Premium+$8/user/month
Enterprise CloudIncludes Guard Standard

Guard Pricing Structure

PlanPriceSSOSCIM
Standard ProductsVaries by product
+ Guard Standard+$3-4/user/month
+ Guard Premium+$8/user/month
Enterprise CloudIncludes Guard Standard

Note: Guard Standard includes SSO, SCIM, and API controls. Guard Premium adds anomaly detection, SIEM integrations, and data classification. Enterprise Cloud bundles Guard Standard at no additional cost.

What this means in practice

Guard subscriptions are billed per managed user across your entire Atlassian organization, not per product:

Organization SizeGuard Standard CostGuard Premium Cost
100 users+$3,600-4,800/year+$9,600/year
250 users+$9,000-12,000/year+$24,000/year
500 users+$18,000-24,000/year+$48,000/year

This is in addition to your existing Jira, Confluence, and other product licenses, which can already run $100K+ annually for mid-sized teams.

Additional constraints

SCIM key expiration
API keys now expire after 1 year (as of January 2025), requiring annual rotation.
Billing complexity
Guard charges per managed user across all Atlassian products, regardless of which products they actually use.
Portal-only limitations
SCIM support for Jira Service Management portal-only accounts won't arrive until Q2 2025.
Group sync gaps
While SCIM works across most products, Bitbucket still has limited group synchronization support.

Summary of challenges

  • Atlassian 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

Atlassian doesn't sell SCIM standalone. It's bundled with Atlassian Guard, a separate security subscription on top of your existing product licenses:

Atlassian Guard Standard ($3-4/user/month)

SCIM 2.0 automated provisioning
SAML single sign-on (SSO)
API access controls
Security audit logs
Domain verification
Session management

Atlassian Guard Premium ($8/user/month)

Everything in Standard, plus:
Anomaly detection and alerts
SIEM integrations (Splunk, QRadar)
Data loss prevention (DLP)
Advanced threat detection
Data classification controls

The reality: Guard is billed per managed user across your entire Atlassian organization, not per product. So if you have 100 users across Jira, Confluence, and Bitbucket, you're paying Guard costs for all 100 users even if only 20 actively use SCIM provisioning.

For teams that just want automated user provisioning, roughly 60-70% of Guard's features are security theater you won't use. You're essentially paying double licensing costs (product + Guard) to get basic identity automation that should be standard in 2025.

What IT admins are saying

Community sentiment on Atlassian's SCIM pricing is mixed to negative, with most complaints centered on the additional Guard subscription cost. Common complaints:

  • Having to purchase Atlassian Guard on top of already-expensive product licenses
  • Guard billing complexity with per-managed-user pricing across the entire organization
  • Annual SCIM API key rotation requirement adding operational overhead
  • Confusing pricing structure with multiple Guard tiers and product dependencies

The Guard pricing model is frustrating - we're already paying premium prices for Jira and Confluence, now we need another subscription just for basic provisioning features.

Reddit r/sysadmin

SCIM keys expiring after a year is going to be a nightmare for our automation. One more thing to track and rotate annually.

Atlassian Community Forum

The recurring theme

IT teams feel nickeled-and-dimed by having to pay for a separate Guard subscription when SCIM should be included with their existing high-cost Atlassian product licenses.

The decision

Your SituationRecommendation
Don't have Guard subscription, need SCIMUse Stitchflow: avoid the $3-8/user/month Guard add-on
Have Guard Standard, comfortable with annual key rotationUse native SCIM: you're already paying for it
Need Guard Premium features beyond SCIMEvaluate Guard Premium: SCIM comes bundled with anomaly detection
Small team, low employee turnoverManual may work: but consider automation as you scale
Complex multi-product setup across Jira/Confluence/JSMUse Stitchflow: avoid Guard billing complexity and key management

The bottom line

Atlassian Guard adds $3-8 per user monthly on top of already-expensive product licenses, plus mandatory annual SCIM key rotation starting in 2025. For organizations wanting automated provisioning without the Guard subscription overhead, Stitchflow provides simpler, flat-rate automation.

Make Atlassian workflows AI-native

Atlassian gates SCIM behind Atlassian Guard subscription. We build complete offboarding, user access reviews, and license workflows without that SCIM Tax upgrade.

No Atlassian Guard subscription 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

  • Requires separate Atlassian Guard subscription in addition to product licenses
  • SCIM API keys now expire after 1 year (as of Jan 2025)
  • Portal-only accounts (JSM) SCIM support expected Q2 2025

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 → Atlassian → 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 via Atlassian Cloud app in OIN. Group sync available for Jira, Confluence, Trello (not Bitbucket). SCIM API keys expire after 1 year (as of Jan 2025).

Atlassian gates SCIM behind Atlassian Guard subscription. 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 → Atlassian → 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 2.0 provisioning support. Can sync job title, department attributes. Provisioning cycle runs every 40 minutes. Supports switching between SCIM and Azure AD nested groups.

Atlassian gates SCIM behind Atlassian Guard subscription. Stitchflow automates complete workflows without that SCIM Tax upgrade.

Unlock SCIM for
Atlassian

Atlassian gates SCIM behind Atlassian Guard subscription plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade.

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

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

Atlassian Jira logo

Atlassian Jira

SCIM Tax

Project Management / Issue Tracking

SCIM StatusIncluded
Manual Cost$11,946/yr

Atlassian Jira supports SCIM 2.0 for automated user provisioning, but only with an Atlassian Guard subscription—an additional $3-4/user/month on top of your base Jira plan. For a 100-person team on Standard ($9.05/user/month), adding Guard means a 33-44% cost increase just to unlock basic provisioning automation. Enterprise customers get Guard included, but that's $155/user/year with an 801-user minimum—$124,355 upfront commitment. The Guard subscription requirement creates a frustrating gap for growing teams. You're paying for Jira licenses but still manually managing user accounts, group assignments, and project access. SSO with JIT provisioning helps with login, but doesn't handle deprovisioning when employees leave or group sync for project permissions. For development teams where access delays impact sprint velocity, manual provisioning becomes a bottleneck.

View full guide
Atlassian Loom logo

Atlassian Loom

SCIM Tax

Video Messaging / Async Communication

SCIM StatusIncluded
Manual Cost$11,946/yr

Atlassian Loom supports SCIM 2.0 for automated user provisioning, but only on Enterprise plans with custom pricing. This creates a significant barrier for teams on Business plans ($15-20/user/month) who need automated provisioning but can't justify Enterprise-level costs. The limitation is particularly problematic because Loom's domain capture feature can automatically add users to Enterprise workspaces, creating provisioning gaps where some users get automatic access while others require manual management. For video messaging platforms handling sensitive content, this creates a compliance risk. Teams often deploy Loom organization-wide for async communication, but without automated deprovisioning on Business plans, former employees may retain access to recorded videos containing confidential information. SSO alone doesn't solve this - you need SCIM to ensure departing users lose access immediately when removed from your identity provider.

View full guide
Atlassian Opsgenie logo

Atlassian Opsgenie

SCIM Tax

Incident Management / On-Call

SCIM Tax+238%
Manual Cost$11,946/yr

Atlassian Opsgenie supports SCIM provisioning, but requires an additional Atlassian Guard subscription (~$4/user/month) on top of your existing Opsgenie plan. More critically, Opsgenie reaches end of life on April 5, 2027, with Atlassian migrating customers to Jira Service Management. This creates a challenging situation: invest in SCIM setup for a product being discontinued, or manage manual provisioning during the transition period. For incident management tools, automated provisioning isn't just about convenience—it's about reliability. On-call schedules depend on accurate team membership, and incident response is time-sensitive. Manual user management creates gaps where critical personnel might lack access during emergencies, or former employees retain unnecessary incident management privileges.

View full guide