Summary and recommendation
Index Exchange supports SCIM 2.0, but only through Okta's identity provider and only on custom Enterprise plans with revenue-share pricing. The platform uses OIDC for SSO (not SAML) and has no native Microsoft Entra integration, creating significant gaps for organizations using multi-vendor identity stacks or standardized on Microsoft.
For advertising teams managing multiple vendor relationships, this Okta-only approach creates a provisioning bottleneck. IT teams running Entra or other identity providers face manual account management, while the custom pricing model makes budget planning difficult. Without automated deprovisioning across all identity providers, departing employees may retain access to advertising platforms handling sensitive campaign data and budgets.
The strategic alternative
Index Exchange gates SCIM behind Custom. 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 | Custom |
| 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 | ✓ | ❌ | 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 Index Exchange accounts manually. Here's what that costs:
The Index Exchange pricing problem
Index Exchange gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Standard | Custom (revenue share) | ||
| Enterprise | Custom (revenue share) |
Plan Structure
| Plan | Price | SCIM |
|---|---|---|
| Standard | Custom (revenue share) | ❌ |
| Enterprise | Custom (revenue share) | ✓ |
Note: Index Exchange operates on revenue-share pricing models with custom contract terms. SCIM provisioning requires enterprise-level agreements.
What this means in practice
Index Exchange's provisioning challenges center on platform and integration limitations rather than transparent pricing tiers:
Additional constraints
Summary of challenges
- Index Exchange supports SCIM but only at Custom tier (Custom (revenue share))
- 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
Index Exchange doesn't sell SCIM as a standalone service. It's bundled with their Enterprise advertising platform:
The challenge: Index Exchange operates on custom revenue share models, meaning SCIM access requires committing to their entire advertising platform. If you're not actively running programmatic advertising campaigns that justify revenue sharing, you're essentially paying platform fees just for user provisioning.
Stitchflow Insight
Additionally, their SCIM implementation is Okta-exclusive with no Microsoft Entra support, limiting your identity provider options. We estimate ~90% of Enterprise features are irrelevant for IT teams that simply need automated user lifecycle management.
What IT admins are saying
Community sentiment on Index Exchange's SCIM implementation reveals frustration with platform limitations and integration gaps. Common complaints:
- OIDC-only SSO creates compatibility issues with SAML-first environments
- Heavy reliance on Okta excludes organizations using other IdPs
- No native Microsoft Entra support despite widespread enterprise adoption
- Custom pricing model makes cost planning difficult for procurement teams
We're standardized on Entra and SAML across our ad tech stack. Index Exchange being OIDC-only with no Entra gallery app means we can't automate provisioning like we do with other platforms.
The Okta dependency is problematic. We use Google Workspace as our primary IdP and having to maintain a separate Okta instance just for Index Exchange provisioning doesn't make financial sense.
The recurring theme
Index Exchange's narrow integration focus forces organizations to either accept manual provisioning or maintain additional identity infrastructure they wouldn't otherwise need.
The decision
| Your Situation | Recommendation |
|---|---|
| Need SCIM but not on Enterprise tier | Use Stitchflow: avoid custom revenue share negotiations |
| Using Entra ID or Google Workspace | Use Stitchflow: no native support outside Okta |
| On Enterprise but SCIM setup is complex | Use Stitchflow: we handle the technical implementation |
| Already on Enterprise with working SCIM | Keep native SCIM: you're paying for it |
| Small ad ops team, minimal user changes | Manual may work: but prepare for operational overhead |
The bottom line
Index Exchange gates SCIM behind Custom. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the Index Exchange workflow gap
Index Exchange gates SCIM behind Custom, 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
Custom
Prerequisites
None
Key limitations
- SSO via OIDC (not SAML)
- Provisioning primarily through Okta
- No native Entra support
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
Supports Create, Update, Deactivate, Attribute Sourcing via OIDC
Index Exchange gates SCIM behind Custom. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the workflow gap in
Index Exchange
Index Exchange gates SCIM behind Custom 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
