Summary and recommendation
Zendesk does not offer native SCIM provisioning on any plan, despite being a major enterprise customer support platform. While Professional ($115/agent/month) and Enterprise ($169/agent/month) plans support automated provisioning through Okta and Azure AD via API connectors, this creates vendor lock-in and leaves organizations using Google Workspace or OneLogin with no automated provisioning options. For support teams that experience high turnover and need rapid scaling during peak seasons, this forces IT into manual account management that creates onboarding delays and offboarding security gaps.
The lack of universal SCIM support becomes particularly problematic during critical periods when customer service quality depends on rapid agent onboarding. Without standardized provisioning, IT teams can't implement consistent user lifecycle management across all applications, creating compliance risks and operational bottlenecks. When support agents leave or need role changes, the manual process increases the window of inappropriate access—a security concern for platforms handling customer data.
The strategic alternative
Zendesk gates SCIM behind Enterprise. That can unlock provisioning, but it still does not complete the offboarding, access review, or license workflow across the rest of your stack. Stitchflow builds and maintains the IT workflows your team still runs manually, across every app, including the ones without APIs.
Quick SCIM facts
| SCIM available? | Yes |
| SCIM tier required | Enterprise |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Not available |
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 Zendesk accounts manually. Here's what that costs:
The Zendesk pricing problem
Zendesk gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Suite Team | $69/agent/month | ||
| Suite Growth | $89/agent/month | ||
| Suite Professional | $115/agent/month | ||
| Suite Enterprise | $169/agent/month |
Pricing structure
| Plan | Price | SCIM | Third-party provisioning |
|---|---|---|---|
| Suite Team | $69/agent/month | ❌ Not available | ❌ Not supported |
| Suite Growth | $89/agent/month | ❌ Not available | ❌ Not supported |
| Suite Professional | $115/agent/month | ❌ Not available | ✓ Via Okta/Entra API |
| Suite Enterprise | $169/agent/month | ❌ Not available | ✓ Via Okta/Entra API |
Note: Zendesk QA (a separate product) has native SCIM support, but the core Support product does not.
What this means in practice
Without native SCIM, IT teams managing Zendesk face several operational challenges:
Additional constraints
Summary of challenges
- Zendesk 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 Zendesk actually offers for identity
Zendesk doesn't offer native SCIM at all. Instead, they provide basic identity features that require third-party integrations or manual management:
SAML SSO (Professional tier and above)
Third-party provisioning (Okta/Entra only)
What's missing
The core problem: Zendesk forces you into either manual provisioning or vendor lock-in with specific identity providers. For customer support teams dealing with high agent turnover and seasonal scaling, this creates operational bottlenecks exactly when you need smooth provisioning most.
What IT admins are saying
Community sentiment on Zendesk's provisioning capabilities centers around frustration with the lack of native SCIM support in their flagship Support product:
- No native SCIM despite being a major enterprise customer service platform
- Forced reliance on third-party IdP integrations for any automated provisioning
- Confusing product fragmentation - Zendesk QA has SCIM but core Support doesn't
- Manual account management becomes a bottleneck during support team scaling
Does Zendesk support SCIM? No, Zendesk does not natively support SCIM provisioning.
It's frustrating that we have to use Okta's API connector instead of proper SCIM. Every other major SaaS app has native SCIM by now.
The recurring theme
For a platform built around customer service efficiency, Zendesk ironically creates service desk tickets for IT teams who must manually manage agent accounts during busy seasons and high turnover periods.
The decision
| Your Situation | Recommendation |
|---|---|
| Small support team (<20 agents), stable staffing | Manual management with SSO is workable on Professional tier |
| High agent turnover or seasonal scaling needs | Use Stitchflow: eliminates onboarding delays during peak periods |
| Using Google Workspace or OneLogin | Use Stitchflow: only option for automated provisioning |
| Multi-IdP environment or complex org structure | Use Stitchflow: works with any SAML provider, any Zendesk plan |
| Enterprise compliance requirements | Use Stitchflow: complete audit trail for agent lifecycle management |
The bottom line
Zendesk gates SCIM behind Enterprise. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the Zendesk workflow gap
Zendesk gates SCIM behind Enterprise, but the bigger issue is the workflow around it. Stitchflow builds and maintains the offboarding, access review, or license workflow underneath.
Technical specifications
SCIM Version
2.0
Supported Operations
Create, Update, Deactivate, Groups
Supported Attributes
Not specifiedPlan requirement
Enterprise
Prerequisites
None
Key limitations
- No native SCIM support in core Zendesk
- Must use third-party IdP integrations for provisioning
- Zendesk QA has separate SCIM - not main Support product
Documentation not available.
Configuration for Okta
Integration type
Okta Integration Network (OIN) app with SCIM provisioning
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).
Docs
Enterprise required for SCIM
Zendesk gates SCIM behind Enterprise. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Configuration for Entra ID
Integration type
Microsoft Entra Gallery app with SCIM provisioning
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).
Enterprise required for SCIM
Zendesk gates SCIM behind Enterprise. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the workflow gap in
Zendesk
Zendesk gates SCIM behind Enterprise plan. That can unlock provisioning, but it still does not complete the offboarding, access review, or license workflow across your stack.
Start with the free gap diagnostic


