Pricing and offers for Office 365, Dynamics CRM, Enterprise Mobility Suite, Azure, and more

Appropriate roles: User management admin | Admin agent | Microsoft AI Cloud Partner Program partner admin | Sales agent | Billing admin

To see the latest Cloud Solution Provider (CSP) programs and offers, from the Partner Center, go to the Pricing workspace.

Partners use the pricing workspace to get price lists for all products and services available to CSPs. Products or services in private preview, used for testing purposes, or available through other sales channels, aren't included in CSP price lists. This article includes details about pricing for Cloud Solution Provider partners and their update frequency:

• License-based services includes pricing information for Office 365, Enterprise Mobility, and Security E3, and Dynamics 365. License-based pricing section includes current and preview pricing and the offer list matrix. Price lists include list price and estimated retail prices (ERP) for offers in all supported currencies. The offer list matrix includes market availability and other important information about the offers. These files are updated on the first day of every month at midnight Coordinated Universal Time (UTC).

  Note

  List and ERP prices are for monthly billing frequency. For annual billing frequency, multiply the monthly price by 12.

• Usage-based services includes pricing information for Microsoft Azure and Visual Studio. You can also use the Azure Services in CSP Pricing Calculator. The usage-based download includes both the CSP price lists for all supported currencies and the Shared Services pricing files in ERP. These files are updated on the first day of every month.

• Microsoft Azure Reserved Instances includes pricing information for all supported currencies for Azure Reserved Instances. The pricing download also includes the Shared Services pricing in ERP. These files are updated on the first day of every month.

• Software subscriptions includes pricing for term-based software subscriptions for all supported currencies. The price file includes all supported currencies with list price and estimated retail prices (ERP). These files are updated on the first day of every month.

• Azure plan pricing includes pricing information for Azure plan consumption services and Azure plan reservation pricing. Prices are direct prices or ERP and can be retrieved for any given supported market. The data in these files is refreshed every day.

• Foreign exchange rates are used to calculate billing charged between USD and the partners local currency for Azure products. The rates are updated monthly.

• Marketplace includes pricing for independent software vendor (ISV) solutions from Microsoft's commercial marketplace. Prices are retrieved per market. The data in these files is refreshed every day.

Price list preview and change frequency

License-based services include a price list preview, provided 30 days in advance of any changes. To see the price list preview, go to Sell > Pricing and offers. EndOfSale offers aren't in the current month's price list but are in the current month's end of sale price list. There's no price preview for usage-based services since these services are dynamic. The following table explains how to read the price list table.

Price changes

Price changes are a common occurrence. Partners can anticipate price changes for license-based offers by looking at the price list preview. If a price change is reflected on the price list preview, partners can expect the change to go into effect on the first of the following month at midnight UTC. On the Partner Center, select the Pricing workspace to see the price list preview.

However, Azure usage-based pricing has no preview. Partners can keep up with Azure consumption price changes by using the RateCard API, which returns that day's meter pricing.

Usage-based prices can change throughout a month. To get 'current' daily pricing for these Azure resources, partners need to call the RateCard API.

Pricing and special segments

CSP offers some services to special market segments, for example, education, nonprofit and government community cloud. Not all services are available in every channel. No segment defaults to what we call the commercial segment. All license-based pricing is available in the license-based price list on the Price lists page. Azure Government pricing is available in the usage-based price list when signed into the Azure Government enabled CSP tenant. Software subscriptions don't yet support these special segments.

Partner margins, the difference between the list price and the estimated retail prices, can vary from segment to segment. Typically, education and nonprofit tend to have lower or no margins for CSP partners. Refer to the license-based price list for exact values.

Add-on offer types

License-based services can be acquired as either base offers or add-ons. Only base offers are discoverable and purchasable via the Partner Center catalog. Partners need to apply add-ons only after purchasing the base offers. The license-based price list Secondary license type column includes information about each offer and its type. Base offers have Nonspecific values in the price list secondary license type column and can be purchased in the catalog. Secondary license type values of add-on can't be purchased in the catalog. To purchase these add-ons:

1. Consult the offer list matrix to see the list of offer IDs that need to be purchased before you can purchase an add-on.
2. Purchase the base offer from the catalog
3. Navigate to your customer from the customer list. Select the base offer subscription you just purchased. On the manage subscription page, available add-ons appear that can be applied to the base offer.

Add-ons are listed regardless of their segment. A commercial Add-on can include education base offers. Education base offers can include commercial base offers. Partners should always use the prerequisite lists to understand that at least one of the prerequisites must exist before acquiring the add-on.

Pricing between Azure and other products

Pricing differs across different types of offers. License-based pricing is typically the amount per license for a given month. Usage-based pricing is defined for a specific resource with an associated meter ID. Partners aren't charged for acquiring the Azure subscription. However, partners are charged for resources consumed by different deployments under the Azure subscription. Pricing in the usage-based price list is organized around different resource meter IDs in Azure.

Azure reservations are term-based purchases for the particular resource type - Virtual Machines. Purchasing an Azure reservation enables a partner to pre-pay (one- or three-year terms) and reserve a given virtual machine. Reservations save the partner money and ensures their virtual machine is available for the duration of the term. A partner can align the reservation they want against the usage-based resource meter IDs. The meter IDs are consistent across the resource, whether the partner is purchasing a virtual machine or simply deploying the virtual machine as a usage-based resource.

European regional prices

Partners transact in regions that are assigned when they're on-boarded. The European region is unique since this region supports more than one currency. Partners request pricing based on the customer's market but are billed in their currency, which might be different than the customer market currency. In these cases, a partner gets pricing in all supported currencies for the customer market they request pricing information for. All European market price lists include pricing in all supported currencies in the European region. Partners are billed based on the market price sheet and currency line item aligning with the partner billing currency.

The multicurrency support enables a key scenario which had been blocked for years in traditional license-based and software pricing, enabling a partner to purchase a product SKU for a customer in a different country/region when the product SKU isn't available in the partner's country/region. This scenario is now enabled and no longer blocked in new commerce. Products now available in this scenario include some of the calling plans only available in specific EU markets. Other examples include Business Voice product SKUs, only available in GB, but can now be purchased by partners various EU countries.

Important details about the European regional price lists

Partners might see some variant prices for markets with different currencies than their own.

Slight price differences in same currencies across different markets:

Example:

• Product in UK GBP: 30.25
• Product for DE in GBP: 30.23

Slight price differences for the same term but with different billing frequencies:

• Product in UK GBP annual term with annual billing: 3393.9
• Product in UK GBP annual term with monthly billing: 3393.96

In both of these cases, partners can always rely on being billed the amount reflected in the price list for the customer market and partner billing currency.

Offers matrix

On the Pricing and offers page, view the Cloud Reseller Offer Matrix, to read about the different SKUs and product bundles available to you to sell. The offers matrix includes which offers are available per locale. If an item is listed on the price list but not on the offer matrix, it means that the products can't be ordered yet. As soon as they're available to order, the offers matrix is updated.

Microsoft also publishes a list of the Azure Services in CSP on the Pricing and offers page.

Offers matrix and price list questions

If you have questions about the price list or offer matrix, submit a service request through Partner Center.

Offer limits

Some license-based offers have certain rules and limitations that prohibit multiple purchases for the same customer. These rules apply to most trials and many of the small business offers. Small business offers are defined by those offers that have a maximum license count that is less than 300.

These purchasing constraints are defined as part of the offer configuration and can be found by looking in the offer list matrix. Two columns of data work together to define the enforcement: 1. Offer Limit Scope and 2. Offer Limit. The constraints are enforced during a purchase. The catalog in Partner Center disallows a partner from purchasing more offers than the rules allow. Any attempt to violate the constraints results in an error.

Offer limit scope is recorded as a column on the offer list matrix and can have values of None, Lifetime or Concurrent.

• Offers with None can be purchased without constraints
• Lifetime offers can be purchased only once
• Concurrent offers can be purchased as many times as is allowed by the Offer Limit value for that offer. Most trials have a Lifetime Offer Limit Scope with an Offer Limit of 1. Most small business offers have a Concurrent Offer Limit Scope with an Offer Limit of 2.

Taxes and pricing

All pricing in Partner Center CSP price lists is tax-exclusive. For more information in the Partner Center document Taxes and tax exemptions.

Offer attestation

Some offers require the partner to agree before buying. This process is called attestation, and the only offers requiring attestation are Windows 365 Business offers with Windows Hybrid Benefit. Partners see text on the review screen when purchasing these offers that says, "I understand that each person using Windows 365 Business with Windows Hybrid Benefit also needs to have a valid copy of Windows 10/11 Pro installed on their primary work device." Partners must agree to this before purchasing.

Attestation applies both to the Partner Center and the Partner Center APIs when submitting orders and checking out carts. Partners can determine which offers require attestation by checking the AttestationProperties on the offer or SKU objects.

These properties explain the attestation type and if the attestation is enforced for purchases (enforceAttestation=True). If required, partners simply set the AttestationAccepted to true on the cart or order line items.

The following offers currently require attestation prior to purchasing

Multiyear term offers

Thirty-six month offers

There are approximately 50 Dynamics offers that have three-year terms. These are identified by (36 mo) in the title of the offers. These offers are similar to the yearly term offers. The only difference is their term. These offers renew automatically after three years instead of one.

Here's a summary of how these offers work:

• Terms are thirty-six months, and subscriptions renew automatically after three years.
• Partners can cancel or change the number of licenses throughout the term of the subscription.
• Annual renewal is at the price of purchase time for the three-year term.
• Billing frequency is still yearly or monthly.

72 month offers

Microsoft 365 A1 base offer has a six-year term. The Office 365 A1 add-ons are available after purchasing this base offer.

Here's a summary of how these offers work:

• The term is 72 months (six years).
• As subscription isn't renewed and expires after six years.
• Billing frequency on the offer shows as annual, but the partner is billed up-front on their first invoice after acquiring the subscription.
• Subscriptions for A1 72-month offers are locked after purchase and can't be canceled.
• License counts can be added to the subscription after initial purchase.
• This subscription is noncancelable and nonrefundable.

Estimated retail price (ERP)

Most price lists include a list price, the price the partner is billed, and the estimated retail price. Estimated retail price (ERP) is also called Microsoft suggested retail price or MSRP. These two values, ERP and MSRP, represent the estimated market value of the products if a customer were to purchase the products directly from Microsoft.

Here's where to find ERP/MSRP details for each type of product or service:

New commerce license-based pricing

Pricing strategy in new commerce Microsoft 365/Dynamics 365 remains the same between traditional and new commerce. Each currency has one price and monthly plan charges for a term remains constant through the remainder of the term. Partners are billed in their country/region currency.

How to access price lists and why

New commerce license-based price lists requests are by market country/region. For example, if a partner wants to get pricing for products sold to a German (DE) customer, they would ask for the German (DE) price list. For European countries/regions (and ONLY for European countries/regions), these market-based price list files include pricing in all six supported European currencies (SEK, NOK, CHF, DKK, GBP, EUR). Currency pricing enables the partner to understand how much they are billed in their currency regardless of the customer market. If a partner in Great Britain (GB), for example, wants to purchase a product SKU for a customer in Germany, they would get the DE price sheet and need only the Great Britain Pounds (GBP) pricing because the GBP price point is what the partners are billed. Supporting pricing by market aligns the product availability to the pricing, enabling partners to get pricing for markets even when the product might not be available to customers their own country/region. This design also can support future scenarios if different markets with the same currency need different pricing.

Pricing data is available to partners both from the Partner Center dashboard and through the pricing sheet API. Partners download the price list by navigating to the Price lists page. The new commerce offer price list and offer matrix are labeled with New Commerce.

Price lists include basic information about pricing (how much it costs). The offer matrix includes purchase information about the products (how to buy it). Much of the information included in these download files is also accessible through the various Partner Center APIs (catalog APIs and price sheet APIs). Price lists require the partner to select the market for the pricing they request while the Offer-list matrix is agnostic of market.

Price list and offer-list matrix files default to the current month. To retrieve the previous month's price list, select the month and then download the pricing file for the desired market. Price changes should occur only on a monthly cadence. Partners can use the price list preview to know of price changes coming in the next month. Price changes mid-month rarely occurs, usually to correct an error in the data. Any mid-month price changes are broadly announced and be reflected in the price sheet with a new EffectiveStartDate.

Market specific discounts

Some markets include geo-specific discounts on top of the CSP margin discounts. Partners might discover pricing for select product SKUs having deeper discounts in some markets depending on the product SKU. Markets might include a deeper discount are the United Kingdom, India, Australia, or Canada. These discounts are very targeted and only affect a very small number of product SKUs. One example:

• Product SKU name: Teams Phone with Calling Plan
• ProductId: CFQ7TTC0HL73
• SkuId: 0001

In this case the CSP price might be discounted in the GB market, so other EU markets may see a higher CSP price point, reflect as unit price in the price lists.

New commerce pricing versus traditional license-based pricing

There should be general consistency between tradition and new commerce pricing for most product SKUs. However, partners might notice slight differences when comparing legacy traditional license-based pricing to new commerce pricing.

New commerce terms and billing frequencies

Partners are billed in their currency based on the currency value in the price list. This billing charge remains constant for a billing plan that is shorter than the term. Annual term (P1Y) prices reflect the 12 months, partners divide the total by 12 to get the monthly plan charge.

The new commerce price list has three fields that work together to help the partner understand the amount they are billed when transacting. TermDuration describes how long the subscription lasts. Most subscriptions support Annual or pay for one year (P1Y) and monthly pay for one month (P1M). The UnitPrice amount is for the term being purchased. If a partner purchases an annual term with monthly pricing, they are billed one-twelfth the total amount each monthly billing period. The amount billed each month for an annual term with monthly billing is the same each month throughout the term. Price changes during the term don't affect billing plan charges for an existing subscription. Price changes are only relevant for renewals, transitions, and new subscriptions.

Monthly and annual terms

The price list includes termDuration data that explains how long the term lasts. Many products support both monthly (P1M) and annual (P1Y). However, not all products support monthly term. A few examples of this include: Microsoft Intune, Microsoft Defender for Cloud, some Phone System and Calling plans, and various Exchange Online stand-alone products. Partners should reference the current price list and filter by termDuration to view product SKUs by term.

Three-year terms in new commerce

Some partners have customers that need three-year terms to preserve the pricing for the lifetime of the term. Price changes that occur during the term are only applied to newly purchased subscriptions or new term renewals at the time of price changes. Microsoft is soon adding support for three-year term SKUs for Microsoft E3, E5, and Teams Enterprise. Three-year terms are only available for some product SKUs. Partners use the license-based new commerce price lists to discover which SKUs support three-year terms.

Details about the three-year Microsoft 365 enterprise SKU terms:

• The new three-year term enterprise SKUs (ESKUs) are first available in the price list preview and purchasable the following month. The end of sale SKUs with teams also support the three-year terms. Three year SKUs include P3Y in the price list preview's TermDuration column.
• These three-year SKUs are assigned a distinct SKUID and are not terms on the existing ESKUs but their own SKUID outright. SKUIDs can be found in the price list files.
• These three-year SKUs have the same provisioning ID as the one-year and monthly ESKUs, so converting to three-year terms does not require license reassignment.
• Moving from an entperise SKU annual term to these new three-year terms requires an upgrade/conversion, not a change term action.
• The three-year term follows all the existing rules around cancelation and management scenarios for new commerce subscriptions. (link to manage, link to cancelation policy).
• Partners find details about minimum requirements in the partner center price lists. The three-year SMC SKUs require a 100 license count minimum enforced on conversion or new subscription purchases.
• The new three-year terms support both the current "without teams" ESKUs and the end of sale state "with teams". Partners with older "with teams" ESKU subscriptions can convert to these three-year term ESKUs.
• The with teams three-year term SKUID information is available in the price list preview and then in the End of Sale price list.
• These new three-year terms are new commerce only, CSP legacy license-based subscriptions are continuing along their retirement or migration to new commerce. See the migration topic for details about legacy to new commerce migration.
• Other three-year terms (mostly Dynamics SKUs) function the same way they always have. The SMC three-year SKUs are distinct from other three-year terms because they have new seat minimums, have distinct SKUIDs, and are upgraded to instead of changing an existing enterprise subscription term.
• Partners that need to purchase annual and the new three-year term SKUs in the same cart need to ensure they have the same billing plan of Annual to get available promotions.

New commerce price list

Select the market and then export the price list file. The file is a compressed, comma-delimited text file.

New commerce price list details

The structure of items in the new commerce pricing file differs from the traditional office price list.

New commerce offer matrix

The offer matrix contains purchase information and rules for the product SKUs. It's market-agnostic. End of sale offers are also in the offer matrix, refer to price list for active offers.

Effective dates

Partners see two important date time values in the price lists: EffectiveStartDate and EffectiveEndDate. Partners use these values to determine which line items are active and current. Sometimes line items are duplicate in the price list, and when this occurs partners can look to the latest date ranges to identify the current line items and price points. Partners can rely on the latest date range unless the date ranges overlap. Newly available product SKUs and price changes go into effect on the first of the month at midnight UTC.

Here's an example of overlap:

In the preceding example, a transaction made on November 2 would be related to the top line item. A transaction made on November 4 would be associated with the second line item. Overlap is a condition the Partner Center team is working to resolve because it can cause confusion for price list consumers.

Price list preview

New commerce supports future pricing. Partners can export and view future pricing for the coming month. Traditional license-based price lists included flags for new offers, deleted offers, changed and unchanged. New commerce pricing files enable partners to track these changes by using the EffectiveStartDate and EffectiveEndDates.

New offers are identified when they're in the future price file but not in the current price file.

Offer limits in new commerce

Existing license-based subscriptions enforced ownership limits, or the number of subscriptions a partner could purchase for a customer. These typically were small business SKUs or offers with less than a 300-license maximum. In traditional license-based subscriptions, partners could see the limits in the offer list matrix for existing license-based products as Concurrent describing the number of subscriptions the partner could have. New commerce implements a license constraint across the purchased product SKUs. New commerce small business maximum 300 maximum constraints are applied at the product SKU level. So a partner could have multiple small business subscriptions for a customer as long as the aggregate of the license counts stays under the declared maximum. The maximum for small business applies regardless of where the customer's product SKU came from, that is, multiple partner or channels.

Traditional license-based included a Concurrent setting with a limit value, usually of two. These settings mean the customer could have a maximum of two subscriptions for the offer from a given Partner.

Here's an example of the traditional, license-based offer and the concurrency setting:

• Microsoft 365 Business Premium
• Offer ID: 61795cab-2abd-43f6-88e9-c9adae5746e0
• Offer Limit Scope: Concurrent
• Offer Limit: 2

New commerce license-based uses a Max license Count with a value to enforce these small business limits. The product SKUs enforces this limit on any purchased subscriptions for the product SKU. So, a given customer could have four subscriptions from different partners if the total number of licenses from all subscriptions was less than 300. The limit is on the number of aggregate licenses purchased for the product SKU, not on the number of subscriptions. Partners can view these values in the offer matrix for new commerce and get these values in the SKU using the catalog APIs. Here's an example of a new commerce product SKU with the max count value:

• Microsoft 365 Business Premium
• Product ID: CFQ7TTC0LCHC
• SKU ID: 0002
• Max license Count: 300

The maximum limits are pooled on the customer tenant. A customer could have 100 licenses of a product SKU from one partner, and another 100 from a second partner. But the aggregate limit can't exceed the maximum. A transaction that exceeds the limit returns an error that includes the remaining number of available licenses, helping them to understand how many licenses are left under the maximum available. The error message looks like this: The requested number of 51 license exceeds the remaining limit of 50 license allowed per subscription for the CatalogItemId - CFQ7TTC0LCHC:0002:CFQ7TTC0KFFN. Partners also see this information when using the APIs to add a lineItem to the cart that exceeds the limit as an error property availableQuantity. More information about the cart lineItem property can be found in the API documentation cart resource.

Partners can validate these limits and the available quantity functionality in sandbox by testing specific product SKUs with lower maximum limits. Partners can reference the offer matrix to find these product SKUs.

SKUs with no cost

Trials are always free, but other product SKUs might also be free with no cost. Below are some examples of no cost product SKUs. The list of free product SKUs might grow over time. Partners should be sure to reference the price list for the current list of free products.

Pricing and offer matrix APIs

Pricing and offer matrix APIs build on the existing price sheet API infrastructure that was released to support Azure plan. This API is now extended to support license-based new commerce pricing. The price sheet and offer matrix APIs supports pricing for updated new commerce license-based online services only. It doesn't support traditional office license-based services available for download only from Partner Center pricing and offers page.

Related content

• Azure plan pricing
• Azure pricing overview