Microsoft Contracts: Comparing Types, Channels, and Conditions to Understand the Impact on Costs and Licensing

For a better understanding of how Microsoft structures its commercial offering

In this article, we analyze the main types of Microsoft contracts, clearly explaining how they work and how different conditions can affect costs and license management, making it easier to evaluate their impact on budget and business operations. For the same license, the price can vary by as much as 40% between companies.

Let’s take Microsoft 365 E3, with a public list price of around €35/user/month: it can cost €29 or €40, and for 1,000 users the difference exceeds €130,000 per year—without the product changing by a single comma.

We’re not talking about “mysterious” discounts or pricing errors: the variability lies entirely in Microsoft’s contractual structure. An element often invisible to those who look only at the sticker price, but which creates conditions that can impact the budget, operational flexibility, license management, and compliance.

The principle is simple: what you pay and under what conditions (how, when, and under which rules you can use and modify the licenses) depends on the type of agreement you sign and the level of commitment you accept.

The Microsoft Enterprise Agreement (EA) has historically been one of the most widely used Microsoft licensing contracts by large organizations with at least 500 or more users/devices, as it allows licensing of Microsoft cloud services and/or on-premises software over a three-year period, with centralized license management and volume-based discounts.

Starting in January 2025, as announced in the November 12 blog post by Nicole Dezen, Chief Partner Officer and Corporate Vice President, Global Partner Solutions, some Enterprise Agreement (EA) contracts for the direct cloud market will no longer be renewable under the current EA framework. Microsoft will begin notifying affected customers—according to the blog, “a small percentage”—that EA renewal will no longer be possible at the beginning of the year.

In place of the EA, Microsoft will propose to these customers the Microsoft Customer Agreement for enterprise (MCA-E), the digital evolution of the traditional EA. For SMC customers (for Microsoft, these are companies with fewer than 3,000 users), the recommended options will be the Cloud Solution Provider (CSP) Program (for those seeking a services and support experience via a partner), or the MCA-E (for those preferring a direct purchasing relationship or a per-user purchase model).

This decision by Microsoft aims to strengthen its partner ecosystem in the small and medium customer (SMC) segment, which, as a reminder, includes companies with fewer than 3,000 users. Still in the blog post, Nicole Dezen highlights the company’s commitment to supporting the needs of this segment, allocating 70% of total incentives to partners serving it.

The market appears highly profitable: according to IDC data from October 2024, the Total Addressable Market (TAM) for SMCs in FY25 will be $661 billion (of which $467 billion in cloud solutions), with an annual growth rate of 15% (20% for cloud) over the next 4 years.

With an Enterprise Agreement (EA), typical of large organizations, you sign a three-year contract and maintain a minimum number of licenses, receiving in return double-digit discounts compared to the list price. On the other hand, with monthly purchases through a Cloud Solution Provider (CSP), you have maximum flexibility—licenses can be added or removed almost in real time—but at a higher cost that can exceed 30%. There are also differences when it comes to compliance: in the EA, conditions are more structured, with formal audits and periodic reporting, offering greater stability and traceability in case of reviews. In the CSP model, management is leaner and decentralized, but requires constant attention to avoid non-compliant usage, since the increased flexibility reduces the degree of “automatic control” provided by the contract.

Committed vs Transactional and License Volume: Why They Matter

After seeing how contract type can affect license price by up to 40%, the next step is to understand two variables Microsoft uses to segment customers: commitment level (committed vs transactional) and license volume.

Microsoft, in fact, does not sell licenses in the same way to everyone. 

  • Enterprise (500+ users): access to contracts like EA or MCA-E, with volume discounts*, Software Assurance, and multi-year payment plans.
  • Corporate (50–500 users): typically contracts like MCA or MPSA, with fewer structured benefits but more flexibility.
  • SMB (<50 users): direct channels or the old Open model (being phased out), without access to enterprise discount logics.

 

Here the commitment level variable comes into play:

  • Committed: you commit for 12 or 36 months to maintain a minimum number of licenses, obtaining significant discounts and extra benefits.
  • Transactional: you pay month-to-month with no minimum constraints, with maximum flexibility to increase or decrease licenses in real time but at a higher price and with fewer benefits.

 

The accessibility matrix thus defines not only which contracts you can sign based on company size but also whether you can access more advantageous “committed” rates or if a “transactional” approach is more appropriate. Some benefits—like volume discounts, Software Assurance, or three-year payment plans—remain Enterprise-only.

Important Update – August 2025 Microsoft announced that from November 1, 2025, it will eliminate Price Level discounts for online services in Enterprise Agreement (EA) and Microsoft Products and Services Agreement (MPSA) contracts. This means prices for levels B, C, and D will be aligned with level A (public price). We discussed this in a dedicated article. [insert link to new article]

A Quick Overview of Microsoft Contracts for Enterprise

Contracts typically for Enterprise companies, i.e., with a minimum of 500 users, include:  

  • Microsoft Enterprise Agreement (EA)  
    Il Microsoft Enterprise Agreement (EA) è il contratto tradizionale pensato per le grandi organizzazioni, strutturato per garantire prezzi più bassi in cambio di impegni rigidi. È un accordotriennale commitment-based: l’azienda si impegna a mantenere un numero minimo di licenze per tutta la durata — almeno 500 utenti o dispositivi per le realtà commerciali, 250 per quelle governative — e in cambio ottiene sconti significativi rispetto al listino. Ricordiamo però che dal 1° novembre 2025, Microsoft eliminerà i Price Level discounts per i servizi online acquistati tramite EA (e MPSA) quindi la situazione cambierà.

    L’EA è pensato per chi ha una base utenti stabile e vuole una copertura completa, sia per il cloud sia per il software on-premises, con incluso Software Assurance (attenzione però che Microsoft ha ritirato le offerte From SA per Microsoft 365 e Dynamics 365 dal 1 aprile 2024: si possono rinnovare, ma non estendere/aggiungere).  

    Il rovescio della medaglia? Durante l’anno si possono aumentare le licenze, non ridurle: la flessibilità è limitata, ma la prevedibilità dei costi e i vantaggi economici lo rendono ancora oggi la scelta preferita di molte enterprise. 
    Una variante più recente è il Microsoft Enterprise Agreement Subscription (EAS), che mantiene la stessa logica di impegno triennale dell’EA ma con un modello in abbonamento: i costi sono inferiori rispetto all’EA tradizionale ma alla fine del contratto le licenze non restano di proprietà dell’azienda. 
     

  • Microsoft Customer Agreement – Enterprise (MCA-E) The Microsoft Customer Agreement – Enterprise (MCA-E) is the cloud-first contract designed for large organizations (500+ users/devices) that want to purchase Microsoft services without the rigidity of the traditional Enterprise Agreement. More flexible in management and billing, it allows purchases both directly and via partners, with modern billing cycles and native integration with Azure.

 

From January 2025, Microsoft will start not renewing some direct cloud EA contracts (we also discussed this here), encouraging interested customers to migrate to the Microsoft Customer Agreement – Enterprise (MCA-E), the more modern “cloud-first” version of EA.

However, the transition is not always advantageous: EA offered structured volume discounts and price protection on Azure for three years—benefits that may be lost with MCA-E, leaving room for more volatile pricing and case-by-case negotiations, also influenced by currency exchange rates. Moreover, MCA-E is an evergreen contract, without fixed expiration dates: fewer formal opportunities to review conditions and prices, with the risk of dragging a suboptimal model for years.

With the removal of Price Level discounts for online services from November 1, 2025, the direction is clear: Microsoft is reducing the historical advantages of EA and pushing more customers toward MCA-E and CSP, models where discount leverage is lower and prices are increasingly aligned to public list prices.

Deep Dive into EA Contract Structure

At least regarding “enterprise-only” benefits—and the constraints that come with them—it is essential to correctly read and interpret the structure of Enterprise Agreement (EA) contracts. Many elements impacting budget, flexibility, and compliance are hidden in clauses and documents composing the agreement: from volume discounts and price protection to restrictions on license reduction and true-up rules. For this reason, here is a quick deep dive into the EA structure and its component documents to understand where key conditions hide and how they interrelate.

The legal foundation of an EA is the Microsoft Business & Services Agreement (MBSA), an “evergreen” document that sets general business terms with Microsoft, from privacy management to audit procedures, without specific purchase obligations.

Under the MBSA umbrella sits the Enterprise Agreement, defining specific terms and conditions: duration, license transferability, product use, inclusion of Software Assurance, and rules for mergers or acquisitions.

However, the EA alone is not enough to purchase licenses: at least one Enrollment is required, the operational contract that defines what is purchased. Two main types are available:

  1. Enterprise Enrollment (EE): for user-side licenses (e.g., Microsoft 365, Office, Windows). Includes organization-wide subscription obligations for one or more base products, dedicated pricing, payment conditions, and an annual true-up mechanism to adjust to actual growth.
  2. Server & Cloud Enrollment (SCE): for server infrastructure and cloud services (e.g., Windows Server, SQL, Azure). It also requires commitment to a base installation, while providing volume discounts and flexible conditions for cloud migration.

 

In summary: EA is a multi-level structure where MBSA defines general rules, EA adds specific conditions, and Enrollments determine the products actually purchased and govern operational modes. Knowing this well is key not to miss opportunities and economic benefits.

A Quick Overview of Other Microsoft Contracts

In the corporate segment (50–500 users), the most common contracts are the Microsoft Customer Agreement (MCA), which has no minimum user constraints, and the Microsoft Products and Services Agreement (MPSA), available for organizations with at least 250 users/devices.

  • Microsoft Customer Agreement (MCA): similar to MCA-E but without enterprise requirements, it is a transactional contract suited for self-service buyers or those wanting to entrust cloud service management to a Cloud Solution Provider (CSP) partner.
  • Microsoft Products and Services Agreement (MPSA): a transactional contract for on-demand purchase of on-premises and cloud licenses as needed within a single agreement without expiration, no minimum commitment, and optional Software Assurance. It is the evolution of the old Select program.

For SMEs (typically under 50 users), the historically most common models were Microsoft Open—now being phased out—and the direct channel.

The Open License, although simple and familiar to many resellers, is gradually disappearing from official options: Microsoft is pushing for more modern models like Open Value or purchases via CSP. The direct channel is mainly used by micro-businesses or those wanting immediate Microsoft relationships but does not offer volume discounts or deferred payment conditions.

The Role of Channels  

When talking about Microsoft contracts, attention almost always focuses on the type of agreement—EA, MCA, MPSA—and their conditions.

However, an equally important, often overlooked variable is the purchase channel. Even with the same contract, the final price can vary significantly depending on who sells you the licenses and how many intermediaries exist between you and Microsoft.

An example is the Cloud Solution Provider (CSP) program: it allows buying monthly or annual licenses through Microsoft CSP partners, with billing modes defining whether the agreement is committed or transactional. The partner acts as an intermediary in license management and can offer additional services (support, migrations, training). This model guarantees maximum operational flexibility but often at higher prices than an Enterprise Agreement.

The reason is simple: every link in the commercial chain—from Microsoft (direct) to Licensing Solution Provider (LSP), CSP partners offering extra services, down to distributors and local resellers—applies its own margins and adds services that inevitably reflect on the final price. 

Take a three-year EA for Microsoft 365 E3 with 1,000 users: if you sign it directly with Microsoft, you might get a discounted list price (e.g., €33 per user/month). Passing through an LSP, the cost rises 3-5% to cover margins and extra services. If you rely on a local reseller who buys from an LSP or distributor, two margin layers can make you pay 10-15% more.

The Impact of Contractual Conditions 

Every Microsoft contractual choice—from agreement type to purchase channel, through commitment level and management methods—has concrete effects on four key areas: ha effetti concreti su quattro aree chiave: 

  • Costi – Ci sono diversi elementi che incidono in modo significativo sulla spesa annuale: sconti di volume legati alla tipologia di contratto, meccanismi di protezione prezzi, margini applicati dai partner lungo la catena di distribuzione e persino oscillazioni del cambio valuta. Questi fattori, combinati, possono far variare il budget complessivo anche di decine di migliaia di euro all’anno. Per questo è fondamentale avere una piena comprensione non solo della tipologia di contratto sottoscritta, ma anche di tutte le condizioni economiche e operative che lo accompagnano.

     

  • Flessibilità operativa – Strutture contrattuali articolate, come l’Enterprise Agreement con i suoi livelli ed enrollment, consentono di modellare la copertura in base alle esigenze aziendali, combinando cloud e on-premises e prevedendo scenari complessi come acquisizioni o espansioni internazionali. Questa flessibilità, però, richiede una pianificazione strategica per sfruttarne appieno i benefici, e lo stesso vale per qualsiasi contratto commitment-based. I modelli transactional, invece, permettono di scalare licenze quasi in tempo reale, gestendo con facilità picchi temporanei o nuovi progetti, ma a fronte di costi più elevati.

    Le condizioni contrattuali possono inoltre influire su aspetti pratici legati alla flessibilità operativa come la possibilità di aggiungere o rimuovere licenze in corso d’anno, gestire picchi temporanei di utilizzo, estendere rapidamente la copertura a nuove sedi o società acquisite, effettuare switchingtra SKU in base alle esigenze, favorire la migrazione graduale verso il cloud, o applicare downgrade. This,upgrade senza dover attendere la fine del contratto. Questi margini di manovra variano molto a seconda della struttura dell’accordo e possono fare la differenza tra un licensing agile e uno vincolante. 
     

  • Optimization: Contractual conditions can open (or close) important maneuvering spaces. Depending on agreement type (enterprise-only or not) and its clauses, you can access opportunities for rightsizing (true-up and license redistribution based on actual use), consolidation options among products, tenants, or affiliates to exploit economies of scale, license mobility options to move workloads between on-premises and cloud without extra costs, and advanced usage insights to identify unused or underutilized licenses for better renewal conditions.
  • Compliance – La tipologia di contratto influisce direttamente su come viene gestita la conformità, pur restando sempre responsabilità dell’azienda verificarla. Accordi strutturati come l’Enterprise Agreement prevedono audit periodici, rendicontazioni formali, clausole stringenti sugli audit e, in alcuni casi, grace period per correggere eventuali non conformità. Offrono processi di reporting e monitoraggio più centralizzati, che impongono una gestione ordinata e documentata.

    Modelli più snelli e decentralizzati come il CSP — soprattutto in modalità transactional — privilegiano flessibilità e rapidità operativa, ma richiedono controlli interni più rigorosi, una gestione autonoma del reporting e un monitoraggio continuo, poiché l’assenza di scadenze e audit programmati porta a individuare eventuali problemi solo a posteriori.  

In altre parole, scegliere il contratto più indicato significa bilanciare costi, flessibilità, possibilità di ottimizzazione e requisiti di compliance in base al proprio profilo aziendale e ai piani di crescita. 

At WEGG siamo consulenti esperti di licensing Microsoft, con una conoscenza approfondita delle condizioni contrattuali e delle diverse tipologie di accordo. Possiamo supportarti nella valutazione e nella scelta del modello più adatto per la gestione delle licenze, delle relative ottimizzazioni e nella negoziazione dei rinnovi. 

02-s pattern02

Hai bisogno di supporto relativamente alla comprensione dei contratti Microsoft? 

Contact us at [email protected] for a consultation!