Stitchflow
Code42 logo

Code42 SCIM guide

Native SCIM

How to automate Code42 user provisioning, and what it actually costs

Native SCIM requires Enterprise plan

Summary and recommendation

Code42 (now Mimecast Incydr) supports native SCIM 2.0 provisioning, but only on Enterprise plans starting at ~$90/user/year. The implementation requires Identity Management to be enabled on your tenant and Customer Cloud Admin permissions for setup. While the SCIM integration itself is robust—supporting user lifecycle management, attribute sync, and group-based organization mapping through both Okta and Entra—the Enterprise tier requirement creates a significant cost barrier for mid-market organizations.

For a 100-person team, upgrading from lower tiers to Enterprise just to unlock automated provisioning could cost $108,000+ annually, often for advanced security features beyond basic user management needs. This forces IT teams into an uncomfortable choice: accept the manual overhead of provisioning data loss prevention tools (creating compliance gaps) or pay enterprise premiums primarily for automation capabilities.

The strategic alternative

Code42 gates SCIM behind Enterprise. Skip the Enterprise plan upgrade and automate complete outcomes across your stack. We maintain the integration layer underneath. You focus on judgment, not plumbing.

Quick SCIM facts

SCIM available?Yes
SCIM tier requiredEnterprise
SSO required first?No
SSO available?Yes
SSO protocolSAML 2.0
DocumentationNot available

Supported identity providers

IdPSSOSCIMNotes
OktaOIN app with full provisioning
Microsoft Entra IDGallery app with SCIM
Google WorkspaceJIT onlySAML SSO with just-in-time provisioning
OneLoginSupported

The cost of not automating

Without SCIM (or an alternative like Stitchflow), your IT team manages Code42 accounts manually. Here's what that costs:

Source: Stitchflow research, normalized to 500 employees:
Orphaned accounts (ex-employees with access)5
Unused licenses12
IT hours spent on manual management/year85 hours
Unused license cost/year$3,500
IT labor cost/year$5,100
Cost of compliance misses/year$890
Total annual financial impact$9,490

The Code42 pricing problem

Code42 gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.

Tier comparison

PlanPriceSSOSCIM
ProCustom
BusinessCustom
Enterprise~$90/user/year

Plan Structure

PlanPriceSCIM
ProCustom
BusinessCustom
Enterprise~$90/user/year

Note: Code42 uses custom pricing across all tiers, but Enterprise typically starts around $90 per user annually based on market data.

What this means in practice

The Enterprise upgrade represents a substantial investment for teams requiring automated provisioning:

Team SizeAnnual Enterprise CostMonthly Cost
50 users~$54,000/year~$4,500/mo
100 users~$108,000/year~$9,000/mo
200 users~$216,000/year~$18,000/mo

Organizations on Pro or Business plans face an all-or-nothing upgrade decision - there's no middle tier with basic SCIM capabilities.

Additional constraints

Identity Management prerequisite
SCIM requires Identity Management to be enabled on the Code42 tenant, adding configuration complexity.
Admin permissions required
Setup demands Customer Cloud Admin permissions, creating internal approval bottlenecks.
Dual Okta apps
Code42 maintains separate Okta integrations (Code42 cloud vs. Single Tenant), requiring careful selection during setup.
Post-acquisition uncertainty
With Mimecast's acquisition and rebranding to Incydr, long-term product roadmap and pricing stability remain unclear.

Summary of challenges

  • Code42 supports SCIM but only at Enterprise tier (Custom (~$90/user/year base))
  • Google Workspace users get JIT provisioning only, not full SCIM
  • Our research shows teams manually provisioning this app spend significant hidden costs annually

What the upgrade actually includes

Code42 (now Mimecast Incydr) doesn't sell SCIM separately. It's bundled with Enterprise-tier features that cost ~$90/user/year:

SCIM 2.0 automated provisioning
SAML single sign-on (SSO)
Identity Management controls
Advanced data loss prevention
Insider threat detection
Legal hold capabilities
Advanced reporting and analytics
Dedicated customer success management

The platform requires significant setup - you need Customer Cloud Admin permissions and Identity Management enabled on your tenant. Code42's acquisition by Mimecast has also created complexity with two separate Okta integrations (Code42 cloud and Single Tenant versions).

Stitchflow Insight

If you need comprehensive data protection and insider risk management, the Enterprise upgrade delivers value. If you just want automated user provisioning for basic endpoint backup, you're paying for enterprise security features you likely won't use. We estimate ~60% of Enterprise features are overkill for teams that only need SCIM provisioning.

What IT admins are saying

Community sentiment on Code42's SCIM implementation is mixed, with concerns about the enterprise-only requirement and post-acquisition uncertainty. Common complaints:

  • Being locked into expensive Enterprise plans just for SCIM provisioning
  • Confusion around the Mimecast acquisition and product transitions
  • Complex setup requirements needing Customer Cloud Admin permissions
  • Multiple Okta apps creating integration confusion (Code42 cloud vs Single Tenant)

The acquisition by Mimecast has created a lot of uncertainty about the future roadmap and pricing structure.

Reddit r/sysadmin

Why do we need Enterprise just for basic user provisioning? The ~$90/user/year jump is steep when you just want automated onboarding.

Spiceworks Community

The recurring theme

While Code42 offers solid SCIM support, the Enterprise tier requirement and post-acquisition uncertainty make it an expensive proposition for teams that just need reliable user provisioning.

The decision

Your SituationRecommendation
On Pro/Business plan, need SCIMUse Stitchflow: avoid the Enterprise upgrade and ~$90/user/year commitment
Already on Enterprise with Identity Management enabledUse native SCIM: you're paying for it and it's full SCIM 2.0
Small team, low employee churnManual provisioning may work: but watch for security gaps
Need Enterprise features beyond SCIMEvaluate Enterprise: SCIM comes bundled with the tier
Using legacy Code42 (pre-Mimecast acquisition)Plan migration strategy: product is now Mimecast Incydr

The bottom line

Code42's SCIM requires the Enterprise tier with Identity Management enabled, creating a significant cost barrier for smaller teams. For organizations that need provisioning automation without the Enterprise commitment, Stitchflow delivers the same user lifecycle management at a predictable flat rate.

Make Code42 workflows AI-native

Code42 gates SCIM behind Enterprise. We build complete offboarding, user access reviews, and license workflows without that SCIM Tax upgrade.

No Enterprise upgrade required
Less than a week, start to finish (~2 hours of your time)
We maintain the integration layer underneath
Book a Demo

Technical specifications

SCIM Version

2.0

Supported Operations

Create, Update, Deactivate, Groups

Supported Attributes

Not specified

Plan requirement

Enterprise

Prerequisites

None

Key limitations

  • Requires Identity Management to be enabled on Code42 tenant
  • Requires Customer Cloud Admin permission for setup
  • Code42 was acquired by Mimecast - product now called Mimecast Incydr
  • Two apps in Okta: Code42 (cloud) and Code42 Single Tenant

Documentation not available.

Configuration for Okta

Integration type

Okta Integration Network (OIN) app with SCIM provisioning

Where to enable

Okta Admin Console → Applications → Code42 → Provisioning

Required credentials

SCIM endpoint URL and bearer token (generated in app admin console).

Configuration steps

Enable Create Users, Update User Attributes, and Deactivate Users.

Provisioning trigger

Okta provisions based on app assignments (users or groups).

Code42 has full SCIM 2.0 support via Okta OIN. Supports user creation, updates, deactivation, and organization mapping based on SCIM groups.

Code42 gates SCIM behind Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.

Configuration for Entra ID

Integration type

Microsoft Entra Gallery app with SCIM provisioning

Where to enable

Entra admin center → Enterprise applications → Code42 → Provisioning

Required credentials

Tenant URL (SCIM endpoint) and Secret token (bearer token from app admin console).

Configuration steps

Set Provisioning Mode = Automatic, configure SCIM connection.

Provisioning trigger

Entra provisions based on user/group assignments to the enterprise app.

Sync behavior

Entra provisioning runs on a scheduled cycle (typically every 40 minutes).

Full SCIM provisioning with Entra. Supports user creation, deactivation, attribute sync, and group provisioning.

Code42 gates SCIM behind Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.

Unlock SCIM for
Code42

Code42 gates SCIM behind Enterprise plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade.

See how it works
Admin Console
Directory
Applications
Code42 logo
Code42
via Stitchflow

Last updated: 2026-01-20

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

Alteryx logo

Alteryx

SCIM Tax
SCIM StatusIncluded
Manual Cost$9,490/yr

Alteryx supports native SCIM 2.0 provisioning, but only on Enterprise plans with custom pricing (7+ users minimum). The feature requires SSO (SAML or OIDC) to be configured first and completely overrides manual user management. For teams on Professional ($5,000/user/year) or Business ($10,000-$20,000/user/year) plans, accessing SCIM means upgrading to Enterprise - often a significant cost increase for functionality that should be table stakes. This creates a provisioning gap for most Alteryx deployments. Without automated user lifecycle management, IT teams face manual onboarding/offboarding workflows, delayed access provisioning, and compliance risks around orphaned accounts. The high per-user costs make Alteryx particularly expensive to scale, and forcing an Enterprise upgrade just for basic provisioning automation compounds that challenge.

View full guide
Atlan logo

Atlan

SCIM Tax
SCIM StatusIncluded
Manual Cost$9,490/yr

Atlan supports native SCIM 2.0 provisioning with full user and group management capabilities. However, SCIM is only available on Enterprise tier, which requires custom pricing negotiations. Additionally, SSO must be enabled before SCIM can be configured, and Atlan's pricing tiers (Starter, Premier, Enterprise) are not publicly disclosed, making cost planning difficult for IT teams. This creates a significant barrier for organizations wanting automated provisioning without committing to enterprise-level contracts. For data teams evaluating Atlan, the lack of transparent pricing means you can't budget for provisioning capabilities upfront. The SSO prerequisite also forces organizations into a specific implementation sequence that may not align with their rollout timeline.

View full guide
Benchling logo

Benchling

SCIM Tax
SCIM StatusIncluded
Manual Cost$9,490/yr

Benchling supports SCIM provisioning, but only on Enterprise plans with custom pricing that typically starts at $1M+ annually. This creates a massive barrier: organizations on Professional plans ($20,000+/year) face a 50x+ price increase to unlock automated user provisioning. Even mid-sized life sciences teams end up paying enterprise-level licensing just to automate basic user lifecycle management. The pricing gap is so extreme that most organizations either stick with manual provisioning or delay Benchling adoption entirely. This creates a significant operational burden for IT teams managing researchers across multiple lab environments. Manual user provisioning in a platform that handles sensitive R&D data introduces compliance risks and delays researcher onboarding. When a scientist joins or leaves, IT must manually coordinate access across Benchling's complex permission structure for notebooks, entities, and workflows. For organizations with frequent collaborator access or seasonal research teams, this becomes unmanageable.

View full guide