Azure DevOps SCIM guide

15Five includes SCIM provisioning on all plans starting at $4/user/month, with full support for creating, updating, and deactivating users across Okta, Entra ID, Google Workspace, and OneLogin. However, 15Five's SCIM implementation has a critical prerequisite: SSO must be configured first, and their documentation explicitly warns against using JIT provisioning alongside SCIM due to duplicate user creation risks. This creates operational friction for IT teams managing performance management rollouts. The SSO-first requirement means you can't test SCIM provisioning in isolation, and the JIT conflict forces you to choose between automated onboarding convenience and reliable user lifecycle management. For HR-driven tools like 15Five that need to maintain accurate manager hierarchies and team structures, these provisioning gaps can disrupt performance review cycles and employee engagement tracking.

Dropbox Business supports SCIM 2.0 provisioning on Standard plans and above ($15/user/month), with solid integration across major identity providers including Okta, Azure AD, and Google Workspace. However, there's a critical architectural limitation: Dropbox Sign (formerly HelloSign) operates as a separate product that doesn't support SCIM at all, despite being a core part of many organizations' document workflows. This creates a significant provisioning gap for IT teams. While your main Dropbox storage accounts can be automatically managed, any users who need access to Dropbox Sign must be manually provisioned and deprovisioned. For organizations relying on both products, this means maintaining hybrid workflows where some users are automated and others require manual intervention—exactly the kind of inconsistency that leads to compliance issues and security gaps during employee transitions.

HiBob includes native SCIM support across all plans at no additional cost, with bidirectional sync capabilities for Okta, Entra ID, and other major identity providers. However, HiBob creates a unique challenge: as an HRIS platform, it's typically the authoritative source for employee data, meaning it pushes user information TO your IdP rather than receiving it. This reverses the normal provisioning flow and can create complex sync conflicts when managing users across multiple systems. The bidirectional sync complexity becomes particularly problematic when HiBob and your IdP disagree on employee status, department changes, or termination dates. IT teams often struggle with determining which system should be the ultimate source of truth for different attributes, leading to manual intervention and potential security gaps during employee transitions.