Cursor 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.

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.

Airbase supports SCIM provisioning, but only on Enterprise plans starting around $8,500/year. While SCIM works with all major identity providers (Okta, Entra ID, Google Workspace), the Enterprise requirement creates a significant barrier for smaller finance teams who need automated provisioning for spend management but can't justify enterprise-level spend management software costs. This creates a particular challenge in finance applications where rapid provisioning and deprovisioning is critical for corporate card access and financial controls. Manual user management means delayed access for new employees needing corporate cards, and more critically, potential security gaps when departing employees retain access to spend management systems. For finance teams handling sensitive financial data and corporate spending, these delays and oversights create both operational friction and compliance risks.