SCIM paywalled apps

1Password supports SCIM provisioning on its Business plan ($7.99/user/month), but requires deploying and managing the 1Password SCIM Bridge on your own infrastructure. This self-hosted approach means you're responsible for maintaining servers, handling updates, and troubleshooting connectivity issues between your identity provider and 1Password's systems. The SCIM Bridge also operates separately from SSO (which uses OIDC only), requiring you to configure and maintain two distinct integrations. This architecture creates operational overhead that many IT teams don't want to manage. Unlike cloud-native SCIM implementations, you're essentially running 1Password's provisioning infrastructure for them. When the SCIM Bridge goes down, provisioning stops working. When 1Password updates their API, you need to update your Bridge deployment. For teams that just want automated user lifecycle management, this becomes an ongoing maintenance burden.

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.

Adobe Creative Cloud supports SCIM provisioning, but only on Enterprise plans with custom pricing—and only if you use Azure AD or Google Workspace as your identity provider. This creates a massive blind spot: organizations using Okta, OneLogin, or other IdPs are completely locked out of automated provisioning, despite Adobe being in Okta's integration network for SSO. Even when SCIM works, it only handles user creation and removal—license assignment and management still requires manual intervention. This IdP restriction is particularly problematic for enterprises that have standardized on Okta or other providers. You're forced to choose between maintaining your existing identity infrastructure or accepting manual user management for one of your most expensive SaaS applications. The limitation becomes even more painful when you consider that Teams plans ($89.99/user/month) don't support SCIM at all, pushing you into custom Enterprise pricing territory just to automate basic user lifecycle management.

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.

Airbyte supports SCIM provisioning, but only on Enterprise plans with custom pricing. While their Cloud plan starts at $10/month plus usage credits, SCIM access requires jumping to Enterprise—a significant cost leap that puts automated provisioning out of reach for most data teams. This creates a problematic gap where data engineers get SSO access through OIDC, but IT teams must manually provision and deprovision accounts in a platform that handles sensitive data source connections. The stakes are particularly high with data integration platforms. Data engineers need timely access to build and maintain pipelines, but manual provisioning delays create bottlenecks. More critically, when engineers leave or change roles, manual deprovisioning risks leaving active accounts with access to production databases, APIs, and other sensitive data sources—a compliance and security nightmare.

Airfocus supports SCIM provisioning, but only on Enterprise plans with custom pricing. While it handles basic user lifecycle management (create, update, deactivate), it lacks group provisioning entirely—meaning team assignments and workspace access must be managed manually. The Azure Entra integration also suffers from significant delays (~40 minutes for provisioning), creating gaps where users can't access product roadmaps they need immediately. For product management teams, this creates operational friction. Product managers, executives, and engineering leads need timely access to strategic roadmaps, but manual group assignments slow onboarding and complicate offboarding. Without automated group provisioning, IT teams must coordinate with product leads to ensure the right stakeholders have appropriate workspace access—exactly the kind of manual work SCIM should eliminate.

Airtable supports native SCIM provisioning, but with significant limitations that create operational friction for IT teams. User provisioning requires Business ($45/user/month annually) or higher, while group provisioning is locked behind Enterprise (custom pricing, typically $75+/user/month). More problematic: user disable/reactivate functionality only works with Okta, leaving teams using Entra ID or Google Workspace unable to automatically deactivate accounts when employees leave. Additionally, SSO is a prerequisite for SCIM, meaning you can't set initial passwords through provisioning—users must authenticate through your IdP first. These limitations create security gaps in your offboarding process. When employees leave, IT teams using non-Okta IdPs must manually disable Airtable accounts or risk data exposure. For organizations with sensitive data in Airtable bases, this manual step represents a compliance risk, especially given Airtable's role in storing customer data, project timelines, and operational workflows.

Amplitude supports SCIM provisioning, but only on Growth plans (starting around $36K/year) or Enterprise plans with custom pricing. While Amplitude's SCIM implementation covers the core functionality—creating, updating, and deactivating users—it requires SCIM to be specifically enabled for your organization, and regenerating the SCIM key immediately invalidates existing integrations without warning. For product teams on Plus plans ($49/month), upgrading to Growth just to unlock SCIM means jumping from under $600/year to $36,000+/year—a 60x increase. That's often more than the entire analytics budget for smaller product teams. The gap becomes particularly problematic for cross-functional product teams where analysts, PMs, and engineers need varying levels of access to user behavior data, but manual provisioning creates security risks around sensitive analytics permissions.

Anaplan supports SCIM 2.0 for user provisioning, but only on Enterprise plans with custom pricing that typically ranges from $50K-$250K for implementation plus ongoing licensing. SCIM provisions users at the Workspace level and requires coordination with Anaplan support for setup. Critically, users must be created and activated in Anaplan before SSO will work—there's no just-in-time provisioning support. This creates a coordination problem for IT teams managing finance and planning users. Without JIT provisioning, you need to manually pre-create accounts or ensure your SCIM sync runs before users attempt their first login. For planning teams working with sensitive financial data, this gap means potential access delays during budget cycles or model updates, exactly when analysts need immediate access to planning workspaces.

Apollo.io supports native SCIM provisioning, but only on their Organization plan at $119/user/month (annual). This creates a significant barrier: teams on Basic ($49/user/month) or Professional ($79/user/month) face a 50-51% price increase just to unlock automated user provisioning. For a 20-person sales team, upgrading from Professional to Organization costs an extra $9,600/year. Additionally, SCIM is only officially tested with Okta and Microsoft Entra ID, limiting options for teams using other identity providers. This pricing gate is particularly problematic for sales organizations where Apollo.io is most valuable. Sales teams experience high turnover, and prospect data requires immediate access control—new SDRs need Apollo access on day one, and departing reps must lose access immediately to protect valuable contact databases. Manual user management creates security gaps and slows onboarding in fast-moving sales environments.

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.

Ashby supports SCIM 2.0 for automated user provisioning, but only on its Growth and Enterprise tiers. While Ashby's newer pricing structure starts at $400/month for Foundations (up to 100 employees), SCIM requires upgrading to Growth or Enterprise with custom pricing. For most organizations, this means annual contracts starting around $6K-$15K, plus additional costs for elevated seats ($800/year each) and dedicated recruiter licenses ($350-750/month). This creates a significant access control gap for recruiting teams. Without automated provisioning, IT admins must manually manage access to sensitive candidate data and personally identifiable information (PII). Hiring managers who need temporary access to specific job openings often get over-provisioned permissions, while departing employees may retain access to confidential recruiting data longer than necessary.

Atlassian supports SCIM (the protocol that lets your identity provider automatically create, update, and remove user accounts), but requires a separate Atlassian Guard subscription on top of your existing product licenses. Guard Standard costs $3-4/user/month additional, meaning a 100-person organization pays $3,600-4,800/year extra just for provisioning capabilities. The hidden complexity: Guard billing is per "managed user" across your entire Atlassian organization, not per active product license. Recent changes make this even more operationally burdensome. As of January 2025, SCIM API keys now expire after one year, requiring mandatory annual rotation. Plus, portal-only accounts (common in Jira Service Management for external users) won't support SCIM until Q2 2025, leaving a provisioning gap for customer support workflows.

Atlassian Bitbucket supports SCIM 2.0 for user provisioning, but requires an additional Atlassian Guard subscription on top of your existing Bitbucket plan. More critically, Bitbucket's SCIM implementation only provisions users—group sync is completely unavailable. This means while your IdP can create and deactivate user accounts, all repository permissions and team memberships must be managed manually within Bitbucket itself. For development teams handling sensitive source code, this creates a significant security and operational gap. Repository access controls are critical for IP protection, but without group sync, IT admins must rely on developers to manually assign the correct permissions in Bitbucket after SCIM provisions the accounts. This manual step defeats the purpose of automated provisioning and creates compliance risks when developers leave or change roles.

Atlassian Confluence supports SCIM 2.0 provisioning, but requires an Atlassian Guard subscription ($4/user/month) unless you're on Enterprise. For teams on Standard ($5.25-6.00/user/month) or Premium ($11.75/user/month), adding Guard increases your total cost by 67-76%. Plus, you'll deal with annual API key expiration management and Google Cloud IdP users losing group sync functionality entirely. This creates a significant cost barrier for mid-sized teams who need automated user provisioning but don't want Enterprise-level features. A 200-person team on Standard would pay an extra $9,600/year just to unlock SCIM capabilities they should reasonably expect from a modern SaaS platform.

Atlassian Jira supports SCIM 2.0 for automated user provisioning, but only with an Atlassian Guard subscription—an additional $3-4/user/month on top of your base Jira plan. For a 100-person team on Standard ($9.05/user/month), adding Guard means a 33-44% cost increase just to unlock basic provisioning automation. Enterprise customers get Guard included, but that's $155/user/year with an 801-user minimum—$124,355 upfront commitment. The Guard subscription requirement creates a frustrating gap for growing teams. You're paying for Jira licenses but still manually managing user accounts, group assignments, and project access. SSO with JIT provisioning helps with login, but doesn't handle deprovisioning when employees leave or group sync for project permissions. For development teams where access delays impact sprint velocity, manual provisioning becomes a bottleneck.

Atlassian Loom supports SCIM 2.0 for automated user provisioning, but only on Enterprise plans with custom pricing. This creates a significant barrier for teams on Business plans ($15-20/user/month) who need automated provisioning but can't justify Enterprise-level costs. The limitation is particularly problematic because Loom's domain capture feature can automatically add users to Enterprise workspaces, creating provisioning gaps where some users get automatic access while others require manual management. For video messaging platforms handling sensitive content, this creates a compliance risk. Teams often deploy Loom organization-wide for async communication, but without automated deprovisioning on Business plans, former employees may retain access to recorded videos containing confidential information. SSO alone doesn't solve this - you need SCIM to ensure departing users lose access immediately when removed from your identity provider.

Atlassian Opsgenie supports SCIM provisioning, but requires an additional Atlassian Guard subscription (~$4/user/month) on top of your existing Opsgenie plan. More critically, Opsgenie reaches end of life on April 5, 2027, with Atlassian migrating customers to Jira Service Management. This creates a challenging situation: invest in SCIM setup for a product being discontinued, or manage manual provisioning during the transition period. For incident management tools, automated provisioning isn't just about convenience—it's about reliability. On-call schedules depend on accurate team membership, and incident response is time-sensitive. Manual user management creates gaps where critical personnel might lack access during emergencies, or former employees retain unnecessary incident management privileges.

Atlassian Statuspage supports SCIM 2.0 provisioning, but requires an Atlassian Guard subscription ($3-4/user/month) on top of your existing plan. While Statuspage itself starts at $29/month, SCIM access means paying Guard licensing for every user who needs status page access. The bigger limitation: group sync isn't available for Statuspage, forcing manual role assignments even with automated provisioning. For incident response teams, this creates operational friction during the worst possible moments. Status page updates are often urgent during outages, requiring multiple team members to have posting access. Without group-based provisioning, IT teams must manually assign permissions to SREs, DevOps engineers, and communications staff. When incidents strike and new team members need emergency access, the manual process becomes a bottleneck.

Atlassian Trello supports SCIM provisioning through Atlassian's centralized SCIM API, but only for Enterprise customers ($17.50+/user/month with 50-seat minimum) who also purchase Atlassian Guard. The critical limitation: group sync is not available for Trello. While SCIM can create and deactivate users, it cannot assign them to specific Trello boards or workspaces based on group membership. This means IT teams must manually manage board access for every user, defeating much of the automation benefit. For organizations where Trello has broad adoption across teams, this creates a significant operational burden. Users get provisioned to the Atlassian organization but don't automatically receive Trello licenses or appropriate board access. IT teams end up managing two separate processes: automated user creation through SCIM, and manual board permission assignment through Trello's interface. The 50-user minimum also forces smaller teams into expensive Enterprise licensing they may not otherwise need.

Autodesk supports SCIM 2.0 for automated user provisioning, but only with a Business Success Plan subscription—an additional cost on top of already expensive product licenses (AutoCAD at $1,975/year, Revit at $3,005/year). The SCIM implementation has significant limitations: nested groups are flattened to individual users, Azure AD sync intervals are fixed at 40 minutes, and SSO is enforced domain-wide once enabled, forcing all users in your domain to use SSO. For AEC firms with project-based workflows, these limitations create operational friction. Contractors and temporary team members need quick access to design tools, but the 40-minute sync delay and mandatory domain-wide SSO create bottlenecks. The additional Success Plan cost compounds an already expensive licensing model, especially when managing multiple Autodesk products across different project teams.

Basecamp offers automated user provisioning only through Okta's connector, which uses a proprietary API rather than the standard SCIM 2.0 protocol. This integration is available with Basecamp's Business plan ($299/month flat rate for unlimited users), but creates significant limitations for IT teams: you're locked into Okta as your identity provider, with no native SCIM support for Entra ID, Google Workspace, or other platforms. While Basecamp does support SAML SSO across multiple IdPs, SSO alone only handles authentication—users must still be manually created and managed in Basecamp. This creates a problematic gap for organizations using non-Okta identity providers or those requiring standardized SCIM implementations. IT teams end up managing Basecamp users manually or through custom scripts, increasing operational overhead and compliance risk. The lack of true SCIM 2.0 support means you can't leverage your existing provisioning workflows or easily switch identity providers without losing automation capabilities.

Better Uptime supports full SCIM 2.0 provisioning with user lifecycle management and group sync—but only on Enterprise plans that typically cost $3,100-$12,000/year. Teams on Starter ($29/month) or Pro (custom pricing) plans can't automate provisioning at all, creating manual overhead for DevOps teams that need frequent access changes for on-call rotations and incident response. The real problem isn't just manual user management. For uptime monitoring tools, proper provisioning directly impacts incident response capabilities. When team members leave or change roles, they need immediate removal from on-call schedules and alert routing. Manual processes create dangerous gaps where alerts go to inactive users during critical outages. Better Uptime's Enterprise requirement forces teams to choose between operational security and budget constraints.