Editorial photograph of a Microsoft enterprise licensing review with M365, Copilot, and Azure pricing options on the boardroom screen
Guide · Microsoft · Licensing

Microsoft licensing in 2026. The complete guide.

Every Microsoft contract vehicle, every M365 SKU, every Copilot price, and the Azure consumption commitment math. Written for CIOs, CFOs, and procurement leaders running an active Microsoft decision.

Read the Article Microsoft Services
4Contract vehicles
30+Active SKUs
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent
Key Takeaways

What this guide delivers

  • Four contract vehicles. EA, MCA, CSP, MPSA each serve different enterprise sizes and footprints.
  • Microsoft 365 is the lead estate. E3, E5, F1, F3, Business Standard, Business Premium map across workforce segments.
  • Copilot is now strategic. 30 USD per user per month enterprise SKU drives EA value in 2026.
  • MACC drives Azure economics. Multi year Azure commitment unlocks discount bands tied to consumption.
  • Power Platform prices separately. Citizen developer sprawl is the unmanaged cost line.
  • Dynamics 365 prices per app. Sales, Customer Service, Field Service, Finance, Supply Chain each price separately.
  • Median 22 percent recovery. Buyer side renewals that run vehicle selection plus SKU discipline plus MACC math.

Microsoft licensing is the largest software estate most enterprises run. The 2026 portfolio spans four contract vehicles, thirty plus active SKUs, the Copilot family, the Azure consumption commitment, and the Power Platform plus Dynamics 365 product lines.

The buyer side that maps every vehicle, every SKU, and every consumption commitment against documented business need takes the discount band the EA renewal would otherwise concede.

Contract vehicles

Microsoft sells through four primary contract vehicles. Each carries different commercial terms, different discount bands, and different True Up mechanics. The vehicle selection drives the next three years of cost trajectory.

Enterprise Agreement (EA)

The traditional three year subscription for organizations of 2,400 plus users. Annual True Up. Multi year price lock. Negotiated discount overlay. Remains the right vehicle for complex multi product enterprises with stable user populations.

Microsoft Customer Agreement (MCA)

The cloud first agreement Microsoft is steering customers toward. Pay as you go or commitment based. Direct billing or partner billing through a Cloud Solution Provider. Suitable for cloud native organizations or those with simplified Microsoft footprints.

Cloud Solution Provider (CSP)

The partner channel for Microsoft cloud services. The partner bills the customer, manages the subscription, and provides Tier 1 support. CSP discounts pass through partly to the customer and partly to the partner margin.

Microsoft Products and Services Agreement (MPSA)

The transactional agreement for organizations that buy intermittently. Suitable for small or mid market organizations that do not justify an EA commitment. Largely superseded by the MCA for cloud and the CSP for partner driven sales.

VehicleBest forTermTrue Up
Enterprise Agreement2,400 plus users, multi product3 yearsAnnual
Microsoft Customer AgreementCloud first, direct or partner billed1 to 3 yearsMonthly or annual
Cloud Solution ProviderPartner relationship strategic1 year typicalMonthly
Microsoft Products and Services AgreementTransactional buying, small or mid market1 to 3 yearsNone

Microsoft 365 SKU map

Microsoft 365 is the largest license line in most enterprises. The portfolio spans information worker SKUs, frontline SKUs, security and compliance add ons, and the Copilot family. Mapping the right SKU to the right user segment is the first cost lever.

Microsoft 365 E3

The productivity baseline for information workers. Office apps, Exchange Online, SharePoint, Teams, OneDrive, Windows 11 Enterprise, and core security. The default SKU for the majority of enterprise users.

Microsoft 365 E5

E3 plus Microsoft Defender (XDR), Purview compliance, Power BI Pro, and Teams Phone. Typically prices at roughly 56 USD per user per month versus 36 USD for E3. Worth the premium when the security plus compliance plus BI workload justifies it.

Microsoft 365 F1 and F3

The frontline worker SKUs. F1 is a license only SKU for shared device scenarios. F3 includes Office Online, Exchange Online, Teams, and a subset of M365 productivity. Suitable for retail, manufacturing, healthcare, and field workforces.

Business Standard and Premium

The small and mid market SKUs capped at 300 users. Business Standard is broadly E3 equivalent at a lower price. Business Premium adds Entra ID P1, Defender for Business, and Intune. Not available above 300 users.

Procurement and IT teams reviewing the Microsoft 365 SKU mix across information workers, frontline, and Copilot adoption
The M365 SKU mix is the first cost lever. Most enterprises overbuy E5 and underuse F3 across their workforce segments.

Copilot family

Microsoft Copilot is a family of SKUs covering productivity, sales, service, and custom agents. Each SKU carries a different price point, a different prerequisite, and a different commercial model. The 2026 EA cycle confirms Copilot as the strategic line.

Microsoft 365 Copilot

The core enterprise SKU at 30 USD per user per month. Requires a qualifying M365 base license. Covers Copilot for Word, Excel, PowerPoint, Outlook, Teams, and OneNote plus Business Chat. The largest Copilot adoption line for most enterprises.

Copilot for Sales and Service

The role specific SKUs integrating with Dynamics 365 or Salesforce. Pricing runs at 50 USD per user per month standalone or 20 USD as an add on to M365 Copilot. Suitable for revenue facing teams.

Copilot Studio

The custom agent platform priced on a message based consumption model. Base 200 USD per month for 25,000 messages with additional pools at the same rate. Agent sprawl is the largest hidden cost risk.

Copilot Pro

The individual professional SKU at 20 USD per user per month. Aimed at individual users without a Microsoft 365 enterprise license. Not the SKU enterprise customers should be buying for their workforce.

Azure and the MACC

Azure runs on a consumption model. The Microsoft Azure Consumption Commitment (MACC) is the buyer side discount lever. The MACC commits the enterprise to a minimum Azure spend over a multi year term in exchange for a discount band on consumption.

MACC commit math

The MACC commit value drives the discount band. The customer commits to a minimum Azure spend over the term. Under consumption forfeits the unused commit. Over consumption pays at the same discount rate until the next reservation tier.

Reservations and savings plans

Azure Reservations lock pricing on specific VM or database SKUs for one or three years. Savings Plans lock pricing on compute consumption flexibly across SKUs. Both consume MACC and stack with the MACC discount band.

EA billed versus MCA billed MACC

The MACC can sit inside the EA invoice flow or under a separate MCA billed by a Cloud Solution Provider. The choice drives invoice consolidation, partner economics, and Tier 1 support. Both options are credible at scale.

  • Match commit to forecast. Over commit wastes spend. Under commit loses the discount.
  • Reserve the steady state. Three year reservations on production workloads compound MACC savings.
  • Leave headroom for growth. Pay as you go consumption above reservations absorbs unplanned scale.
  • Review the portfolio quarterly. Azure consumption shifts faster than the EA cycle.

Power Platform and Dynamics

Power Platform and Dynamics 365 sit outside the M365 base. Each prices separately on per user or per app models. The license sprawl risk is highest in Power Platform where citizen developer adoption can drive uncontrolled cost.

Power BI

Power BI Pro is included in M365 E5. Power BI Premium adds dedicated capacity and large model support. Premium Per User combines Pro plus Premium features. The right SKU depends on the workload size and user count.

Power Apps and Power Automate

Power Apps prices per app or per user. Power Automate prices per user or per flow. Citizen developer governance is the buyer side discipline that prevents license sprawl across the platform.

Dynamics 365 modules

Dynamics 365 Sales, Customer Service, Field Service, Finance, and Supply Chain Management each price separately. Per user pricing typical. Module bundles available through D365 Enterprise plans. The buyer side prices each module against documented adoption.

Power Platform governance

Environments, data loss prevention policies, and Center of Excellence tooling control citizen developer sprawl. Without governance the per app or per user lines grow uncontrolled and concede MACC like discipline in reverse.

Buyer side moves

Five buyer side moves drive the median 22 percent recovery on a consolidated Microsoft renewal. The buyer side that runs all five captures the band. Skipping any one move concedes a meaningful share of the recovery.

Move one. Pick the right vehicle

EA, MCA, CSP, or MPSA. The vehicle selection drives the next three years of pricing. Most enterprises default to the EA without testing whether the MCA plus CSP combination would deliver better economics.

Move two. Right size the M365 SKU mix

Map E3, E5, F1, F3, Business Standard, and Business Premium across the workforce segments. Most enterprises overbuy E5 for users who would be content on E3 and underuse F3 across frontline populations.

Move three. Price Copilot first

Copilot is the lead variable in the 2026 EA cycle. Pricing Copilot before the M365 base discloses the bundle math early and forces Microsoft to commit to the Copilot discount band on its own terms.

Move four. Engineer the MACC

The MACC commit value, the reservation portfolio, and the partner channel decision drive Azure economics over the term. The buyer side that models all three together captures both the MACC discount and the reservation discount on the same workload.

Move five. Govern Power Platform

Environment governance, data loss prevention policies, and a Center of Excellence prevent citizen developer license sprawl. Without governance Power Platform grows uncontrolled and erodes the discipline applied elsewhere.

  1. Vehicle selection. Test EA versus MCA plus CSP comparison.
  2. M365 SKU mix. E3, E5, F1, F3 mapped to workforce segments.
  3. Copilot scope first. Price Copilot before the M365 base.
  4. MACC engineering. Commit, reservations, partner channel together.
  5. Power Platform governance. Environments, DLP, Center of Excellence.

What to do next

The checklist takes the procurement function from a Microsoft license review into a contained renewal motion. The earlier the work starts, the wider the option set on the day Microsoft puts the proposal on the table.

  1. Document the contract end date. Calendar twelve months out from EA expiry.
  2. Inventory the user estate. Active users, SKU mix, frontline counts, Copilot eligibility.
  3. Inventory the Azure footprint. Subscriptions, monthly consumption, reservation portfolio, MACC commit.
  4. Inventory Power Platform and Dynamics. Apps, flows, environments, per user licenses, module licenses.
  5. Test the vehicle selection. EA versus MCA plus CSP economics side by side.
  6. Right size the M365 SKU mix. Strip overbought E5, deploy F3 to frontline populations.
  7. Define the Copilot scope. Multi year commitment band on pilot adoption math.
  8. Engage Vendor Shield. Independent buyer side review before Microsoft engagement opens.

Frequently asked questions

What are the four main Microsoft contract vehicles?

Enterprise Agreement (EA) for 2,400 plus users. Microsoft Customer Agreement (MCA) for direct cloud spend. Cloud Solution Provider (CSP) via partners. Microsoft Products and Services Agreement (MPSA) for transactional buys.

What is the difference between M365 E3 and E5?

Microsoft 365 E3 is the productivity baseline. M365 E5 adds advanced security (Defender), advanced compliance (Purview), Power BI Pro, and Phone System. E5 typically prices at roughly 56 percent more than E3.

How does Copilot pricing work in 2026?

Microsoft 365 Copilot is 30 USD per user per month enterprise. Copilot for Sales and Service price separately. Copilot Studio sells on a message based consumption model with prepurchased pools.

What is the Microsoft Azure Consumption Commitment?

MACC is a multi year Azure spend commitment that unlocks discount bands. Can be billed inside the EA or directly via the MCA through a CSP partner. Drives reservation and savings plan strategy.

Does Power Platform require separate licensing?

Power BI Pro is included in M365 E5. Power BI Premium, Power Apps, Power Automate, and Power Pages all price separately on per user or per app models. Citizen developer governance matters here.

What is the typical Microsoft enterprise discount band?

Level B (2,400 to 5,999 users) typically sees 8 to 12 percent overlay. Level C (6,000 to 14,999) sees 12 to 18 percent. Level D (15,000 plus) sees 18 to 25 percent. Negotiated overlays vary by Azure and Copilot commitment.

Should we move to the Microsoft Customer Agreement?

The MCA is the cloud first agreement Microsoft is steering customers toward. Suitable when the enterprise wants direct billing or runs a single tenant cloud footprint. The EA remains better for complex multi product enterprises.

How does Redress engage on Microsoft licensing?

Redress runs Microsoft licensing decisions inside Vendor Shield, the Renewal Program, and the Software Spend Assessment. The work covers EA, MCA, CSP, M365, Copilot, Azure, Power Platform, and Dynamics 365.

How Redress engages

Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, and the Software Spend Assessment.

Read the related Microsoft EA renewals article, the Microsoft Copilot licensing 2026 article, the Microsoft services, the Microsoft knowledge hub, the benchmarking service, and the Benchmark Program.

Right size your Microsoft estate with the Microsoft 365 license optimizer.
Open the Optimizer →
White Paper · Microsoft

Download the Microsoft EA Renewal Playbook.

Microsoft Enterprise Agreement renewal motion, true up exposure, Copilot bundling, and the buyer side discount band moves.

Independent. Written for CIOs, CFOs, and procurement leaders. No vendor partner affiliation.

Microsoft EA Renewal Playbook

Open the playbook in your browser. Corporate email only.

Open the Paper →
4
Contract vehicles
30+
Active SKUs
3yr
EA term standard
$30
Copilot per user
22%
Median recovery

Microsoft licensing is not complicated by accident. The customer that maps every vehicle, every SKU, and every consumption commitment against business need takes the discount band Microsoft would otherwise keep.

Buyer side Microsoft reviewer
Enterprise licensing decisions
More Reading

More from this practice.

Vendor Knowledge →
Microsoft EA Renewal Playbook
Microsoft · White Paper
Microsoft EA Renewal Playbook
EA renewal motion and Copilot bundle.
14 min read
Copilot Licensing 2026
Microsoft · Article
Microsoft Copilot Licensing 2026
Copilot SKUs and EA bundling.
12 min read
Microsoft Knowledge Hub
Microsoft · Hub
Microsoft Knowledge Hub
All Microsoft research, in one place.
5 min read
Vendor Shield
Program · Subscription
Vendor Shield
Always on advisory across publishers.
7 min read
Editorial photograph of a Microsoft enterprise licensing review session covering EA, MCA, CSP, and Copilot

Master the vehicles. Hold the band.

We run Microsoft licensing decisions across EA, MCA, CSP, and the partner channel. Median 22 percent recovery on consolidated renewals through vehicle selection, SKU discipline, and Azure commit math.

Buyer side intelligence, monthly.

Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active vendor decisions.