Oracle HCM SCIM guide

Workday supports SCIM, but with a crucial caveat: it's designed primarily as an HR source system that provisions to other applications, not as a destination for inbound provisioning. While Workday does support inbound SCIM for specific use cases like Strategic Sourcing, the integration requires Enterprise-level pricing ($100-200/employee/year, typically $100K-500K annually) and mandates SSO configuration—without SSO, SCIM requests return 403 Forbidden errors. This creates a complex identity architecture challenge. Most organizations use Workday as their authoritative HR system, meaning employee data flows from Workday to their IdP and other applications. When you need to provision users into Workday (for contractors, vendors, or non-employee access), you're working against the typical data flow, requiring expensive bidirectional sync capabilities and extensive integration work that can take months to implement properly.

8x8 supports SCIM 2.0 for automated user provisioning, but only on their quote-based X Series plans (previously $24-44/user/month range before they moved to custom pricing). While SCIM can create, update, and deactivate users, it has critical gaps that create ongoing manual overhead: license assignment must be done manually after every user is provisioned, users can't be deleted (only deactivated), and provisioned users don't automatically appear in the Company Directory. For IT teams managing a unified communications platform that typically covers all employees, these limitations defeat much of SCIM's purpose. You're still manually touching every user account to assign licenses and ensure directory visibility. The lack of user deletion support also creates compliance headaches when employees leave - accounts accumulate as "deactivated" rather than being properly removed.

Absorb LMS supports native SCIM provisioning, but only on Enterprise plans with SSO as a required paid add-on. Even with SCIM enabled, the implementation has critical limitations: SAML provisioning only creates accounts on first login and never updates existing users, and full user provisioning requires the specific "Absorb 5 - New Learner Experience" version. For organizations managing compliance training across hundreds or thousands of learners, these gaps create ongoing manual work. The SSO-as-add-on model means you're paying extra fees on top of already custom Enterprise pricing ($6-12/user/month base, but varies significantly). For learning management systems handling external partners, contractors, and employees across different access levels, the inability to update existing user attributes through SAML provisioning forces IT teams into manual account management—exactly what automated provisioning should eliminate.