Microsoft Open Value: What It Is, When It Makes Sense, and What to Watch Out For

What Is Microsoft Open Value?

Microsoft Open Value is a volume licensing agreement designed for organisations with five or more desktop PCs or users. It bundles software licences and Software Assurance (SA) into a single three-year agreement, allowing organisations to make annual payments rather than a large upfront purchase, and providing access to SA benefits throughout the term.

Open Value occupies the middle ground in Microsoft's licensing portfolio — above the old Open License transactional model (retired in January 2022) and below the Enterprise Agreement (EA), which requires a minimum of 500 seats. For organisations that are too large for simple retail or OEM purchasing but too small for a formal EA, Open Value has historically been the standard route to volume pricing and upgrade rights.

There are two core variants. Open Value (OV) provides perpetual licence ownership at the end of the three-year term — the organisation retains the right to use the software version covered by the agreement indefinitely, even after SA expires. Open Value Subscription (OVS) is a pure subscription model: licences are held only while the agreement is active, and if the organisation does not renew, access to the software ceases. OVS typically carries a lower annual payment than OV in exchange for surrendering ownership rights.

What Software Assurance Includes in an OV Agreement

Software Assurance is the mechanism by which Microsoft bundles ongoing value into multi-year volume agreements. In an Open Value deal, SA is mandatory — it is included in the pricing rather than an optional add-on. This is worth understanding precisely because SA entitlements vary by product and are routinely under-utilised.

SA under Open Value provides access to new software version upgrades released during the SA coverage period, so an organisation that starts on Windows 11 with SA will be entitled to move to the next major Windows release at no additional licence cost. It includes access to Microsoft's eLearning and training voucher benefits, Home Use Programme rights for covered applications, and 24x7 problem resolution support for specific Microsoft products.

For organisations that actively use SA benefits, the effective value per pound or dollar of SA spend is meaningfully higher than the headline price suggests. For organisations that pay for SA and never activate entitlements, SA is pure margin for Microsoft. In our experience across 500+ licensing engagements, SA utilisation in OV agreements averages below 30 percent of available entitlements.

Open Value vs CSP vs MCA: The Honest Comparison

Microsoft's commercial strategy in 2026 is to migrate the mid-market out of Open Value and into CSP (Cloud Solution Provider) or MCA (Microsoft Customer Agreement). Understanding the commercial reality behind each programme is essential to making a rational procurement decision.

Open Value Strengths

Open Value provides perpetual licence ownership, which is a genuine differentiator for organisations that require owned software rights rather than subscription dependency. If the business relationship with Microsoft were to change, or if budget constraints forced a temporary reduction in spend, an organisation holding OV perpetual licences retains the right to run the covered software version without ongoing payments.

OV also covers on-premises workloads cleanly. For organisations running Windows Server, SQL Server, or Office deployments on their own hardware or in private data centres, OV remains one of the most straightforward mechanisms to licence on-premises products with volume pricing and SA benefits.

The annual payment structure of OV reduces cash-flow pressure compared with large upfront software purchases. Spreading cost over three annual payments, with predictable pricing locked in at agreement start, provides budget visibility that month-to-month CSP subscriptions cannot match for stable workloads.

CSP Strengths

CSP (Cloud Solution Provider) is Microsoft's preferred model for cloud-first mid-market organisations. Under CSP, organisations purchase M365, Azure, Dynamics, and other cloud services through a Microsoft-authorised partner on a monthly or annual basis. There is no minimum seat threshold, making CSP accessible for organisations below the five-seat OV floor — or organisations that need to quickly add small numbers of licences without triggering a formal agreement amendment.

CSP provides flexibility to scale up and down on a monthly basis under the NCE (New Commerce Experience) framework, though that flexibility comes at a price. NCE monthly subscriptions are billed at list price with no discount. NCE annual subscriptions carry up to 5 percent discount. For organisations that value commercial flexibility above cost optimisation, CSP is appropriate. For organisations that value cost certainty and price competitiveness, OV or EA remains the better mechanism.

MCA Strengths

The Microsoft Customer Agreement (MCA) is a simpler commercial framework that removes much of the formal EA paperwork and negotiation process. For organisations purchasing M365 and Azure services through the MCA route, the agreement is standardised, acceptance is electronic, and there is no formal negotiation window. This simplicity is exactly why Microsoft promotes MCA — buyer leverage in MCA is structurally lower than in EA or OV, because there is no formal negotiation process and Microsoft's standard commercial terms apply without modification.

The M365 Licensing Context: Where Open Value Fits in 2026

Understanding where OV sits relative to Microsoft 365 SKU tiers is essential context. Microsoft's current M365 enterprise stack runs E1, E3, E5, and E7 — with E7 as the new top-tier SKU introduced above E5. Microsoft field teams are actively steering E5 customers toward E7 at renewal, with E7 bundling advanced AI capabilities and security features that were previously sold as expensive add-ons to E5.

Open Value customers accessing M365 are typically on E1 or E3, occasionally E5. The OV programme does not provide the same negotiation leverage around E5-to-E7 migrations or Copilot add-on pricing that a well-structured EA does. If an organisation is considering M365 E5 or E7, the EA negotiation framework is the more appropriate vehicle — OV pricing for upper-tier M365 SKUs is generally not as competitive as a negotiated EA at equivalent seat counts.

Microsoft 365 Copilot, priced at $30 per user per month as a standalone add-on (or included within the E7 bundle), is another dimension where OV's commercial leverage is limited. Copilot pricing negotiation happens in the context of broader EA commercial discussions, not within OV amendment processes.

When Open Value Still Makes Sense in 2026

Despite Microsoft's push toward CSP and MCA, there are genuine scenarios where OV remains the most appropriate licensing mechanism.

Organisations requiring perpetual on-premises licences — particularly for Windows Server, SQL Server, or legacy Office versions — are best served by OV. The perpetual ownership rights and SA coverage for on-premises products are structurally superior to CSP, which has no on-premises perpetual licence provision.

Organisations between 5 and 500 seats that want predictable, locked pricing over a three-year horizon without the administrative overhead of a full EA. OV provides commercial certainty that NCE CSP monthly billing cannot match for stable, predictable workloads.

Organisations with strong on-premises infrastructure strategies that do not see a wholesale migration to Microsoft's cloud services within the three-year OV term. If significant investment in private data centre capacity or hybrid infrastructure is planned, OV's on-premises coverage makes commercial sense.

Organisations that actively use Software Assurance entitlements — particularly training benefits, deployment planning services, and home use programme access — will extract genuine value from SA inclusion that offsets the cost premium over CSP subscription pricing.

When Open Value Is the Wrong Choice

Open Value is the wrong vehicle for organisations that have already migrated substantially to M365, Azure, or Dynamics 365 cloud services. For cloud-first workloads, OV provides no pricing advantage over a well-negotiated CSP or EA agreement, and the three-year lock-in reduces flexibility to respond to licensing changes — particularly as Microsoft continues to evolve M365 SKU structures with E7 and new Copilot tiers.

Organisations approaching 500 seats should evaluate the EA route seriously. Above approximately 200 to 300 seats on M365 E3 or E5 equivalent licensing, the EA typically delivers 15 to 20 percent better pricing than OV for comparable coverage, plus access to Azure Hybrid Benefit and more substantive True-Up negotiation flexibility. OV's maximum discount leverage is structurally lower than EA because the formal negotiation engagement is less structured and Microsoft's field team incentives are oriented toward EA and MCA renewals.

Organisations that are growing rapidly and expect to cross the 500-seat threshold before the OV three-year term expires should plan migration to EA from the outset rather than entering OV and then facing an early migration. Early termination of OV agreements is commercially unfavourable, and licensing continuity during programme transitions creates complexity that is easier to avoid through upfront programme selection.

Five Traps to Avoid in Open Value

Trap 1 — Paying for SA You Don't Use: Software Assurance entitlements under OV require active management to extract value. Organisations that pay the SA premium without auditing and activating available benefits — training vouchers, E-learning, home use licences, deployment planning credits — are paying a 20 to 30 percent premium for nothing. Before signing or renewing an OV agreement, map every SA entitlement against planned usage and quantify the value. If SA utilisation is consistently below 40 percent, the commercial case for OV over a lower-cost CSP arrangement weakens substantially.

Trap 2 — Accepting the OV Renewal Without Price Comparison: Microsoft's OV renewal process is largely automated and partner-driven. Renewal pricing is rarely the best available price. Partners have incentive to renew at standard rates rather than introduce competitive pricing tension. Before any OV renewal, benchmark pricing against CSP list rates, EA indicative pricing, and competitor offers. Even a 10 to 15 percent reduction from the standard renewal rate is achievable with minimal negotiation effort if approached three to four months before renewal.

Trap 3 — Not Planning for Programme Migration: Many organisations enter OV as a practical solution for their current size and complexity, without a clear view of where the licensing relationship will be in three years. If organisational growth, cloud migration velocity, or M365 adoption patterns are likely to push the organisation toward EA or CSP during the OV term, plan for this migration from day one. Entering OV without a migration path creates contractual friction at exactly the wrong moment — when the business is trying to move quickly.

Trap 4 — Conflating OV with EA Negotiation Leverage: The Open Value agreement process is not a negotiation in the same way as an EA. OV pricing is typically set by the partner and follows standard Microsoft volume tiers, with limited room for customised commercial terms. Organisations that have grown accustomed to EA-style negotiation — where True-Up timing, Azure consumption commitments, and SKU mix all influence final pricing — will find OV a less flexible commercial environment. If commercial leverage matters, EA is the appropriate framework.

Trap 5 — Ignoring the Programme Transition Signal: Microsoft has begun selectively declining new EA contracts for smaller organisations and steering them toward CSP and MCA. This is a deliberate commercial strategy. OV remains available, but Microsoft's investment in the programme — in terms of partner training, commercial incentives, and product coverage — is diminishing relative to CSP and MCA. An organisation committing to a new three-year OV agreement in 2026 should do so with eyes open to the programme trajectory.

Key Recommendations

Audit SA entitlements before renewal: Document every SA benefit available under your OV agreement, map against planned usage, and quantify the value. This exercise alone typically reveals either strong justification for OV renewal or a compelling case to move to CSP.

Benchmark renewal pricing externally: Do not accept partner renewal pricing without an independent market comparison. CSP equivalent pricing and EA indicative pricing provide meaningful benchmarks that should be applied to any OV renewal conversation.

Map your organisation's three-year trajectory: If growth, cloud migration, or M365 expansion is planned, model the licensing programme implications of reaching 300, 500, or 750 seats over the OV term. Avoid being locked into OV when EA or a structured MCA would be commercially superior at scale.

Engage independent Microsoft EA advisory specialists: Programme selection between OV, CSP, MCA, and EA is a strategic decision that affects commercial terms, flexibility, SA value, and negotiation leverage for the following three to five years. Independent advisory, free from partner or vendor incentives, provides the objective analysis that in-house teams and Microsoft-aligned partners cannot.