Summary and recommendation
Qlik offers SCIM 2.0 support, but with significant barriers that limit its practical value. SCIM provisioning requires Enterprise plans (starting at $30,000+/year) and is primarily designed for Azure AD/Entra ID with P1+ licensing requirements. For Okta users, SCIM is only available through Talend Cloud integration, adding complexity. Other IdPs are left with basic JIT provisioning via SAML, which creates accounts on first login but doesn't handle ongoing lifecycle management.
This creates a problematic gap for IT teams managing Qlik access. JIT provisioning means you can't pre-provision users, can't automate role assignments, and can't ensure accounts are properly deactivated when employees leave. For organizations using Google Workspace, OneLogin, or other IdPs, there's no automated provisioning path at all—leaving admins to manually manage user accounts in a business-critical analytics platform.
The strategic alternative
Qlik 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 | ✓ | ✓ | 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 Qlik accounts manually. Here's what that costs:
The Qlik pricing problem
Qlik gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Starter | Fixed users, 25GB capacity | ||
| Standard/Premium | $30-$150/user/mo* | ||
| Enterprise | $30,000-$300,000+/year |
Plan Structure
| Plan | Price | SCIM |
|---|---|---|
| Starter | Fixed users, 25GB capacity | ❌ |
| Standard/Premium | $30-$150/user/mo* | ❌ |
| Enterprise | $30,000-$300,000+/year | ✓ |
*Pricing varies by role (Analyzer $30-$50, Professional $70-$150) and deployment model
What this means in practice
Enterprise pricing represents a dramatic jump from per-user tiers. For organizations currently on Standard/Premium plans:
Conservative estimate: Moving from $50/user/month Standard to $30,000 Enterprise minimum breaks even at just 50 users annually. However, most Enterprise deployments cost significantly more than the minimum.
Real-world impact: Organizations with 25-100 users face choosing between:
Additional constraints
Summary of challenges
- Qlik supports SCIM but only at Enterprise tier ($30,000-$300,000+/year depending on deployment)
- 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
Qlik doesn't sell SCIM à la carte. It's bundled with Enterprise tier features:
The challenge: SCIM requires Azure AD P1+ licensing on top of Qlik Enterprise costs. For Okta users, you're routing through Talend Cloud, adding another integration point. If you just want automated user provisioning, you're paying for enterprise-grade analytics infrastructure you may not need.
Stitchflow Insight
We estimate ~60% of Enterprise features are irrelevant for teams that primarily need reliable user provisioning across multiple IdPs without the Azure AD P1+ tax.
What IT admins are saying
Community sentiment on Qlik's SCIM implementation is mixed, with frustration centered on IdP limitations and licensing requirements. Common complaints:
- SCIM only works natively with Azure AD/Entra ID, leaving Okta users dependent on Talend Cloud
- Azure AD P1+ subscription requirement adds unexpected licensing costs
- Complex setup process with separate apps needed for SSO vs SCIM
- No nested group support limiting organizational flexibility
The Azure AD P1 requirement caught us off guard - we're paying extra just to sync users to Qlik.
Why does SCIM with Okta require going through Talend Cloud? Just give us direct integration like everyone else.
The recurring theme
Qlik's SCIM feels half-baked, forcing admins into specific IdP configurations or third-party workarounds instead of providing universal compatibility.
The decision
| Your Situation | Recommendation |
|---|---|
| On Starter/Standard, need SCIM | Use Stitchflow: avoid the $30K+ Enterprise tier jump |
| Have Azure AD P1+ and already on Enterprise | Use native SCIM: you're paying for both prerequisites |
| Using Okta/Google Workspace, need SCIM | Use Stitchflow: simpler than Talend Cloud routing |
| Large analytics deployment, need Enterprise features | Evaluate Enterprise: SCIM comes bundled with the tier |
| Small team, minimal user changes | Manual may work: but watch for offboarding gaps |
The bottom line
Qlik's SCIM requires both Enterprise pricing ($30K+ annually) and specific IdP tiers (Azure AD P1+), creating a double paywall for automation. For organizations wanting provisioning without the massive tier upgrade or IdP restrictions, Stitchflow delivers the same automation at a fraction of the cost.
Make Qlik workflows AI-native
Qlik 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 with Azure AD/Entra ID
- Okta SCIM available via Talend Cloud
- SAML not supported in Qlik Cloud Government
- Azure AD P1+ required for SCIM
- No nested group support
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).
SSO and provisioning via Okta catalog. Talend Cloud (Qlik) supports SCIM provisioning with Okta.
Qlik 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).
Full SCIM 2.0 support with Entra ID. Requires P1 subscription. Two apps recommended: one for SSO, one for SCIM.
Qlik gates SCIM behind Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.
Unlock SCIM for
Qlik
Qlik gates SCIM behind Enterprise plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade.
See how it works
