Stitchflow
Microsoft Dynamics 365 logo

Microsoft Dynamics 365 SCIM guide

Native SCIM

How to automate Microsoft Dynamics 365 user provisioning, and what it actually costs

Native SCIM requires Included plan

Summary and recommendation

Microsoft Dynamics 365 takes a different approach to provisioning than most SaaS applications—it doesn't support SCIM at all. Instead, Microsoft integrates D365 directly into the broader Microsoft 365 ecosystem, meaning user provisioning happens through Azure AD/Entra ID's native identity management. This works seamlessly if you're running a full Microsoft stack, but creates significant friction for organizations using third-party identity providers like Okta, OneLogin, or Google Workspace. These non-Microsoft IdPs require complex federation setups and custom domain configurations, often losing the automated provisioning capabilities that IT teams expect from modern SaaS applications.

The gap becomes particularly problematic for mixed-IdP environments or organizations trying to consolidate identity management outside the Microsoft ecosystem. While D365 supports SAML SSO from third-party providers, this only handles authentication—not the automated user lifecycle management that prevents security gaps and reduces manual IT overhead. Given D365's complex licensing model (ranging from $8/month for Team Members to $180/month for premium modules), manual user management becomes both expensive and error-prone at scale.

The strategic alternative

Microsoft Dynamics 365 gates SCIM behind Included. Skip the Included 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?Yes
SSO available?Yes
SSO protocolSAML 2.0, WS-Federation, OIDC
DocumentationOfficial docs

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 Microsoft Dynamics 365 accounts manually. Here's what that costs:

Source: Stitchflow aggregate data across apps with 2+ instances, normalized to 500 employees
Orphaned accounts (ex-employees with access)7
Unused licenses12
IT hours spent on manual management/year101 hours
Unused license cost/year$3,925
IT labor cost/year$6,088
Cost of compliance misses/year$1,741
Total annual financial impact$11,754

The Microsoft Dynamics 365 pricing problem

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

Tier comparison

PlanPriceSSOSCIM
Team Member$8/user/month
Business Central Essentials$80/user/month
Business Central Premium$110/user/month
Sales Professional$65/user/month
Sales Enterprise$95/user/month
Project Operations$135/user/month

Pricing and provisioning options

PlanPriceSCIMNotes
Team Member$8/user/month❌ Microsoft ecosystem onlyLimited access
Business Central Essentials$80/user/month❌ Microsoft ecosystem onlyERP functionality
Business Central Premium$110/user/month❌ Microsoft ecosystem onlyFull ERP + analytics
Sales Professional$65/user/month❌ Microsoft ecosystem onlyBasic CRM
Sales Enterprise$95/user/month❌ Microsoft ecosystem onlyAdvanced CRM
Project Operations$135/user/month❌ Microsoft ecosystem onlyProject management

Pricing increases to $80/$110 for Business Central plans in November 2025

What this means in practice

For Microsoft shops: User provisioning works natively through Azure AD/Entra ID with full attribute mapping, group sync, and automated lifecycle management. This is the ideal scenario.

For non-Microsoft IdPs: You're forced into a federation setup where:

Okta, Google Workspace, or OneLogin must authenticate through Microsoft's identity layer
User creation still happens in the Microsoft ecosystem, not your primary IdP
Attribute mapping becomes a two-hop process (your IdP → Azure AD → Dynamics 365)
Group memberships and role assignments require Microsoft-side configuration

Additional constraints

Identity dependency
Even with third-party IdPs, user provisioning ultimately flows through Microsoft's identity infrastructure
Complex licensing model
Different Dynamics 365 modules have separate pricing, making user lifecycle management across applications complicated
Federation requirements
Non-Azure IdPs need custom domain setup and federation configuration before any provisioning works
Limited control
IT admins can't directly manage Dynamics 365 users through their primary identity provider—everything goes through Microsoft's layer

Summary of challenges

  • Microsoft Dynamics 365 supports SCIM but only at Enterprise tier (custom pricing)
  • Google Workspace users get JIT provisioning only, not full SCIM
  • Our research shows teams manually provisioning this app spend significant hidden costs annually

What Microsoft Dynamics 365 actually offers for identity

Native Azure AD/Entra Integration

For organizations in the Microsoft ecosystem, Dynamics 365 provides seamless identity management:

FeatureDetails
ProtocolSAML 2.0, WS-Federation, OIDC
User provisioningFull SCIM via Azure AD/Entra
Group sync✓ Yes
JIT provisioning✓ Yes
Deprovisioning✓ Yes
CostIncluded with Microsoft 365 licensing

The Microsoft advantage: If you're already using Azure AD/Entra as your primary IdP, Dynamics 365 provisioning works natively with full SCIM capabilities at no additional cost.

Third-Party IdP Support

For non-Microsoft identity providers, the experience is more limited:

IdPSSO SupportProvisioning MethodLimitations
Okta✓ SAML via OINAPI/SCIM through federationRequires federated identity setup
Google Workspace✓ SAMLCustom federationComplex configuration
OneLogin✓ SAMLCustom federationAdditional setup overhead

Translation: While Dynamics 365 technically supports third-party IdPs, you'll need to configure federation between your IdP and Azure AD to get full provisioning capabilities. This adds complexity and potential points of failure.

Pricing Reality

Microsoft's complex licensing structure means identity features come "free" with expensive user licenses:

Team Member
$8/user/month (view-only access)
Business Central Essentials
$80/user/month
Sales Professional
$65/user/month
Sales Enterprise
$95/user/month
Project Operations
$135/user/month

While SCIM provisioning is "included," you're paying $65-180/user/month for the underlying Dynamics 365 licenses—making this one of the most expensive SCIM implementations available.

What IT admins are saying

Microsoft Dynamics 365's provisioning experience varies dramatically depending on your identity stack:

  • Microsoft shops love the native integration - Azure AD/Entra users get seamless SCIM provisioning as part of the ecosystem
  • Non-Microsoft environments face complexity - Third-party IdPs like Okta require federation setup and custom domain configuration
  • Licensing confusion creates headaches - With pricing ranging from $8-$180/user/month across different modules, determining proper licenses is complex
  • Multiple app confusion - The Dynamics 365 family includes various apps (Sales, Service, Business Central) each with different provisioning considerations

Best experience with Azure AD/Entra ID... Third-party IdP requires federation setup

Microsoft Learn documentation

Works with Microsoft 365 identity. Third-party SAML IdPs supported with custom domain setup

Integration documentation

The recurring theme

If you're already in the Microsoft ecosystem, Dynamics 365 provisioning works beautifully. But organizations using Okta, Google Workspace, or other IdPs face additional configuration complexity to achieve the same seamless experience.

The decision

Your SituationRecommendation
Microsoft-first org with Azure AD/EntraNative Azure AD provisioning works well
Mixed IdP environment (Okta + Azure)Use Stitchflow: simplifies cross-platform management
Large enterprise with multiple D365 modulesUse Stitchflow: automation essential for complex licensing
Non-Microsoft IdP (Google Workspace, OneLogin)Use Stitchflow: avoids federation complexity
Compliance-heavy industry requiring audit trailsUse Stitchflow: comprehensive logging and monitoring

The bottom line

Microsoft Dynamics 365 works seamlessly with Azure AD but becomes complex with third-party IdPs requiring federation setup. For organizations using non-Microsoft identity providers or managing multiple D365 modules, Stitchflow eliminates the federation overhead and provides consistent provisioning regardless of your IdP choice.

Make Microsoft Dynamics 365 workflows AI-native

Microsoft Dynamics 365 gates SCIM behind Included. We build complete offboarding, user access reviews, and license workflows without that SCIM Tax upgrade.

No Included 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

SSO must be configured first

Key limitations

  • Best experience with Azure AD/Entra ID
  • Part of Microsoft 365 ecosystem
  • Third-party IdP requires federation setup
  • Multiple apps in Dynamics family

Configuration for Okta

Integration type

Okta Integration Network (OIN) app with SCIM provisioning

Prerequisite

SSO must be configured before enabling SCIM.

Where to enable

Okta Admin Console → Applications → Microsoft Dynamics 365 → 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).

OIN integration with group linking, schema discovery, attribute writeback. Provisions via Microsoft ecosystem.

Microsoft Dynamics 365 gates SCIM behind Included. Stitchflow automates complete workflows without that SCIM Tax upgrade.

Configuration for Entra ID

Integration type

Microsoft Entra Gallery app with SCIM provisioning

Prerequisite

SSO must be configured before enabling SCIM.

Where to enable

Entra admin center → Enterprise applications → Microsoft Dynamics 365 → 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).

Native integration with Microsoft Entra ID. Best experience with full Microsoft stack. Federated identity management.

Microsoft Dynamics 365 gates SCIM behind Included. Stitchflow automates complete workflows without that SCIM Tax upgrade.

Unlock SCIM for
Microsoft Dynamics 365

Microsoft Dynamics 365 gates SCIM behind Included plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade.

See how it works
Admin Console
Directory
Applications
Microsoft Dynamics 365 logo
Microsoft Dynamics 365
via Stitchflow

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

8x8 logo

8x8

SCIM Tax

UCaaS / Business Communications

SCIM StatusIncluded
Manual Cost$11,754/yr

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.

View full guide
Absorb LMS logo

Absorb LMS

SCIM Tax

Learning Management System (LMS)

SCIM StatusIncluded
Manual Cost$11,754/yr

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.

View full guide
Airbase logo

Airbase

SCIM Tax

Spend Management / Corporate Cards

SCIM StatusIncluded
Manual Cost$11,754/yr

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.

View full guide