Summary and recommendation
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.
The strategic alternative
Stitchflow provides managed provisioning automation for Opsgenie without the Guard subscription requirement, and can help transition your provisioning to Jira Service Management when you migrate. Flat pricing under $5K/year, regardless of team size, with support through the product transition.
Quick SCIM facts
| SCIM available? | Yes |
| SCIM tier required | Enterprise |
| SSO required first? | Yes |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| 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 Atlassian Opsgenie accounts manually. Here's what that costs:
The Atlassian Opsgenie pricing problem
Atlassian Opsgenie gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Free | $0 (up to 5 users) | ||
| Essentials | $9.45/user/mo | ||
| Standard | $19.95/user/mo | ||
| Enterprise | $31.90/user/mo |
Plan Structure (Billed Annually)
| Plan | Price | SCIM |
|---|---|---|
| Free | $0 (up to 5 users) | ❌ |
| Essentials | $9.45/user/mo | ❌ |
| Standard | $19.95/user/mo | ❌ |
| Enterprise | $31.90/user/mo | ✓ (with Guard) |
Required add-on: Atlassian Guard subscription (~$4/user/month) for SCIM access
What this means in practice
The real cost for SCIM includes both Enterprise upgrade and Guard subscription:
| Team Size | From Standard | From Essentials | Total Annual Cost |
|---|---|---|---|
| 25 users | +$4,308/year | +$8,136/year | $10,770/year |
| 50 users | +$8,616/year | +$16,272/year | $21,540/year |
| 100 users | +$17,232/year | +$32,544/year | $43,080/year |
Calculation: ((Enterprise + Guard) - Current plan) × users × 12 months
Additional constraints
Summary of challenges
- Atlassian Opsgenie supports SCIM but only at Enterprise tier ($31.90/user/month (annual) or $38.50/month (monthly))
- 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 Opsgenie requires two separate subscriptions for SCIM provisioning:
The combined package includes:
If you need enterprise incident management features, the dual subscription makes sense temporarily. However, you're paying premium pricing (~$35-40/user/month total) for a platform being discontinued. We estimate ~60% of Enterprise features are overkill for teams that just need reliable user provisioning for on-call schedules, especially given the looming migration deadline.
Stitchflow Insight
Opsgenie reaches end of life on April 5, 2027, with users migrating to Jira Service Management.
What IT admins are saying
Community sentiment on Atlassian Opsgenie's SCIM requirements is mixed, with growing concern about the product's future. Common complaints:
- Having to purchase separate Atlassian Guard subscription just for SCIM provisioning
- Multiple subscription costs stacking up (Opsgenie Enterprise + Guard adds ~$35.90/user/month)
- Complex Azure AD setup requiring separate apps for SSO vs SCIM
- Uncertainty about migrating to Jira Service Management before April 2027 end-of-life
We're already paying for Enterprise Opsgenie and now need Guard on top of that just to sync users? The costs keep adding up.
The Azure setup is unnecessarily complex - why do we need separate apps for SSO and provisioning?
The recurring theme
Teams are frustrated by the additional subscription requirements for basic SCIM functionality, compounded by the looming end-of-life transition that forces migration planning.
The decision
| Your Situation | Recommendation |
|---|---|
| On Essentials/Standard, need SCIM | Use Stitchflow: avoid the $31.90/user Enterprise upgrade plus Guard subscription |
| Already on Enterprise, don't have Guard | Use Stitchflow: skip the additional ~$4/user/month Guard subscription |
| Already paying for Enterprise + Guard | Use native SCIM: you're paying for it |
| Planning migration off Opsgenie before April 2027 | Use Stitchflow: avoid lock-in to a sunset product's pricing |
| Small on-call team, low turnover | Manual may work: but incident response teams can't afford access delays |
The bottom line
Opsgenie's SCIM requires both Enterprise tier ($31.90/user/month) and Atlassian Guard subscription (~$4/user/month additional), creating a costly barrier for incident management automation. With the product reaching end of life in April 2027, Stitchflow provides provisioning automation without the pricing lock-in or migration risk.
Automate Atlassian Opsgenie without the tier upgrade
Stitchflow delivers SCIM-level provisioning through resilient browser automation, backed by 24/7 human in the loop for Atlassian Opsgenie at <$5K/year, flat, regardless of team size.
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
- SSO requires Standard or Enterprise Opsgenie plan
- SCIM requires Atlassian Guard subscription
- Azure best practice: separate apps for SSO vs SCIM
- Product end of life April 5, 2027
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).
SCIM via Atlassian Guard. Push users and groups. Auto-provision on first login available.
Native SCIM is available on Enterprise. Use Stitchflow if you need provisioning without the tier 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).
SCIM via Atlassian Guard. Best practice: use separate apps for SSO and SCIM in Azure.
Native SCIM is available on Enterprise. Use Stitchflow if you need provisioning without the tier upgrade.
Unlock SCIM for
Atlassian Opsgenie
Atlassian Opsgenie gates automation behind Atlassian Guard subscription plan. Stitchflow delivers the same SCIM outcomes for a flat fee, saving you 238%.
See how it works