Dynamics 365 Licensing: Cloud vs On-Premises — True Cost Comparison

The Core Licensing Models Explained

Dynamics 365 is available in two fundamental deployment models — cloud (SaaS subscription via Microsoft) and on-premises (perpetual licence with hosted deployment). Understanding how each model is priced before moving to total cost analysis is essential.

Dynamics 365 Cloud Subscription

The cloud model operates on a per-user, per-month subscription that includes the application licence, cloud hosting, automatic updates, Microsoft-managed security patching, and built-in disaster recovery. Pricing varies significantly by application module and user licence type:

• Dynamics 365 Business Central Essentials: $80/user/month — core ERP functionality for SMEs
• Dynamics 365 Business Central Premium: $110/user/month — adds Service Management and Manufacturing
• Dynamics 365 Finance: $180/user/month — full financial management for enterprise deployments
• Dynamics 365 Supply Chain Management: $180/user/month — supply chain, inventory, manufacturing
• Dynamics 365 Customer Engagement Plan: $115/user/month — Sales, Customer Service, Field Service
• Dynamics 365 Unified Operations Plan: $190/user/month — Finance plus Supply Chain

These are list prices. Enterprise Agreement customers and those qualifying for specific volume tiers consistently achieve 15–25% discounts from list on cloud subscriptions. The subscription includes mandatory update cycles — Microsoft releases two major update waves per year, and organisations cannot defer updates beyond approximately 90 days.

Dynamics 365 On-Premises

The on-premises model (applicable to Dynamics 365 Business Central On-Premises and Dynamics AX/Finance and Operations on-premises) involves a perpetual licence purchase typically priced at $3,000–$5,000 per named user for core application modules. This one-time licence fee is paired with an annual Software Enhancement (maintenance) payment of approximately 20% of the original licence cost — covering technical support, access to new versions, and Microsoft's online support resources.

Critically, on-premises deployment requires the organisation to provide and maintain the underlying infrastructure: application servers, database servers, load balancers, storage, backup systems, monitoring, and data centre space. These infrastructure costs are separate from the software licence and represent a significant and often underestimated component of the total on-premises cost.

Total Cost of Ownership: The Five-Year Model

Single-year licence cost comparisons systematically favour the on-premises model. Over a five-year horizon — the typical planning cycle for ERP infrastructure decisions — the picture changes materially. The following analysis models a representative mid-market deployment of 150 users on Dynamics 365 Finance and Operations equivalents.

Cloud Five-Year TCO

Licence cost: At $180/user/month for Finance, 150 users pay $324,000 per year at list price. With a 20% EA discount, this reduces to $259,200/year, or $1,296,000 over five years. Support is included in the subscription at no additional charge for standard support tiers.

Infrastructure: $0 — Microsoft provides and manages all cloud infrastructure, security, and disaster recovery as part of the subscription.

Mandatory updates: Two update waves per year. The primary cost is internal IT resource time for testing and validating updates in a sandbox environment — typically 3–5 person-days per wave, or approximately $30,000–$50,000 in internal IT cost over five years.

Implementation and integration: Comparable to on-premises for the initial deployment. One-time cost, not a recurring differentiator between models.

Approximate cloud five-year TCO (excl. implementation): $1.3M–$1.35M

On-Premises Five-Year TCO

Licence cost: At $4,000/user average for 150 users, the initial licence cost is $600,000. Annual software enhancement at 20% of licence cost adds $120,000/year, or $600,000 over five years. Total licence and maintenance over five years: $1,200,000.

Infrastructure hardware: A production-grade Dynamics deployment for 150 users requires dedicated application servers, SQL Server database servers (including SQL Server licences at $15,000–$20,000 per licence), load balancers, and backup infrastructure. Total hardware investment for a 3-tier deployment: $80,000–$200,000 depending on specification and whether virtualised. Hardware refresh at year 3–4 adds a further $80,000–$150,000.

Data centre and operational overhead: Rack space, power, cooling, network connectivity, and monitoring tools add $10,000–$30,000 per year, or $50,000–$150,000 over five years.

IT staff for infrastructure management: A dedicated Dynamics environment requires systems administration for patching, backup management, performance monitoring, and incident response. Even allocating 20% of one FTE's time, at an average loaded IT staff cost of $120,000/year, adds $24,000/year or $120,000 over five years.

Major version upgrades: On-premises Dynamics deployments require major version upgrades every 3–5 years to remain on a supported version. For a 150-user environment, a major upgrade project (including data migration testing, customisation remediation, and user acceptance testing) typically costs $150,000–$400,000 in consulting and internal effort.

Approximate on-premises five-year TCO (excl. implementation): $1.8M–$2.5M

Where On-Premises Can Still Be Competitive

The five-year TCO analysis above does not favour on-premises. However, there are specific scenarios where on-premises deployment remains financially or operationally justified:

Data residency and regulatory requirements: Organisations subject to regulations that require data to remain within specific physical locations or that restrict cloud-based processing may find that compliance costs of cloud deployment (including data sovereignty architecture, data residency addenda, and regulatory approval processes) erode the cloud TCO advantage. For some regulated industries — particularly in healthcare, defence, and certain financial services — on-premises deployment with vetted physical security remains the only compliant option.

Existing infrastructure with extended useful life: If your organisation recently invested in on-premises server infrastructure with a further 5+ years of usable life, the opportunity cost of stranded assets materially reduces the cloud TCO advantage. The decision is no longer cloud versus on-premises from a greenfield position — it is cloud versus continuing to amortise infrastructure already paid for.

Highly customised implementations: Organisations that have invested significantly in custom Dynamics code, bespoke integrations, or heavily modified data models face higher cloud migration costs than organisations running close-to-standard deployments. If your Dynamics implementation is more than 30% customised from the base product, a cloud migration will require a customisation rationalisation project that can cost $200,000–$500,000+ before delivering any cloud TCO benefit.

Bandwidth-constrained remote locations: Global deployments with sites in bandwidth-limited locations (mining operations, remote manufacturing, field offices in emerging markets) may face performance challenges with cloud-based Dynamics that erode user productivity benefits. Hybrid architectures — cloud primary with local synchronisation — add complexity and cost that narrow the cloud advantage.

Hybrid Deployment: The Middle Path

Microsoft has progressively invested in hybrid deployment options that allow organisations to maintain some on-premises workloads while leveraging cloud capabilities. The most relevant hybrid architecture for Dynamics is the on-premises deployment with cloud-managed services: running the Dynamics application on-premises (or in a private cloud/colocation facility) while using Microsoft's cloud services for Power BI reporting, Power Automate workflows, Teams integration, and Dataverse-connected applications.

This hybrid model offers a middle path for organisations that have legitimate reasons not to move their core ERP to the cloud but want to benefit from the productivity tools and AI capabilities that Microsoft increasingly delivers through its cloud services. The licensing structure is more complex — combining on-premises Dynamics licences with cloud service subscriptions — and requires careful management to avoid duplicate licensing or licence type mismatches.

The Hidden Costs That Rarely Appear in Initial Models

In our experience reviewing Dynamics deployment decisions, several cost categories are consistently underestimated or omitted from initial business cases:

• Customisation technical debt: Each year of on-premises operation adds customisation that must eventually be remediated before a cloud migration is possible. Organisations that defer cloud migration often find their eventual migration costs substantially higher than if they had moved earlier when the customisation debt was lower.
• Deferred innovation cost: Dynamics 365 cloud receives continuous feature investment — AI-powered insights, Copilot capabilities, industry-specific modules, and Power Platform integrations — that are delivered exclusively or primarily through the cloud. On-premises deployments access new capabilities through annual major upgrades at best, meaning the feature gap widens progressively. Quantifying this innovation gap is difficult but real.
• Business continuity and disaster recovery: Cloud subscription includes geo-redundant disaster recovery as standard. On-premises DR requires either a secondary site (doubling hardware costs) or a contracted DR provider (typically $20,000–$60,000/year). This cost is frequently excluded from on-premises TCO models.
• Security and compliance overhead: Microsoft's cloud infrastructure is certified against ISO 27001, SOC 2 Type II, GDPR, and dozens of other standards as part of the standard service. On-premises deployments require the organisation to maintain their own equivalent certifications, which is a material internal cost for organisations subject to formal compliance obligations.

Making the Decision: A Practical Framework

The cloud versus on-premises decision should be made through a structured, data-driven process rather than based on initial cost impressions or vendor-provided calculators. The following sequence ensures all relevant factors are considered:

1. Establish the full TCO for both scenarios using the cost categories outlined above, with your organisation's actual user count, customisation level, and infrastructure situation.
2. Assess regulatory and data residency requirements with your legal and compliance teams. If genuine restrictions exist, cloud options may be more limited than assumed — but engage a Microsoft specialist before concluding that on-premises is the only compliant option, as Microsoft's cloud data residency and compliance certifications have expanded significantly.
3. Audit your customisation estate to understand the migration complexity and cost if you are currently on-premises and considering cloud migration.
4. Model the innovation gap — what Microsoft cloud-exclusive features would you gain access to, and what is the business value of that access? This is the hardest dimension to quantify but often the most strategically significant.
5. Negotiate your EA before deciding — the terms and discount structure of your Microsoft Enterprise Agreement materially affect the cloud TCO. Engaging an independent advisor to benchmark your EA terms before committing to either deployment model ensures you are making the decision on the basis of achievable — not list — pricing.

The right answer depends on your organisation's specific profile. For the majority of mid-market and large enterprise organisations without hard regulatory constraints and approaching a hardware refresh cycle, cloud subscription delivers lower five-year TCO, lower operational overhead, and access to continuous platform innovation. For organisations with specific regulatory requirements, recent infrastructure investments, or highly customised implementations, a hybrid or phased approach may better balance immediate cost with long-term strategic flexibility.