Freshservice SCIM guide

Salesforce supports SCIM 2.0 provisioning, but only on Enterprise ($175/user/month) and Unlimited ($350/user/month) editions. For organizations on Starter plans ($25/user/month), unlocking automated provisioning requires a 7x price increase—adding $150/user/month just to eliminate manual account management. For a 50-person team, that's $90,000/year in additional licensing costs solely to access SCIM capabilities. The pricing barrier creates a significant operational gap. Without automated provisioning, IT teams must manually create Salesforce accounts, assign profiles and permission sets, and remember to deactivate users when they leave—a process that's error-prone and doesn't scale. SSO alone doesn't solve this problem since it only handles authentication, not account lifecycle management. This manual overhead becomes particularly problematic in organizations with frequent role changes or seasonal hiring patterns.

Miro supports SCIM (the protocol that lets your identity provider automatically create, update, and remove user accounts). But SCIM is locked behind Miro's Enterprise plan, which requires custom pricing for 30+ members. Teams on Starter ($8/user/month) or Business ($16/user/month) can't access automated provisioning, even though Business includes SAML SSO. This creates a costly gap for mid-sized teams. A 50-person team on Business pays $9,600/year but can't automate user lifecycle management—they're forced into manual provisioning or an expensive Enterprise upgrade just to eliminate the security risk of orphaned accounts. Additionally, Miro's SCIM implementation can't create or delete teams, limiting automation to basic user operations.

Zendesk does not offer native SCIM provisioning on any plan, despite being a major enterprise customer support platform. While Professional ($115/agent/month) and Enterprise ($169/agent/month) plans support automated provisioning through Okta and Azure AD via API connectors, this creates vendor lock-in and leaves organizations using Google Workspace or OneLogin with no automated provisioning options. For support teams that experience high turnover and need rapid scaling during peak seasons, this forces IT into manual account management that creates onboarding delays and offboarding security gaps. The lack of universal SCIM support becomes particularly problematic during critical periods when customer service quality depends on rapid agent onboarding. Without standardized provisioning, IT teams can't implement consistent user lifecycle management across all applications, creating compliance risks and operational bottlenecks. When support agents leave or need role changes, the manual process increases the window of inappropriate access—a security concern for platforms handling customer data.