Summary and recommendation
SAP Sales Cloud supports SCIM 2.0 through SAP Identity Provisioning Service, but only on Enterprise plans starting at $134/user/month. The bigger problem: SCIM is disabled by default and requires creating a support ticket in the CEC-CRM component to enable the feature flag. Once enabled, manual user creation is completely disabled, forcing you into full automation dependency. Only Employee-type users can be provisioned, limiting flexibility for different user roles.
For organizations on Starter ($57/user/month) or Pro plans, upgrading to Enterprise just for SCIM means a 135% price increase. For a 50-person sales team, that's an additional $46,200/year in licensing costs. The support ticket requirement adds operational friction that delays user access and creates dependency on SAP's support response times.
The strategic alternative
SAP Sales Cloud 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? | 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 SAP Sales Cloud accounts manually. Here's what that costs:
The SAP Sales Cloud pricing problem
SAP Sales Cloud gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Plan Structure
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Starter | $57/user/mo (reported) | ||
| Pro | Custom pricing | ||
| Enterprise | $134/user/mo (starting) |
Note: SCIM requires SAP Identity Provisioning Service integration and is disabled by default even on Enterprise plans.
What this means in practice
Using reported pricing (Starter → Enterprise for SCIM access):
| Team Size | Annual Upgrade Cost | Monthly Increase |
|---|---|---|
| 25 users | +$23,100/year | +$1,925/month |
| 50 users | +$46,200/year | +$3,850/month |
| 100 users | +$92,400/year | +$7,700/month |
Calculation: ($134 - $57) × users × 12 months
Additional constraints
Summary of challenges
- SAP Sales Cloud supports SCIM but only at Enterprise tier ($134/user/mo (starting))
- 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
SAP Sales Cloud doesn't sell SCIM à la carte. It's bundled with Enterprise-tier features and requires manual enablement:
The SCIM feature flag must be manually enabled by SAP support through a CEC-CRM ticket, adding deployment friction even after paying Enterprise prices. Once enabled, manual user creation is disabled entirely—you're locked into SCIM-only provisioning.
Stitchflow Insight
If you need enterprise CRM capabilities anyway, the upgrade delivers value. If you just want automated user provisioning for your sales team, you're paying Enterprise premiums ($134+/user/month) for a feature that's disabled by default. We estimate ~80% of Enterprise features are irrelevant for teams that only need reliable user provisioning.
What IT admins are saying
Community sentiment on SAP Sales Cloud's SCIM implementation is mixed, with frustration centered on the complexity of enablement rather than the feature itself.
- SCIM being disabled by default despite being available
- Having to create support tickets just to enable basic provisioning
- Lack of clear documentation on the enablement process
- Premium enterprise pricing barriers for smaller organizations
SCIM is there but you have to create a ticket in CEC-CRM component to get the feature flag turned on. Not exactly self-service.
The fact that manual user creation gets disabled when you enable SCIM caught us off guard during implementation.
The recurring theme
SAP has the technical capability but wraps it in unnecessary operational friction, requiring support tickets and enterprise pricing for what should be standard identity automation.
The decision
| Your Situation | Recommendation |
|---|---|
| On Starter/Pro, need SCIM | Use Stitchflow: avoid the $77+/user/mo Enterprise jump |
| Already on Enterprise, SCIM disabled | Enable native SCIM: create support ticket with SAP |
| Need SCIM but not Enterprise CRM features | Use Stitchflow: start with a free gap diagnostic, then build the workflow across every app without asking your team to own the plumbing. |
| Large sales org, already planning Enterprise | Enable native SCIM: you're paying premium pricing anyway |
| Small sales team, infrequent changes | Manual may work: but watch for access creep as you scale |
The bottom line
SAP Sales Cloud gates SCIM behind Enterprise. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the SAP Sales Cloud workflow gap
SAP Sales Cloud 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
SSO must be configured first
Key limitations
- SCIM disabled by default (feature flag)
- Create support ticket to enable
- Manual user creation disabled when SCIM enabled
- Only Employee type users provisioned
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).
Enterprise required for SCIM
SAP Sales Cloud 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
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).
Enterprise required for SCIM
SAP Sales Cloud 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
SAP Sales Cloud
SAP Sales Cloud 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, and it can add a 135% markup just to get there.
Start with the free gap diagnostic
