Microsoft Dynamics 365 can be deployed as a cloud SaaS service or as on-premises software running in your data centre. The licensing models differ fundamentally: cloud uses per-user-per-month subscriptions (OPEX), while on-premises uses perpetual Server + CAL licences (CAPEX). Microsoft’s dual-use rights allow cloud subscribers to run equivalent on-premises software enabling hybrid deployments without double-licensing. This guide provides CIOs with a comprehensive comparison of both models.
In the cloud model, Dynamics 365 is a Microsoft-hosted SaaS service. You subscribe on a per-user-per-month basis, and Microsoft manages all infrastructure — servers, databases, storage, security patching, and version upgrades. There is no separate charge for application servers or SQL Server licences; these are included in the subscription fee.
Cloud licences are subscription-based: you pay a monthly fee per user for as long as they need access. Typical costs range from $40/user/month for Customer Service Professional to $210/user/month for Finance or Supply Chain Management. The subscription includes the application, infrastructure, storage (base allocation), support, and all version upgrades. There is no upfront capital expenditure — costs are fully OPEX. You can add or remove users at each billing cycle, making the model inherently elastic.
Cloud subscribers receive two major updates per year (Wave 1 in April, Wave 2 in October) plus continuous minor updates — all included in the subscription at no additional cost. Microsoft delivers new features, security patches, and performance improvements automatically. There is no upgrade project to plan, test, or execute internally. This eliminates the significant cost of version upgrades that on-premises customers face (typically $200K–$1M+ per major upgrade for large deployments including testing, customisation rework, and downtime).
Cloud licensing scales seamlessly: add 50 users for a 3-month project, then remove them. You pay only for active subscriptions. This elasticity is particularly valuable for seasonal businesses, M&A integration, and pilot programmes. On-premises perpetual licences cannot match this flexibility — buying 50 CALs for a temporary need creates stranded assets once the need ends. For organisations with variable user counts, cloud’s pay-per-use model can reduce annual licensing costs by 20–40% compared to provisioning on-premises for peak demand.
Cloud licensing is self-enforcing: Microsoft controls access through subscription entitlements. You cannot exceed your licensed user count without Microsoft knowing — which eliminates the compliance risk inherent in on-premises deployments where unlicensed users can access the system without immediate detection. For organisations that have faced audit exposure on-premises, moving to cloud removes this risk category entirely.
On-premises Dynamics 365 (including legacy Dynamics CRM and Dynamics AX/Finance and Operations deployed in your data centre) uses a traditional Server + Client Access Licence (CAL) model. You purchase perpetual licences upfront and own them indefinitely.
You license the Dynamics 365 Server software with a one-time fee per server instance — typically several thousand dollars per server. This covers the right to install and run the application server. If you deploy multiple server instances (for high availability, dev/test, or disaster recovery), each may require its own server licence depending on the specific product use rights. The server licence is perpetual — once purchased, you can run that version indefinitely.
Each user or device accessing the on-premises system requires a CAL. CALs come in different levels: Professional CALs grant full functionality (approximately $1,000 per user, one-time), while Basic or Essential CALs provide limited access at lower cost. Device CALs are an alternative when multiple users share a single device. CALs are perpetual — you own them outright — but they entitle access only to the specific version they were purchased for unless you maintain Software Assurance.
Software Assurance is an annual maintenance fee (typically 20–25% of the original licence cost per year) that provides version upgrade rights, technical support, and planning services. Without SA, your perpetual licence allows you to run the version you purchased indefinitely — but you cannot upgrade to newer versions without purchasing new licences. SA is the critical decision: maintaining it ensures access to latest versions; letting it lapse locks you into your current version permanently (re-acquiring SA after a lapse typically requires repurchasing the underlying licence).
On-premises licensing covers only the application software. You must separately licence and maintain: Windows Server, SQL Server (a significant cost — Enterprise Edition can exceed $15K per core), networking infrastructure, backup and disaster recovery systems, and the IT staff to manage everything. These infrastructure costs are often underestimated in cloud-vs-on-prem comparisons but typically represent 40–60% of the total on-premises cost beyond the Dynamics licences themselves.
| Dimension | Cloud (SaaS) | On-Premises (Server + CAL) |
|---|---|---|
| Licence model | Per-user-per-month subscription | One-time perpetual Server + CAL |
| Cost structure | OPEX — predictable monthly spend | CAPEX — large upfront, lower ongoing |
| Infrastructure | Included (Microsoft-managed) | Separate — Windows, SQL, hardware, staff |
| Updates | Automatic — 2 major waves/year included | Manual — requires SA + internal upgrade project |
| Scaling up | Add subscriptions instantly | Purchase additional CALs (lead time + cost) |
| Scaling down | Remove subscriptions at billing cycle | Perpetual — sunk cost, no recovery |
| Feature availability | Latest features, AI, Power Platform integrations | Feature-limited — cloud-first development |
| Compliance risk | Self-enforcing (subscription controls access) | Requires CAL tracking and audit readiness |
| Customisation | Extensibility model — must follow Microsoft guidelines | Full code access — deep customisation possible |
| Data residency | Microsoft data centres (geo-selection available) | Full control — data stays in your environment |
| Long-term cost (7+ yrs) | Higher cumulative subscription cost | Lower if infrastructure exists and SA maintained |
| Best for | Agility, innovation, variable workloads | Regulatory lock-in, deep customisation, existing infra |
A meaningful cloud-vs-on-premises comparison requires modelling total cost of ownership (TCO) over a multi-year horizon — not just licence prices. The following framework covers a 500-user Dynamics 365 Finance deployment.
| Cost Category | Cloud (5-Year Total) | On-Premises (5-Year Total) | Notes |
|---|---|---|---|
| Application licences | $6,300,000 | $1,500,000 | Cloud: $210/user/mo × 500 × 60 mo. On-prem: $3,000/CAL × 500 (one-time) |
| Software Assurance / support | Included | $1,500,000 | SA at ~20%/year × 5 years on licence value |
| SQL Server licences | Included | $400,000 | Enterprise Edition for production + DR |
| Windows Server + CALs | Included | $150,000 | Server OS + user CALs for application tier |
| Hardware / hosting | Included | $600,000 | Servers, storage, networking, DR site |
| IT staff (DBA, sysadmin) | $0 (Microsoft-managed) | $750,000 | 1.5 FTE dedicated to D365 infra over 5 years |
| Major version upgrades | Included (automatic) | $500,000 | 1–2 upgrades over 5 years (testing, rework, downtime) |
| 5-Year TCO | $6,300,000 | $5,400,000 | On-prem is ~14% cheaper — but only with existing infrastructure |
Cloud delivers better TCO when: (1) you lack existing data centre infrastructure and would need to build or lease, (2) your user count is variable (seasonal, M&A, growth uncertainty), (3) you need latest features and AI capabilities, (4) you want to eliminate IT infrastructure overhead, (5) your upgrade history shows version lag (skipping upgrades to save cost creates technical debt), or (6) your deployment is under 300 users where on-prem infrastructure overhead is disproportionately expensive. For most organisations starting fresh, cloud is cheaper within the first 3 years when full TCO is considered.
On-premises delivers better TCO when: (1) you have fully depreciated data centre infrastructure and idle IT capacity, (2) your user count is large and stable (500+ with minimal fluctuation), (3) regulatory requirements mandate on-premises data residency with no cloud exceptions, (4) you have deep customisations that are incompatible with the cloud extensibility model, (5) you maintain SA consistently and can upgrade efficiently, or (6) your planning horizon extends beyond 5 years with stable requirements. The critical caveat: on-prem TCO advantage erodes quickly if SA lapses, upgrades are deferred, or infrastructure requires refresh.
Microsoft provides dual-use rights that allow cloud subscribers to run equivalent on-premises software — a powerful provision for hybrid deployments and migration planning.
Dynamics 365 cloud subscriptions include the right to deploy the equivalent on-premises software for licensed users. If you have 100 Dynamics 365 Sales Online subscriptions, those 100 users can legally access a Dynamics 365 Sales on-premises server. This enables testing environments, hybrid usage during migrations, and fallback scenarios without purchasing separate on-premises licences. Critical limitation: these rights are not perpetual — if the cloud subscription ends, the on-premises access rights expire immediately. You do not retain perpetual on-premises licences from a cloud subscription.
If you own on-premises Dynamics licences with active Software Assurance, Microsoft offers transition benefits to move to the cloud. These include discounted “from-SA” subscription SKUs that recognise your existing investment, typically providing 40–60% off cloud subscription rates for a transition period (usually 1–3 years). After the transition period, pricing reverts to standard rates. This incentive structure means organisations with active SA should negotiate transition pricing aggressively before committing to full-price cloud subscriptions — Microsoft’s sales teams have authority to offer substantial credits to facilitate cloud migration.
Dual-use rights enable simultaneous cloud and on-premises deployment — the foundation of hybrid strategies. Common hybrid scenarios: running on-premises CRM for data-sensitive processes while using cloud for customer-facing portals, maintaining an on-premises instance for custom integrations while migrating standard workflows to cloud, or operating both environments during a phased migration. From a licensing perspective, as long as each user consuming both environments has a valid cloud subscription, no additional licences are required. The cloud subscription covers access to both deployments for that user.
Cloud licences for Dynamics 365 are tied to the Microsoft tenant, not to a specific data centre region. You can move your cloud deployment between Azure regions for data residency, latency optimisation, or regulatory compliance without licence implications. This is a significant advantage over on-premises, where moving to a new data centre may trigger server licence recounting. Additionally, Dynamics 365 cloud subscriptions are portable across EA, CSP, and Web Direct procurement channels — you can change your purchasing mechanism without affecting your deployment or user assignments.
Microsoft’s development investment is overwhelmingly cloud-first. Understanding the feature gap is critical for CIOs evaluating long-term on-premises viability.
| Feature Category | Cloud Availability | On-Premises Availability | CIO Impact |
|---|---|---|---|
| Copilot AI assistance | Full — Sales, Service, Finance, Supply Chain | Not available | Competitive disadvantage for AI-driven workflows |
| Power Platform integration | Native — Power BI, Power Automate, Power Apps | Limited — requires manual connector setup | Reduced automation and analytics capabilities |
| Dataverse / Common Data Model | Built-in unified data platform | Not available | No cross-application data unification |
| Bi-annual feature waves | Automatic — April and October releases | Manual upgrade required (6–18 month lag typical) | Delayed access to functionality improvements |
| Teams / Outlook integration | Deep native integration | Basic — requires configuration | Reduced productivity for collaboration workflows |
| Security / compliance tools | Microsoft 365 Compliance Centre, DLP, eDiscovery | Self-managed — separate tools required | Higher compliance management overhead |
| Mobile experience | Cloud-optimised mobile apps | Available but limited updates | Field workforce productivity gap |
The single biggest migration barrier is deep customisation. On-premises deployments often contain direct code modifications, custom SQL queries, and integrations that bypass the application layer. Cloud Dynamics 365 enforces an extensibility model that prohibits direct code changes — customisations must use supported APIs and extension points. Before committing to migration, audit every customisation: categorise as (a) compatible with cloud extensibility, (b) requires rework using supported patterns, or (c) not feasible in cloud — requires alternative architecture. This assessment typically takes 4–8 weeks for complex deployments and determines migration timeline and cost.
If you have active Software Assurance, negotiate transition credits before accepting standard cloud pricing. Microsoft’s “Bridge to Cloud” programmes and from-SA SKUs can provide 40–60% discounts on cloud subscriptions for 1–3 years. These programmes are not always proactively offered — you must ask. Present your total Microsoft spend (EA, Azure, M365) as leverage: Microsoft is more willing to discount D365 cloud transition pricing when it secures a larger overall commitment. Independent advisory can benchmark your entitlement and identify the maximum discount achievable.
Use dual-use rights to run cloud and on-premises in parallel during migration. A typical transition timeline for large deployments: months 1–3 for cloud environment setup and configuration, months 4–8 for data migration and integration testing, months 9–12 for user acceptance testing and phased go-live. During this entire period, the same users can access both environments under the cloud subscription — no double-licensing required. Plan for a minimum 3-month parallel run after go-live before decommissioning the on-premises environment, ensuring all edge cases and integrations are validated.
Yes — Microsoft’s dual-use rights allow Dynamics 365 cloud subscribers to deploy and access the equivalent on-premises software. If you have 200 Dynamics 365 Sales Online subscriptions, those 200 users can legally access a Dynamics 365 Sales on-premises server at no additional cost. This is valuable for hybrid deployments, migration staging, and disaster recovery scenarios. The critical limitation: these rights are tied to active cloud subscriptions. If you cancel the cloud subscription, the on-premises access rights expire immediately — you do not retain perpetual on-premises entitlements from cloud subscriptions.
On licence cost alone, yes — perpetual on-premises licences with SA are typically cheaper than cloud subscriptions over a 5–7 year horizon. However, full TCO analysis usually narrows or reverses this gap. On-premises requires SQL Server licensing ($400K+ for Enterprise Edition), Windows Server licensing, hardware, IT staff, and periodic upgrade projects — costs that are included in cloud subscriptions. For a 500-user Dynamics 365 Finance deployment, our modelling shows on-premises is approximately 14% cheaper over 5 years when existing infrastructure is in place — but 20–30% more expensive if new infrastructure must be provisioned. The breakpoint depends entirely on your existing infrastructure and IT capacity.
The feature gap is significant and growing. Cloud-exclusive features include: Copilot AI assistance across all D365 modules, Dataverse (unified data platform), native Power Platform integration (Power BI, Power Automate, Power Apps), deep Microsoft Teams and Outlook integration, automatic bi-annual feature waves, and Microsoft 365 compliance tools (DLP, eDiscovery). On-premises receives security patches and maintenance updates, but new functional capabilities are cloud-first — many are cloud-only. If your business strategy depends on AI, automation, or cross-application integration, on-premises will become an increasingly limiting constraint.
If you have active Software Assurance on your on-premises Dynamics licences, Microsoft offers “Bridge to Cloud” and from-SA transition SKUs that provide 40–60% discounts on cloud subscription rates for 1–3 years. These programmes recognise your existing investment and reduce the financial impact of the transition. During migration, dual-use rights allow you to run both environments simultaneously under your cloud subscriptions — no double-licensing required. Key: negotiate transition pricing before accepting standard cloud rates, and align the migration with your EA renewal to maximise leverage. Letting SA lapse before transitioning forfeits these transition benefits.
Cloud Dynamics 365 enforces a controlled extensibility model — direct code modifications, custom SQL queries, and integrations that bypass the application layer are not permitted. Customisations must use supported APIs, extension points, and the published extensibility framework. Many on-premises customisations can be refactored to work within this model, but some deep modifications may require alternative architectures or ISV solutions. Before committing to migration, conduct a customisation audit: categorise each modification as cloud-compatible, requires rework, or not feasible in cloud. This assessment (typically 4–8 weeks) determines your migration timeline, cost, and whether a phased approach is needed.
Yes — hybrid deployment is fully supported under dual-use rights. Common hybrid patterns include: running sensitive financial processes on-premises while customer-facing portals run in cloud, maintaining on-premises for custom integrations while migrating standard workflows, or operating a phased migration where modules move to cloud sequentially over 12–18 months. Each user accessing both environments needs only a cloud subscription (no separate CAL purchase). Technical integration between environments requires data synchronisation setup (typically using Dual-Write or custom integration patterns), which adds complexity but is well-documented by Microsoft.
For deployments exceeding $500K in annual Dynamics 365 spend, independent advisory typically pays for itself within the first year. The cloud-vs-on-premises decision involves complex trade-offs: TCO modelling with accurate infrastructure cost allocation, customisation compatibility assessment, transition pricing negotiation (ensuring you receive maximum SA-based discounts), EA renewal alignment, and hybrid deployment licensing optimisation. Independent advisors bring benchmark data from comparable migrations, knowledge of Microsoft’s internal discount authority, and experience structuring transition agreements that protect your investment during the multi-year migration process.