Microsoft licensing · Module 2

Which Microsoft agreement fits
which software?

Not every Microsoft product can be purchased through every agreement. Whether Microsoft 365, Azure, Copilot, or Windows Server is available depends on the exact product variant and purchasing route.

Updated: 15 August 2026Reading time: about 7 minutesProducts & purchasing routes

In brief

The product name alone does not tell you how it can be purchased.

What matters is the exact product variant, the appropriate agreement, and whether the purchase is direct or through a partner.

01Which product is required?
02Which exact product variant is involved?
03Which agreement is suitable?
04Is it bought directly or through a partner?

Explained simply · The essential terms

Three questions before purchasing software

Knowing which Microsoft product you need is not enough. The agreement, purchasing route, and exact product variant must also match.

Agreement

The legal framework under which an organisation acquires Microsoft products.

Purchasing route

How the purchase is made: directly from Microsoft or through a partner.

SKU

The exact product variant available to order, such as a specific Microsoft 365 plan.

A practical example: An organisation needs Microsoft 365 and Windows Server. Whether both products are available through the same agreement must be checked for each exact product variant.

Read availability correctly

Product name plus programme is not enough.
The exact SKU decides.

Two organisations can use the same product while sourcing it through different programmes, terms, or licence forms. The matrix is therefore guidance—not a promise that every variant can be ordered in every country or channel.

01 · Four checks

Four details determine the actual purchasing route

A defensible mapping starts with the exact offer, not just the familiar product name.

PRODUCT FAMILY

What will be used?

For example Microsoft 365, Azure, Copilot Studio, Windows Server, or SQL Server.

SKU / OFFER

Which exact variant?

Suite, edition, add-on, user type, core pack, subscription, or perpetual licence may follow different routes.

PROGRAMME

Which commercial logic?

EA/EAS, MCA, MPSA, or Open Value define framework, commitment, and ordering process.

CHANNEL & MARKET

Who sells—and where?

Microsoft direct or a CSP partner, country, currency, and customer segment affect the available catalogue.

02 · Product-to-agreement matrix

The main product groups at a glance

The matrix reflects the current Microsoft Product Terms at programme level. MCA is the legal foundation; the actual catalogue can differ between direct and CSP procurement.

Listed for the programmeSelected / special model onlyNot currently listed

Product family	EA / EAS	MCA direct / CSP	MPSA	OV / OVS	Important context
Microsoft 365 / Office 365	Listed for the programme	Listed for the programme	Selected / special model only	Selected / special model only	MPSA and OV/OVS list selected offers only—not every suite by default.
Microsoft 365 Copilot	Listed for the programme	Listed for the programme	Not currently listed	Not currently listed	Not listed as a standalone offer in the current MPSA or OV/OVS availability tables.
Power Platform / Copilot Studio	Listed for the programme	Listed for the programme	Listed for the programme	Selected / special model only	MPSA lists Copilot Studio among other offers; OV/OVS currently lists Power BI Pro only.
Microsoft Azure Services	Listed for the programme	Listed for the programme	Not currently listed	Selected / special model only	Explicitly unavailable under MPSA; OV/OVS uses a separate value-based subscription model.
Windows Server	Listed for the programme	Listed for the programme	Listed for the programme	Listed for the programme	Check edition, core pack, CALs, subscription or perpetual form, and Software Assurance separately.
SQL Server	Listed for the programme	Listed for the programme	Listed for the programme	Listed for the programme	Server/CAL and core models are not equally available for every edition; SA affects important rights.
Office LTSC / desktop applications	Listed for the programme	Listed for the programme	Listed for the programme	Listed for the programme	Perpetual, device-based software—not the same as per-user Microsoft 365 Apps.
Dynamics 365 cloud	Listed for the programme	Listed for the programme	Listed for the programme	Not currently listed	The app, user type, add-on, capacity, and geography determine the exact offer.

✓ does not mean every edition or SKU is available. ◐ deliberately marks restricted, selected, or programme-specific offers. Check the price list, Product Terms, region, and actual quotation before ordering.

03 · Product families

Cloud, Azure, and server products follow different procurement logic

The biggest differences do not sit in the product logo, but in licence form, billing, and included rights.

CLOUD PER USER

Microsoft 365 & Copilot

EA/EAS and MCA are the broad main routes. Under MCA, customers may buy direct from Microsoft or through CSP. MPSA and Open Value list selected Microsoft 365 offers only; Microsoft 365 Copilot is not currently listed there as a standalone offer.

Per-user subscription
Check suite and add-on separately
CSP for partner-led operations

PLATFORM & AGENTS

Power Platform & Copilot Studio

Power Apps, Power Automate, Power BI, and Copilot Studio are listed under EA/EAS, MCA, and MPSA. In this product family, Open Value currently lists Power BI Pro only—not the full Power Platform catalogue.

Account for capacity and add-ons
Copilot Studio listed under MPSA
Open Value is much narrower

CONSUMPTION

Microsoft Azure

EA/EAS and MCA are the central routes for Azure consumption. CSP adds partner billing and services. MPSA explicitly excludes Azure. OV/OVS has a separate value-based Azure subscription that should not be equated with modern pay-as-you-go.

Consumption rather than seats
Assess commitments separately
Clarify billing scope and partner role

ON-PREMISES

Windows Server, SQL Server & Office LTSC

This software is available through several programmes. The decisive details are perpetual or subscription form, edition, licence metric, CALs, and Software Assurance or equivalent subscription rights.

Separate perpetual and subscription
Check SA and mobility rights
Document product version and edition

04 · Under the MCA

Direct procurement and CSP use the same agreement family—but not the same process

The channel affects quotation, invoice, provisioning, support, and available services.

MCA DIRECT

Microsoft as the seller

The customer works with Microsoft sales or uses a supported online purchase. Microsoft manages the billing relationship and issues the invoice.

Direct commercial relationship
Azure and online services
Offer and market dependent

MCA + CSP

Partner as procurement and service channel

The customer accepts the MCA while the CSP partner manages quotation, invoice, provisioning, and agreed services. CSP can offer online services, Azure, software subscriptions, and perpetual software.

Partner invoice and support
Seat, Azure, and software
Partner catalogue can vary

Current distinction since 1 April 2026

According to Microsoft, Windows Server and SQL Server subscriptions in CSP under the MCA include certain License Mobility rights equivalent to the corresponding SA rights in legacy volume programmes. CSP perpetual licences remain unchanged and do not receive those mobility rights.

05 · Common assumptions

The same product name does not automatically mean the same offer

Microsoft 365 is not one SKU

Business, Enterprise, Frontline, security add-ons, and Copilot have their own availability and prerequisites.

MCA does not automatically mean CSP

MCA is the agreement foundation. CSP is the partner channel; an MCA can also exist in a direct Microsoft scenario.

Azure is not identical everywhere

MCA consumption, CSP Azure, EA commitment, and the value-based OV/OVS model differ in billing and term.

Subscription does not universally replace SA

Product- and programme-specific Product Terms define which SA-equivalent rights apply.

06 · Before ordering

Seven checks prevent the most common purchasing mistakes

The offer name on a price line is not enough for a defensible decision.

01Record the exact SKU, edition, and user or core metric
02Identify the programme and enrollment or Purchasing Account
03Document direct, CSP, or another partner channel
04Check country, customer segment, and current price-list availability
05Separate subscription, perpetual rights, and renewal logic
06Check Software Assurance, mobility, Hybrid Benefit, and upgrade rights
07Archive Product Terms, order, and partner quotation together

Key principle

The product name does not determine the route—the exact SKU in the exact programme does.

Start with the required usage right. Then check programme, channel, term, included benefits, and the current offer catalogue.

Primary and official sources

Current, verified, and traceable.

The mapping is based on official Microsoft Product Terms and Microsoft Learn information available on 15 August 2026. Catalogues change; individual offers may vary by country, channel, customer segment, and order date.

Note: The matrix provides professional orientation, not ordering or legal advice. The Product Terms, price lists, agreement documents, and specific quotation valid at the time of order remain authoritative.