Microsoft sells the same software three different ways. The way you buy determines not just what you pay, but what you own, what happens when you stop paying, and how much leverage you have at every renewal for the next decade. This independent guide dissects perpetual, subscription, and SaaS models, maps the economics over a 5-year horizon, identifies the traps embedded in each, and builds the decision framework for your enterprise.
Part of our Microsoft Licensing Knowledge Hub. For agreement-level guidance, see the Microsoft Enterprise Agreement Strategy Guide and the EA vs CSP vs MCA Comparison.
Microsoft's three licence types are not interchangeable packaging for the same product. They are fundamentally different economic relationships between your organisation and Microsoft, each with distinct ownership rights, cost trajectories, renewal dynamics, and exit consequences.
You pay once, you own the right to use that version of the software indefinitely. Microsoft receives a large upfront payment but no guaranteed recurring revenue. To create recurring revenue from perpetual customers, Microsoft introduced Software Assurance, an annual maintenance fee (25–29% of the licence cost) that provides version upgrades, virtualisation benefits, and other entitlements. Without SA, your perpetual licence ages in place. With SA, it behaves like a subscription at 25–29% of its value per year.
You pay monthly or annually for the right to use the current version of the software. Updates are continuous. When you stop paying, the software deactivates. Microsoft receives predictable recurring revenue and the customer receives continuous value, but the customer never builds equity. Ten years of subscription payments buy exactly the same thing as one year: the right to continue paying.
You do not install or manage the software at all. Microsoft hosts it, runs it, updates it, and controls it. You access it through a browser or API. The software runs on Microsoft's infrastructure, your data lives in Microsoft's cloud, and your operational dependency on Microsoft is absolute. SaaS is not a licence type in the traditional sense. It is a service relationship that happens to include software access.
Microsoft's strategic direction is unambiguous: move every customer from perpetual to subscription to SaaS. Each transition increases Microsoft's recurring revenue, deepens customer dependency, and reduces the customer's ability to negotiate at renewal. Understanding this trajectory is essential, not because you should resist it (SaaS is genuinely the right model for many workloads), but because you should choose it deliberately rather than drift into it by default. The organisations that manage this transition intentionally save 20–40% compared to those that allow Microsoft's sales motion to dictate the pace.
A perpetual licence grants your organisation the right to use a specific version of Microsoft software indefinitely. You pay once (through a Volume Licensing programme like the Enterprise Agreement, Open Value, or MPSA) and receive a licence key and download rights for that version. The licence does not expire. If you purchase Windows Server 2022 Standard as a perpetual licence, you can run Windows Server 2022 Standard for as long as the hardware supports it.
Microsoft has been systematically narrowing the products available on perpetual terms, but in 2026, perpetual licences remain available for: Windows Server (Standard and Datacenter), SQL Server (Standard and Enterprise), Office LTSC (Long-Term Servicing Channel, a version of Office without cloud features, updated every 3–5 years), Windows Desktop OS (Windows 11 Pro/Enterprise), and select on-premise server products (Exchange Server, SharePoint Server, Project Server, Visio). Microsoft 365 is not available as a perpetual licence. Dynamics 365 is no longer sold perpetually for new customers.
You pay once and run the software until it reaches end of support (typically 10 years: 5 years mainstream + 5 years extended). No recurring costs, but no upgrades, no virtualisation benefits, no Azure Hybrid Benefit, and no support beyond the extended support period.
You pay 25–29% of the licence value annually, effectively converting the perpetual licence into a subscription at roughly one-quarter of the purchase price per year. Over a 5-year EA cycle, SA payments can equal or exceed the original licence cost. The value of SA depends entirely on which benefits you actually use. See our Software Assurance CIO Playbook.
The software is stable and does not require continuous updates, such as a SQL Server database running a legacy application that will not be upgraded.
The organisation has no plans to migrate to Azure, eliminating the Azure Hybrid Benefit justification for SA.
The product will be used beyond a typical 5-year subscription cycle. The longer you hold a perpetual licence without SA, the lower the annualised cost.
The organisation values ownership: the ability to continue using the software regardless of future contract negotiations with Microsoft.
Version obsolescence: Without SA, you are stuck on the version you purchased. After mainstream support ends, you receive only security updates (extended support). No new features, no design changes, no compatibility updates.
SA creep: Microsoft's sales team will argue that SA is "essential" for every perpetual licence. It is not. SA delivers clear value for virtualised server products and Azure-bound workloads, but for stable desktop OS installations, Office LTSC on fixed workstations, and legacy server applications, SA is an expensive maintenance contract on software that does not need maintaining.
Discontinuation risk: Microsoft may stop offering perpetual versions of products you depend on, forcing a subscription migration at renewal.
Subscription licences grant the right to use software for as long as you pay the recurring fee, typically monthly or annually. The subscription includes continuous updates, cloud storage allocations, and access to companion services. When you stop paying, your access is suspended (typically after a 30–90 day grace period), and eventually your data may be deleted. You own nothing at the end of a subscription. Your ten years of payments entitle you to exactly as much software as your first month.
The dominant subscription product, covering Office apps, Exchange Online, SharePoint, Teams, OneDrive, and security/compliance features. See our E3 vs E5 vs F3 comparison.
CRM and ERP modules sold as per-user monthly subscriptions.
Power BI Pro, Power Apps, Power Automate as per-user or capacity-based subscriptions.
Microsoft's AI assistant, licensed as a per-user subscription add-on.
Subscription pricing appears lower per period than perpetual + SA. A Microsoft 365 E3 subscription at approximately $36/user/month ($432/year) provides Office apps, Exchange Online, SharePoint, Teams, and 1TB OneDrive, a bundle that would cost significantly more to replicate through perpetual Office licences plus Exchange Server licences plus SharePoint licences plus individual service purchases.
The economics shift when you factor in duration. Over 5 years, that M365 E3 subscription costs $2,160 per user. Over 10 years: $4,320. A perpetual Office LTSC licence costs approximately $250–$400 per user (one time) and lasts indefinitely. If the user only needs Office applications, the perpetual licence is dramatically cheaper over any horizon beyond 12–18 months. The subscription wins on breadth of services; the perpetual wins on cost when you do not need the full bundle.
You need the full Microsoft 365 service bundle: Office + email + collaboration + security + compliance.
Your workforce is mobile and requires multi-device access with continuous updates.
Your organisation has fluctuating headcount and subscriptions can be scaled up and down within contractual constraints.
You are committed to the Microsoft cloud ecosystem for the foreseeable future.
Microsoft increases subscription prices at renewal, typically 5–10% per cycle. Over a decade, compounding increases can push subscription costs 30–60% above the initial price. Negotiate price protections and cap clauses to limit this exposure.
Enterprise subscription agreements typically include minimum user counts that cannot be reduced during the term. If you hire 5,000 employees and sign a 3-year EA, then downsize to 3,500, you pay for 5,000 for the remainder. The true-up process adds users but never subtracts them mid-term.
After years of subscription-based M365, your email, files, collaboration workflows, identity management, and security architecture are deeply embedded in Microsoft's cloud. Leaving is technically possible but operationally devastating. This is not a bug; it is Microsoft's strategy.
The most common subscription trap is purchasing higher-tier SKUs than users need. An E5 subscription at ~$57/user/month costs nearly 60% more than E3. If the user does not use E5-exclusive features, that premium is waste. See our E3 vs E5 vs F3 guide.
SaaS is not a different way of buying software. It is a different paradigm entirely. With perpetual and subscription licences, you install and run the software on your infrastructure (on-premise or IaaS). With SaaS, Microsoft runs the software on their infrastructure. You access it through a browser, API, or thin client. Microsoft controls the version, the update schedule, the feature set, the availability, and the infrastructure. You control your data and your configuration, within the boundaries Microsoft defines.
The line between "subscription" and "SaaS" in Microsoft's portfolio is increasingly blurred. The key SaaS products include: Exchange Online (email as a service), SharePoint Online (collaboration), Teams (communication), OneDrive for Business (file storage), Dynamics 365 Online (CRM/ERP), Power BI Service (analytics), Intune (device management), and Microsoft Entra ID (identity). Most Microsoft 365 subscriptions are, in practice, SaaS: you are purchasing access to cloud-hosted services, not locally installed software. See our Entra ID licensing guide and endpoint management licensing guide.
No servers to maintain, no patches to apply, no storage to provision, no disaster recovery to architect. SaaS transfers complexity to Microsoft.
Microsoft deploys updates continuously. SaaS delivers the fastest access to new features and the most predictable operational model.
For organisations fully committed to cloud-first strategies that want to minimise IT operational burden, SaaS is the most operationally efficient model.
SaaS creates the deepest form of vendor dependency. Your email, files, identity, security, compliance, and collaboration workflows all live on Microsoft's infrastructure. Moving to another platform requires migrating everything simultaneously, a project that costs millions and disrupts every employee. This dependency gives Microsoft near-complete pricing power at renewal.
Your data resides in Microsoft's data centres. While Microsoft provides geo-residency options and compliance certifications, you do not control the physical infrastructure. For organisations in regulated industries, SaaS may require additional contractual protections or may be unacceptable for certain data classifications.
Microsoft can and does change SaaS features unilaterally. The Teams unbundling from Office 365 is one example: a feature that was included became a separately priced add-on. In a SaaS model, you have no recourse when the vendor changes the product. You cannot "stay on the old version" because there is no old version.
SaaS pricing appears simple (per user per month), but ancillary costs accumulate: additional data storage beyond base allocations, premium security and compliance features gated behind higher tiers, API call limits that constrain integration workflows, and premium support tiers that add 5–15% to the total cost.
The following comparison models the 5-year total cost of ownership for a representative Microsoft workload: an Office productivity deployment for 1,000 users under each licence type.
| Factor | Perpetual (No SA) | Perpetual + SA | Subscription (M365 E3) |
|---|---|---|---|
| Year 1 Cost (1,000 Users) | $350,000 (one-time) | $350,000 + $91,000 SA | $432,000 |
| Annual Recurring | $0 | $91,000 (SA) | $432,000 |
| 5-Year Total | $350,000 | $805,000 | $2,160,000 |
| What You Get | Office LTSC apps only | Office LTSC + upgrades + benefits | Full M365 bundle (cloud-hosted) |
| What You Keep If You Stop | Office LTSC forever | Office LTSC forever (version at SA lapse) | Nothing |
| Email Included | No (separate Exchange needed) | No | Yes (Exchange Online) |
| Teams / SharePoint / OneDrive | No | No | Yes |
| Continuous Updates | No | Yes (with SA) | Yes |
| Server Infrastructure Required | Yes (for email, collaboration) | Yes | No |
| Vendor Lock-In | Low (own the licence) | Medium (SA dependency for benefits) | Very High (data + workflows in cloud) |
The comparison reveals a fundamental trade-off that Microsoft's sales motion deliberately obscures. Perpetual is dramatically cheaper if you only need Office applications ($350K vs $2.16M over 5 years). But the subscription is genuine value if you need the full M365 bundle: replicating Exchange Online, SharePoint Online, Teams, OneDrive, Intune, and the security stack through on-premise perpetual products would cost far more than $2.16M when you include server hardware, administration, and licensing for each component separately. The question is not "which is cheaper?" but "what do you actually need?" Organisations that buy the full bundle when they only need the Office apps are overpaying by 5–6× over a 5-year horizon.
In practice, almost no large enterprise runs exclusively one licence type. The typical Microsoft estate in 2026 is a hybrid of all three, and managing the interactions between them is where complexity and cost concentrate.
For the knowledge workforce, covering Office, email, Teams, and collaboration.
For the data centre, where on-premise infrastructure still hosts critical databases and applications.
For manufacturing floors, labs, or kiosks that need Office apps but not cloud services.
For cloud workloads, with Azure Hybrid Benefit applied to perpetual Windows Server and SQL Server licences.
Paying twice for the same functionality: Paying for Microsoft 365 subscriptions that include Office apps while also holding perpetual Office licences. See our guide on eliminating redundant licences.
SA on migrating workloads: Maintaining Software Assurance on perpetual licences that are being replaced by subscriptions. SA on SQL Server licences while migrating to Azure SQL Database is pure waste.
Orphaned CALs: Holding perpetual CALs for users who have fully migrated to Microsoft 365 SaaS services. The CALs cover on-premise server access that no longer exists.
Microsoft's commercial engine is designed to migrate every perpetual customer to subscription. The mechanism is predictable: restrict perpetual product updates, enhance subscription-exclusive features, increase the gap between perpetual and subscription capabilities, and eventually make the perpetual version so far behind that the "choice" becomes inevitable. This migration is not inherently bad, but the economics of the transition contain traps that cost enterprises millions when unmanaged.
When you migrate from perpetual Office to Microsoft 365 subscription, your perpetual licences still exist but are redundant. You paid $350,000 for perpetual Office; you are now paying $432,000/year for M365 that includes Office. The perpetual licences have no resale market (Microsoft prohibits licence transfer in most Volume Licensing programmes). The asset is stranded. Plan the transition to coincide with the natural end-of-life of your perpetual licences.
Organisations with perpetual licences plus Software Assurance often transition to subscription without terminating SA. The result: paying SA on perpetual licences while paying subscription fees for the same product's cloud version. This double-payment window can last 1–3 years (the remainder of the EA term) and costs 25–40% of the subscription value in waste. See our licence usage audit guide.
Enterprise Agreements allow you to increase subscription quantities at each annual true-up, but most EA structures do not allow decreases mid-term. If you migrate 2,000 users from perpetual to subscription in Year 1, then reduce headcount to 1,500 in Year 2, you pay for 2,000 subscriptions for the remaining 2 years. Negotiate termination and reduction rights before committing to large subscription volumes.
A US manufacturing company with 8,000 employees held perpetual Office 2019 licences ($2.8M) with SA ($728K/year) under their EA. Microsoft's account team proposed a "seamless upgrade" to M365 E3 at the EA renewal at $3.46M/year. The company agreed without a full analysis.
Result: Year 1 they paid $3.46M (M365) plus $728K (SA on perpetual licences that was not terminated until Year 2), totalling $4.19M instead of $3.46M. Over the remaining 2 years of the EA, the stranded SA cost $728K in pure waste. Additionally, 2,200 of the 8,000 users were factory workers who only needed email. F3 at $8/user/month would have covered them at $211K/year instead of $950K at E3 pricing.
Total avoidable cost over the 3-year EA: $2.95M from an unmanaged transition that the Microsoft sales team presented as a routine upgrade.
Office + email + Teams + compliance + advanced security. Microsoft 365 E3 or E5 subscription.
Email + Teams only. Microsoft 365 F1 or F3 subscription at a fraction of the E3/E5 cost.
Office apps on a shared machine. Office LTSC perpetual per device.
Contractors, seasonal workers using non-Microsoft tools. No licence required.
This segmentation alone typically reduces Microsoft spend by 15–25%. See our M365 plan selection guide.
Windows Server and SQL Server: perpetual + SA. SA provides virtualisation benefits and Azure Hybrid Benefit that deliver measurable value.
Perpetual + SA through the migration window (to maintain Azure Hybrid Benefit), then drop SA post-migration.
SaaS/PaaS (Azure SQL Database, Azure App Service). No perpetual licence needed.
If you are moving from perpetual to subscription, negotiate the transition as a commercial event, not a routine renewal. Microsoft should offer:
Discounted subscription rates during the transition period to offset the stranded value of your perpetual licences.
Applying the remaining value of your SA investment toward subscription costs.
The ability to reduce subscription quantities if your user base shrinks.
Capped renewal increases for 2–3 cycles to prevent escalation.
These are all negotiable, but only if you negotiate them. Microsoft's standard proposal includes none of these protections. See our Microsoft Contract Negotiation Service and EA negotiation strategies.
Implement quarterly reviews of your licence type portfolio:
Are perpetual licences with SA still delivering value, or should SA be dropped?
Are subscription quantities aligned with actual headcount?
Are there users on E5 subscriptions who should be on E3 or F3?
Are there redundant licences (perpetual + subscription covering the same user)?
This ongoing governance prevents the slow accumulation of waste that turns an optimised licence portfolio into an overpriced one within 12–18 months. Our EA Renewal Readiness Assessment provides the structured analysis, and our EA Renewal Preparation Toolkit provides the templates and frameworks.
Yes, for specific products. Windows Server, SQL Server, Office LTSC, and select on-premise server products remain available as perpetual licences through Volume Licensing programmes. However, Microsoft 365, Dynamics 365 (for new customers), and most cloud-first products are subscription-only. The trend toward subscription-only availability is accelerating. Organisations that value perpetual ownership should negotiate perpetual licence purchases during their current EA cycle. Waiting for the next cycle may mean reduced or eliminated perpetual options for specific products.
Microsoft provides a graduated data retention process. When a subscription expires, your users lose access immediately (or within 24 hours). Your data is retained in a "suspended" state for 30–90 days. During the suspended period, an admin can still export data. After the suspension period, data enters a "deletion" phase and is permanently removed within 90 additional days. The total window from expiration to deletion is typically 90–180 days, but the exact timeline depends on your contract terms. Ensure you have a data export plan before allowing any subscription to lapse.
If you only need Office desktop applications (Word, Excel, PowerPoint, Outlook), perpetual Office LTSC is dramatically cheaper over any horizon beyond 12–18 months. Office LTSC costs approximately $250–$400 per user one time versus M365 E3 at ~$432/user/year. Over 5 years, perpetual costs $250–$400 total; M365 costs $2,160. The subscription only becomes the better economic choice when you genuinely use the full M365 bundle: Exchange Online, Teams, SharePoint, OneDrive, Intune, and the security/compliance features. The answer is product-specific, not universal.
Azure Hybrid Benefit (AHB) allows you to use existing Windows Server or SQL Server perpetual licences (with active Software Assurance) to reduce the cost of Azure VMs by 40–80%. The perpetual licence "travels" to Azure. You apply your on-premise core licences to Azure VMs, eliminating the Windows or SQL Server licensing component of the VM cost. Without SA, AHB is not available, and the Azure VM includes the full licence cost. The strategic implication: maintain perpetual + SA on Windows Server and SQL Server licences you plan to use in Azure, even if the on-premise workloads are retiring.
For any organisation spending $2M+ annually on Microsoft, independent advisory delivers measurable ROI on licence type optimisation. Microsoft's account team has a structural incentive to move you to subscription (it maximises their recurring revenue). An independent advisor provides: objective licence type analysis (which products should be perpetual, which subscription, which SaaS), pricing benchmarks across hundreds of comparable EA deals, transition negotiation support (bridge pricing, SA credits, price protections), and ongoing governance to prevent waste accumulation. At Redress Compliance, Microsoft licence type optimisation is a core service within our EA Optimisation and Contract Negotiation practices.