Summary and recommendation
Domo supports SCIM, but only through Okta integration and only for Enterprise customers paying $100,000-200,000+/year. Azure AD users get JIT provisioning only—no automated user lifecycle management or group-based access control. This creates a major gap for Microsoft-centric organizations that need automated provisioning for their business intelligence platform but don't want to switch identity providers or pay Enterprise pricing.
Without proper SCIM automation, IT teams face manual user management for a platform that typically serves analysts, executives, and data teams across multiple departments. Dashboard access by role and data source permissions become administrative bottlenecks. JIT provisioning doesn't handle deprovisioning, leaving orphaned accounts with access to sensitive business data—a significant compliance risk for BI platforms.
The strategic alternative
Domo 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 |
| Documentation | Official docs |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | ✓ | ✓ | OIN app with full provisioning |
| Microsoft Entra ID | ✓ | ❌ | SSO only |
| 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 Domo accounts manually. Here's what that costs:
The Domo pricing problem
Domo gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Standard | $50,000-75,000/year | ||
| Enterprise | $100,000-200,000+/year | ||
| Business Critical | $200,000-500,000+/year |
Plan Structure
| Plan | Price | SCIM |
|---|---|---|
| Standard | $50,000-75,000/year | ❌ |
| Enterprise | $100,000-200,000+/year | ✓ |
| Business Critical | $200,000-500,000+/year | ✓ |
Note: Domo moved to credit-based pricing in mid-2023. Prices vary significantly based on data volume, user count, and feature usage. Individual user licenses can reach $700/user/year on lower tiers.
What this means in practice
For organizations needing SCIM but currently on Standard plans:
| Current Spend | Enterprise Upgrade Cost | Annual Increase |
|---|---|---|
| $50,000 | $100,000 minimum | +100% |
| $75,000 | $100,000 minimum | +33% |
The jump from Standard to Enterprise often doubles the annual cost, making SCIM provisioning a $25,000-50,000+ premium for most organizations.
Additional constraints
Summary of challenges
- Domo supports SCIM but only at Enterprise tier ($100,000-200,000+/year)
- 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
Domo doesn't sell SCIM standalone. It's buried deep in their Enterprise tier alongside a massive bundle of features:
The kicker: Enterprise starts at $100K-200K annually, often requiring $20K-100K+ in implementation services. If you just need automated user provisioning, you're paying for an enterprise BI platform when you might only need basic analytics with proper identity management.
Stitchflow Insight
We estimate ~80% of Enterprise features are overkill for teams that simply want to automate user lifecycle management. The pricing forces you into a massive platform commitment when your primary need is provisioning automation.
What IT admins are saying
Community sentiment on Domo's SCIM limitations centers around IdP compatibility gaps and high pricing barriers. Common complaints:
The implementation complexity adds another layer of frustration, with services costs often reaching $20K-100K on top of platform licensing.
- Azure AD users stuck with JIT-only provisioning while Okta gets full SCIM
- Enterprise tier requirement creates a $100K+ entry point for basic identity automation
- Credit-based pricing model makes cost planning unpredictable
- Limited SCIM documentation outside of Okta-specific forums
"Azure AD SCIM not natively supported" remains a top community request, with many organizations having to choose between their preferred IdP and automated provisioning.
The recurring theme
Domo's SCIM works well if you're an Okta shop with Enterprise budget, but leaves Azure AD organizations paying premium prices for manual user management.
The decision
| Your Situation | Recommendation |
|---|---|
| Need SCIM, not on Enterprise tier | Use Stitchflow: avoid the $70K+ tier jump to Enterprise |
| Using Azure AD/Entra ID | Use Stitchflow: Domo only has JIT for Azure AD, no SCIM sync |
| Already on Enterprise with Okta | Use native SCIM: you're paying $100K+ already |
| Need Enterprise features beyond SCIM | Evaluate Enterprise: SCIM comes bundled with Okta |
| Small BI team, low user churn | Manual may work: but dashboard access by role gets complex fast |
The bottom line
Domo gates SCIM behind Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.
Make Domo workflows AI-native
Domo 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
- SCIM primarily via Okta (Azure AD SCIM community requested)
- Azure AD has JIT only (no full SCIM sync)
- SCIM Base URL: api.domo.com/scim/v2
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).
Domo by Aquera connector provides full SCIM provisioning. Supports user create, update, deactivate. Imports user entitlements into Okta. Configure in Admin Settings > Security > User Provisioning (SCIM). Group push supported for role-based access.
Domo gates SCIM behind Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.
Configuration for Entra ID
Integration type
Microsoft Entra Gallery app
Prerequisite
SSO must be configured before enabling SCIM.
Where to enable
Azure AD has JIT provisioning only, not full SCIM sync. SAML SSO with IdP and SP-initiated flows. Community has requested native Azure AD SCIM support.
Use Stitchflow for automated provisioning.
Unlock SCIM for
Domo
Domo gates SCIM behind Enterprise plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade, avoiding a 167% markup.
See how it works
