GitHub SCIM guide

GitHub Copilot supports SCIM provisioning, but only through Enterprise Managed Users (EMU) on the Enterprise plan ($39/user/month). This creates a significant barrier: your entire GitHub Enterprise organization must be configured as EMU from inception, which fundamentally changes how users interact with the broader GitHub ecosystem. EMU users can't collaborate on repositories outside their managed enterprise, access GitHub.com content normally, or maintain their existing GitHub identities. For most organizations, this EMU requirement creates an impossible choice. You either sacrifice the collaborative benefits of the GitHub ecosystem to get automated Copilot provisioning, or you manually manage AI coding tool access for your engineering teams. Given that Copilot access is directly tied to code security and productivity, manual provisioning creates both operational overhead and security gaps when developers leave or change roles.

Asana supports SCIM 2.0 provisioning, but only on Enterprise plans ($35/user/month). This creates a significant cost barrier for teams on Starter ($10.99/user/month) or Advanced ($24.99/user/month) plans who need automated user provisioning. For a 50-person team moving from Advanced to Enterprise just for SCIM, that's an additional $60,000 annually—often for enterprise features they don't need. The pricing gap is particularly problematic because Asana's Advanced plan already includes premium project management features that most teams require. Without SCIM, IT teams must manually provision users or rely on just-in-time (JIT) provisioning via SAML, which doesn't provide the same level of control over user lifecycle management and group assignments that full SCIM automation delivers.

Box offers automated user provisioning through IdP integrations with Okta and Microsoft Entra ID, but this is not SCIM-compliant provisioning. Instead, Box uses a proprietary API that violates core SCIM standards—the userName attribute isn't required, error codes are non-standard, and attribute mapping is Box-specific. This creates a misleading situation where Box appears to support modern provisioning but actually locks you into IdP-specific integrations. Provisioning requires Business plans ($15/user/month) or higher, and only works with major IdP vendors. This proprietary approach creates significant challenges for IT teams managing multi-vendor environments or planning IdP migrations. Since Box's provisioning relies on custom integrations rather than standardized SCIM, switching identity providers means rebuilding provisioning workflows from scratch. Organizations using less common IdPs, those requiring SCIM compliance for audit purposes, or teams running mixed identity environments are left with manual user management—creating security gaps and administrative overhead that scales poorly as teams grow.