CSP, Open Value or Perpetual: Which Buying Route Suits Your Business?

Fix it now

These are three ways of paying for the same software, not three products. CSP is partner-billed subscription with short terms, Open Value is a three-year volume agreement with Software Assurance built in and payments spread annually, and perpetual means owning a version outright. Cash flow and headcount decide it far more often than features do.

1. Buy through CSP if headcount moves, if you want monthly or annual billing, and if you want a partner rather than a portal to call. It is also where perpetual licence-only purchases now go.
2. Buy Open Value if you want Software Assurance benefits across a standardised estate, spread over three annual instalments. It needs an initial purchase of at least five licences.
3. Buy Open Value Subscription instead if the licence count is likely to fall, because it lets you reduce the count at each anniversary; you stop paying and you stop using the software.
4. Buy perpetual if the machines are fixed, stay for years and need no cloud services. Do not expect Software Assurance to be attachable afterwards.
5. Do not plan around Open License. It stopped taking new purchases and renewals on 1 January 2022 and Microsoft directed licence-only buying to CSP.
6. Do not assume a server product can be bought once and left. Exchange Server SE now requires active Software Assurance or a qualifying Microsoft 365 subscription to install, run and stay current.

If the answer is obvious from your billing preference, stop here. Below is what Software Assurance actually buys, why the perpetual-versus-subscription sum has to be run over the real service life, and where charity and academic programmes beat any commercial negotiation.

Why it happens

CSP means buying through a Microsoft partner who handles provisioning, billing and first-line support. Under the current new-commerce terms, licence-based subscriptions have a cancellation window of seven calendar days from purchase with a prorated refund, whatever the term length – monthly, annual or multi-year. After that window the term runs. That single fact is what people most often get wrong: an annual CSP term is a commitment, not a rolling arrangement you can stop at the end of any month.

Open Value is a volume licensing agreement with a three-year term and an initial purchase of five or more licences. Software Assurance is included, payments are spread across the term rather than paid up front, and you standardise on the agreed products. The non-subscription variant leaves you owning the licences perpetually once the term completes. Open Value Subscription is the lower-commitment variant: the total licence cost can fall in years when the device or user count falls, and when you stop paying, the right to use the software ends.

Perpetual means buying a specific version and keeping it. Security updates run for that version’s supported lifetime, no new features arrive, and nothing renews. The programme that used to sell small volumes of perpetual licences – Open License – closed to new purchases and renewals on 1 January 2022, and Microsoft directed licence-only purchases to CSP partners instead. Perpetual software did not disappear; the agreement wrapper around it did.

Full reference

The three routes side by side

Capital or operating expenditure, and why finance decides it

Perpetual is capital expenditure: a larger payment now, nothing afterwards, a written-down asset. Subscription is operating expenditure: a smaller recurring cost that never stops and never becomes an asset. Which your finance team prefers is not a technicality and it frequently settles the question before any feature comparison begins. What upsets the arithmetic is headcount. A business growing from twenty to thirty-five people over three years buys fifteen more perpetual licences at whatever the price is when it needs them; the subscription simply scales. A business that shrinks pays for perpetual licences nobody uses.

What Software Assurance actually buys

Version upgrade rights are the headline benefit and the least interesting one. The benefits that change designs are the rights: upgrading each covered licence to the most recent version, step-up licences between editions, backup and disaster recovery instances, Azure Hybrid Benefit for Windows Server, the Flexible Virtualization Benefit for running on an Authorised Outsourcer’s hardware, and Licence Mobility for server applications. If you run clustered or virtualised servers, reassignment and mobility rights alone often justify it. If you run a dozen fixed desktops, they never will.

Two mechanical points catch people. Software Assurance is a volume licensing benefit and cannot be added to a retail purchase after the fact, so the requirement decides your buying route rather than the other way round. And on OEM licences it has to be acquired within 90 days of purchase, which means the decision has to be made when the hardware is ordered, not when someone later discovers they need failover rights.

Perpetual is no longer a universal option on the server side

This is the change most likely to invalidate an old plan. Exchange Server Subscription Edition, released on 1 July 2025, requires an active qualifying entitlement – Software Assurance on Exchange Server licences, or a qualifying Microsoft 365 subscription with on-premises server use rights – to install, run and stay current, and the CALs need the same coverage. It follows the Modern Lifecycle Policy rather than a fixed end date, which means staying current is the condition of staying supported. Check the licensing terms for each on-premises server product you intend to buy rather than assuming the whole family still behaves like a one-off purchase.

Downgrade rights, which are part of the route you choose

Downgrade rights let you run an earlier version under a current-version licence, and they are not distributed evenly. Application, system and server licences obtained through Commercial Licensing programmes include them. OEM licences carry limited downgrade rights, generally only where Software Assurance was added within 90 days, though some OEM server software is an exception. Retail full-package product generally does not include them for application and system software. If your plan involves buying the current version and deploying the previous one while a supplier certifies it, the buying route is what makes that legal.

Before you price anything commercially

If you are a registered charity, a school or a non-profit, check Microsoft’s donation and academic programmes before you price a single commercial licence. The savings available there are larger than any negotiation on a commercial agreement will produce, and they are frequently overlooked because the buying process looks unfamiliar. The same applies to the seat threshold at which an Enterprise Agreement becomes available: the economics change again at scale, and the minimum has been revised over the years, so ask rather than assume.

Questions people ask about this