New: Odoo and Dynamics 365 cost calculators.Estimate your costs

Dynamics 365 Commerce Pricing: Per User, Add-On, Canada and 3-Year TCO

Dynamics 365 Commerce is $210/user/month (CAD 284.90), $30 attach on a Finance or SCM base, $4,000 e-Commerce add-on. Canada prices and a 3-year TCO.

Dynamics 365Pricing & ROI14 min readUpdated 17 sources

Key takeaways

  • Standalone user: $210 (CAD 284.90). Attach: $30 on a Finance or Supply Chain Management base. Storefront: $4,000 (CAD 5,427.20) per tenant.
  • Omnichannel retail platform on the F&O engine: POS, e-commerce, merchandising, pricing, distributed order management
  • Four lines: $210 standalone user, $30 attach user, $4,000 e-Commerce tenant add-on, $4,200 headless tenant add-on
  • Retail and Commerce are the same product line: one current price card

Dynamics 365 Commerce pricing at a glance

As of November 2026, Dynamics 365 Commerce lists at $210 per user per month in the United States and CAD 284.90 in Canada, paid yearly. The online storefront is a separate tenant add-on at $4,000 per month (CAD 5,427.20 in Canada), and a headless add-on for custom front ends lists at $4,200 per month (CAD 5,698.50). Users who already hold a Finance or Supply Chain Management base can license Commerce as an attach at $30 per user per month.

The table below puts every line a Commerce quote can contain on one screen. Microsoft marks its price pages as informational, so the amount at checkout or on your reseller quote is the one that applies. Services, Azure consumption and hardware sit outside these lines.

  • Standalone user: $210 (CAD 284.90). Attach: $30 on a Finance or Supply Chain Management base. Storefront: $4,000 (CAD 5,427.20) per tenant.
  • The Commerce price page lists no register fee and no per-store Scale Unit fee. Devices come from the Operations licensing family.
  • Budget implementation separately: a common planning band is $2 to $5 for every $1 of licenses.
Dynamics 365 Commerce line items as of November 2026. Microsoft lists are paid yearly; Canada amounts exclude applicable tax. The attach price comes from the Dynamics 365 Licensing Guide (November 2026), which publishes it in USD only. Microsoft publishes no device price.
LicenseUnited StatesCanadaWho needs it
Dynamics 365 Commerce (user)$210 per user per monthCAD 284.90 per user per monthMerchandisers, retail operations and call center staff who work in headquarters
Commerce attach to a qualifying base$30 per user per monthNot published in CAD; your CSP quotes itUsers who already hold Finance or Supply Chain Management, standard or Premium
e-Commerce add-on$4,000 per tenant per monthCAD 5,427.20 per tenant per monthCompanies that run the Commerce storefront
Headless add-on$4,200 per tenant per monthCAD 5,698.50 per tenant per monthCompanies that build a custom front end on the Commerce engine
Operations Device (shared POS)Not published; your CSP quotes itNot published; your CSP quotes itShared tills and scanners used across shifts

What Dynamics 365 Commerce is and why its pricing differs from the rest of Dynamics 365

Dynamics 365 Commerce is Microsoft's omnichannel retail and e-commerce platform, the successor to Dynamics 365 Retail. It runs on the same Finance and Operations (F&O) engine as Dynamics 365 Finance and Supply Chain Management. It covers point of sale (the Store Commerce app), e-commerce storefronts, merchandising and assortments, pricing and promotions, distributed order management, loyalty, and connections to call centers and marketplaces.

Commerce pricing confuses buyers because the product is not a single seat. A working retail deployment is a stack of licenses: named users for merchandising and operations, device licenses for shared POS terminals, a tenant-level e-commerce add-on, and a Commerce Scale Unit (CSU) with its own device and transaction caps. The $210 headline is the entry point, and most retailers add two or three more line items before go-live.

For the broader F&O price ladder, including Finance and Supply Chain Management at $210 per user, read the Finance and Operations pricing guide first, then come back here for the retail layers. If you want the product tour rather than the price tour, the Dynamics 365 Commerce guide covers capabilities and architecture.

  • Omnichannel retail platform on the F&O engine: POS, e-commerce, merchandising, pricing, distributed order management
  • A real deployment is a stack of licenses: named users, devices, a tenant add-on and a Scale Unit
  • The $210 per user headline is the floor, and most retailers add two or three more line items
  • Commerce licensing differs from pure Finance or Supply Chain deployments, which is why it has its own guide

The Commerce SKUs and their 2026 list prices

Microsoft publishes three Commerce line items on its public pricing page, and a fourth, the attach, lives in the Dynamics 365 Licensing Guide. The figures below are annual-commitment list prices as of November 2026, re-checked against Microsoft's US and Canada Commerce pricing pages. Regional currencies and checkout pricing may differ, and negotiated discounts through a partner or enterprise agreement routinely take these down.

The first SKU is Dynamics 365 Commerce at $210.00 per user per month, paid yearly. It is the standalone named-user license for anyone who manages omnichannel retail operations: merchandisers, category managers, retail operations staff and store managers who log into headquarters. The second is the e-Commerce add-on at $4,000.00 per tenant per month, which switches on e-commerce management. The third is the headless add-on at $4,200.00 per tenant per month, described by Microsoft as custom commerce experiences. Microsoft's pricing layout sometimes shows a "user/month" label near these add-ons, but they are licensed per tenant, not per cashier.

The attach is the cost lever Microsoft does not show on the Commerce pricing page. The Dynamics 365 Licensing Guide (November 2026) prices Commerce as an attach at $30 per user per month when the user's base is Finance, Finance Premium, Supply Chain Management or Supply Chain Management Premium. Business Central and the customer engagement apps do not qualify as a base for a Commerce attach. That one line can reshape a retail program's economics, and the next sections cover it.

The pricing page does not say whether a POS-only rollout buys the e-Commerce add-on, the headless add-on, both or neither. A quote should state which of those choices it used, because the difference is $4,000 or $4,200 a month.

  • Four lines: $210 standalone user, $30 attach user, $4,000 e-Commerce tenant add-on, $4,200 headless tenant add-on
  • Attach is the only one not on the public Commerce pricing page: it lives in the Dynamics 365 Licensing Guide
  • All prices are annual-commit list; partner and enterprise-agreement discounts are common
  • Treat the tenant add-ons as per tenant, not per cashier: they are the surprise line on most quotes
Dynamics 365 Commerce line items, annual-commit list price in USD as of November 2026. Sources: Microsoft Dynamics 365 Commerce pricing page and the Dynamics 365 Licensing Guide (November 2026).
SKUList priceLicense basisWhen it applies
Dynamics 365 Commerce$210/user/monthNamed userStandalone: when you are new to F&O or do not have a qualifying base
Commerce Attach (to Qualifying Base)$30/user/monthNamed user (requires qualifying base)When the user already holds Finance or Supply Chain Management, standard or Premium
e-Commerce add-on$4,000/tenant/monthTenant (sized by transaction tier)When you run the Commerce online storefront
Headless add-on$4,200/tenant/monthTenantWhen a custom front end runs on the Commerce engine

Dynamics 365 for Retail pricing: the old name for Commerce

Dynamics 365 for Retail is the earlier name of what Microsoft now sells as Dynamics 365 Commerce. As of November 2026, Dynamics 365 for Retail pricing in the USA is the Commerce card: $210 per user per month, paid yearly. Microsoft's current Commerce pages do not list a separate Retail SKU or a separate Retail dollar amount, and the same answer applies to North America buyers billed in US or Canadian dollars.

If a proposal, an old bookmark or a reseller deck uses the Retail name, price it with today's lines: $210 per user (CAD 284.90 in Canada), plus the $4,000 e-Commerce add-on (CAD 5,427.20) or the $4,200 headless add-on (CAD 5,698.50) only if the design needs them. Ask the seller which of those three choices the quote used. Do not carry an old device price into a 2026 budget either, because the Commerce price page lists no register or device fee.

Treat the nickname "Commerce360" or "Commerce 360" the same way. We found no product by that name on Microsoft's Commerce pricing or product pages. If a document uses it, ask which contract it refers to, and put services fees on a statement of work.

  • Retail and Commerce are the same product line: one current price card
  • US: $210 per user per month. Canada: CAD 284.90, plus applicable tax
  • No separate Retail SKU on Microsoft's current pricing pages

Dynamics 365 Commerce pricing in Canada

Canada has its own Microsoft price list. As of November 2026, Commerce is CAD 284.90 per user per month, the e-Commerce add-on is CAD 5,427.20 per tenant per month, and the headless add-on is CAD 5,698.50 per tenant per month. All three are paid yearly, plus applicable tax. Microsoft says the prices shown are informational and may differ from the actual list price because of currency, country and regional factors, so the checkout amount governs.

Worked example, with assumptions stated: 8 Commerce users, Canada list, yearly billing, November 2026, tax ignored. The users cost 8 x CAD 284.90 = CAD 2,279.20 per month. Adding the e-Commerce add-on at CAD 5,427.20 brings the software list to CAD 7,706.40 per month, or CAD 92,476.80 over a year. The same 8 users on Business Central Essentials at CAD 108.50 cost CAD 868 per month before any storefront.

Canadian buyers should also ask about the attach rate. Microsoft publishes attach prices in USD only, in the Dynamics 365 Licensing Guide, so the CAD attach amount comes from a Canadian CSP quote.

Dynamics 365 Commerce and Business Central list prices, USD and CAD, as of November 2026. Yearly billing. Canada amounts exclude applicable tax.
LicenseUnited StatesCanada
Commerce user$210 per user per monthCAD 284.90 per user per month
e-Commerce add-on$4,000 per tenant per monthCAD 5,427.20 per tenant per month
Headless add-on$4,200 per tenant per monthCAD 5,698.50 per tenant per month
Business Central Essentials$80 per user per monthCAD 108.50 per user per month
Business Central Premium$110 per user per monthCAD 149.20 per user per month
Business Central Team Members$8 per user per monthCAD 10.90 per user per month

Attach licensing: the $30 lever most retailers miss

If your company already runs Dynamics 365 Finance or Supply Chain Management, your Commerce users rarely need the standalone $210 SKU. They can license the Commerce workload as an attach for $30 per user per month on top of that base. The attach gives the same core Commerce capabilities and the same retail operations, merchandising, POS configuration and distributed order management use rights as the standalone license.

The qualifying bases for a Commerce attach, per the Dynamics 365 Licensing Guide (November 2026), are Finance, Finance Premium, Supply Chain Management and Supply Chain Management Premium. Business Central Premium, Customer Service Enterprise and Field Service do not qualify, whatever older partner tables say. The base-plus-attach rule still applies: the highest-priced app for a named user is the base, and Commerce rides as the attach when one of those bases is already assigned. You cannot attach Commerce to a Team Members or device license.

The trade-off sits in entitlements. The base carries the platform, storage and environment rights, and an attach license rides on it without adding platform, storage or environment entitlements of its own. The Licensing Guide sets the Commerce attach at $30 per user per month in USD; older partner tables that show $20 predate it. Confirm eligibility and the price on your CSP quote before you commit.

  • Commerce attach: $30 per user per month when the user already holds Finance or Supply Chain Management (standard or Premium)
  • Identical core capabilities to the $210 standalone, the trade-off is platform/storage entitlements, not functionality
  • Every full-access attach user must already hold the qualifying base; you cannot attach onto a Team Member or device license
  • The largest per-seat saving in the Commerce catalog, check it first in any licensing review
  • Verify the current rate and eligibility matrix against the latest Licensing Guide before you sign

Device and activity licenses for the store floor

Retail deployments do not run on named-user licenses alone. A store with three POS terminals running across two shifts cannot sensibly license every cashier as a $210 named user, so Microsoft offers two license types for shared and lighter-use scenarios: the Operations Device license and the Operations Activity license. Both are documented in the Dynamics 365 Licensing Guide and apply across the F&O family (Finance, SCM, Commerce, and Project Operations).

The Operations Device license is assigned to a device, typically a shared POS terminal or a warehouse scanner, rather than a person, so any number of staff can log in through that device across shifts. The Activity license is a named-user license for staff who need more Dynamics 365 capability than a Team Members user but less than a full Operations user, for example a store manager who runs reports and approves transactions but does not do central merchandising. Microsoft publishes no list price for either, so your Cloud Solution Provider (CSP) quotes them, and the worked cases in this guide leave them out of the totals. Expect the device estate to be a large line in multi-store math.

Two rules govern how these fit together. First, Microsoft requires a minimum purchase of 20 base Commerce (or qualifying F&O) full-user licenses in the CSP model, which sets a floor on the smallest viable deployment. Second, the Commerce Scale Unit has its own device and transaction caps that are separate from per-device licensing, being under a CSU device cap does not exempt a POS terminal from being properly licensed. Conflating the CSU capacity entitlement with the licensing requirement is the most common budgeting error in Commerce programs.

  • Device license (quoted by your CSP): assigned to a shared POS terminal, the usual way to license a store estate
  • Activity license (quoted by your CSP): named-user license for lighter F&O and Commerce users who need more than Team Members
  • Minimum 20 base full-user licenses in the CSP model sets a floor on the smallest deployment
  • CSU device/transaction caps are separate from licensing, being under a cap does not exempt a device from a license
Store-floor license types for Dynamics 365 Commerce. Source: Dynamics 365 Licensing Guide (November 2026). Microsoft publishes no list price for these licenses; your CSP quotes them.
License typePrice (planning)Assigned toTypical use
Operations DeviceQuoted by your CSPA device (POS terminal, scanner)Shared tills across shifts, license the till, not each cashier
Operations ActivityQuoted by your CSPA named userLighter F&O/Commerce users, e.g. store managers running reports, approvals
Team MembersQuoted by your CSPA named userRead/write to a limited set of entities, very light back-office staff

The e-Commerce add-on: $4,000 per tenant and the transaction tiers

The Dynamics 365 Commerce e-Commerce add-on is the line item that turns on the online storefront. At $4,000 per tenant per month (annual commitment) on Microsoft's Commerce pricing page, it is licensed per tenant rather than per user, which is why a small online channel can still carry a sizeable fixed cost. The add-on requires at least one Dynamics 365 Commerce base or attach license, you cannot buy the storefront in isolation, and it is sized through a tier structure based on monthly e-commerce transaction volume.

Microsoft exposes e-Commerce capacity through tiers. Partner licensing explainers that map to the Licensing Guide describe Tier 1 covering up to 3,000 transactions per tenant per month, Tier 2 covering 10,000, and Tier 3 covering 25,000; above your tier, overage capacity is purchased in 500-transaction increments. These transaction tiers run in parallel with the Commerce Scale Unit device-and-transaction model: a CSU Basic handles up to roughly 3,000 e-commerce transactions or 65 POS devices, a CSU Standard up to 10,000 transactions or 225 devices, and a CSU Premium up to 25,000 transactions or 500 devices. One CSU is typically provisioned by default when you buy the e-Commerce license or device licenses; combined online-and-offline retailers usually need additional CSUs, which Microsoft lists as separate tenant-level Commerce Scale Unit SKUs (Basic / Standard / Premium Cloud).

The practical implication for budgeting is that e-commerce cost scales with volume, not headcount. A retailer doing 2,500 online orders a month fits on Tier 1 at the $4,000 entry; a high-volume D2C brand doing 20,000 orders needs Tier 3 and likely an additional CSU. Model your peak-season transaction volume, not your average, when you pick a tier, overage across many stores is where e-commerce bills quietly balloon, and the CSU device cap interacts with your store count if you run POS through the same scale unit.

  • e-Commerce add-on: $4,000/tenant/month, per tenant, not per user; requires at least one Commerce base or attach license
  • Transaction tiers: Tier 1 = 3K/month, Tier 2 = 10K/month, Tier 3 = 25K/month; overage in 500-transaction increments
  • CSU tiers mirror this: Basic 3K txns / 65 devices, Standard 10K txns / 225 devices, Premium 25K txns / 500 devices
  • One default CSU is typically provisioned with the e-Commerce or device licenses; combined online + offline usually needs additional CSUs
  • Budget for peak-season volume, not average, overage and extra CSUs are where e-commerce bills balloon

Commerce Scale Unit and POS integration: what is priced and what is not

Commerce Scale Unit POS integration is an architecture, not a line on Microsoft's Commerce price card. The Scale Unit hosts the Commerce Runtime and the business logic that POS, e-commerce and partner channels use. It can run in Microsoft Azure or be self-hosted in the store or a data center, and one environment can mix both. The public Commerce price page lists no Scale Unit services fee, while partner price lists show Scale Unit capacity SKUs, so ask a reseller which one your quote carries.

Store Commerce runs on Windows, iOS, Android and macOS, and Store Commerce for web runs in Microsoft Edge and Google Chrome. Per Microsoft Learn, only Store Commerce for Windows has built-in offline mode and a local Hardware Station. Store Commerce for web cannot reach POS hardware directly or work offline. Modern POS was deprecated in October 2023, so current work uses the Store Commerce app.

A practical store design has four decisions. Which registers need Windows because they use cash drawers, printers or offline selling. Which can be browser POS because the lane has dependable connectivity and no direct hardware. Whether the store Scale Unit is cloud, self-hosted or both. Which payment devices sit on the Hardware Station. Integration services from Flectic or another implementer configure that design, and they are a services line, not a Microsoft list price.

If a proposal names a package such as "Commerce Scale Unit POS integration services", ask for its contents: Hardware Station, Scale Unit topology, Store Commerce install, payment certification and a pilot store. Then separate that labor from the $210 user license and from any tenant add-on. The deeper architecture lives in the Dynamics 365 Commerce guide, and the device side of point of sale is covered in the POS system guide.

  • Scale Unit: commerce logic for POS, e-commerce and partner channels, in Azure or self-hosted
  • Hardware Station: printers, cash drawers and card readers; built into Store Commerce for Windows
  • Offline selling: Store Commerce for Windows; web POS needs a live connection
  • Modern POS: deprecated October 2023; new work uses Store Commerce

Copilot, headless commerce and agent channels: value beyond the SKU

List price answers what Microsoft charges. Retailers pay for Commerce because of the runtime: a headless commerce engine on the Scale Unit, Store Commerce POS, distributed order management and, increasingly, AI surfaces that reuse the same pricing, inventory and promotion engines instead of a second stack.

Copilot in Commerce Site Builder helps merchandisers write product and marketing content for B2B and B2C storefronts, and cloud-powered product search uses Azure AI Search behind category browse and keyword search. That search is an Azure-backed capability, which is one reason Azure consumption appears next to the license line on a real bill.

In 2026 Microsoft also published the Dynamics 365 Commerce Model Context Protocol (MCP) server in preview. It exposes catalog, cart, promotion, inventory and order tools to compatible agents on the same Scale Unit that powers POS and e-commerce. For cost planning, treat agent channels as a use of Commerce plus the Scale Unit plus identity, not a replacement for the e-Commerce add-on, and budget Copilot Credits when you build custom agents.

  • Copilot in Site Builder speeds catalog authoring for B2B and B2C storefronts
  • Azure AI Search powers product discovery across Scale Unit channels: plan Azure spend with search traffic
  • Headless APIs keep POS, web, call center and custom front ends on one pricing and inventory engine
  • Commerce MCP (preview, 2026) opens agent shopping on the same Scale Unit; custom agents may consume Copilot Credits

What else Microsoft prices separately

Beyond the core licenses and the e-Commerce add-on, several Commerce capabilities are licensed as separate per-tenant modules. These are not included in the $210 named-user license or the $4,000 add-on, they are additive SKUs you opt into based on the experience you want to deliver. Treating them as part of the base Commerce bundle is a reliable way to under-budget a program.

The three most common are Dynamics 365 Commerce Recommendations (the machine-learning product-recommendations engine), Dynamics 365 Commerce Ratings and Reviews, and Dynamics 365 Fraud Protection. Each is licensed per tenant, with its own price and, in some cases, its own consumption dimension. The Recommendations module, for example, has historically been priced at a premium tier level (with marketplace listings showing multi-thousand-dollar per-month bands), reflecting the machine-learning compute behind it.

The budgeting discipline here is to scope your experience deliberately. A pure B2B Commerce deployment with a curated catalog may not need Recommendations or Ratings and Reviews at all, whereas a consumer D2C brand will likely want all three. Build the per-tenant module line items into your year-one and steady-state model explicitly, and revisit them each renewal, Microsoft has been bundling and unbundling AI-adjacent capabilities across the Dynamics 365 suite as Copilot and agent features expand, and the module boundaries are not frozen.

  • Separately licensed per-tenant modules: Commerce Recommendations, Commerce Ratings & Reviews, Fraud Protection
  • Not included in the $210 user license or the $4,000 e-Commerce add-on, additive SKUs
  • Recommendations carries premium pricing reflecting the ML compute behind it
  • Scope by experience: B2B/curated may skip Reviews/Recommendations; D2C typically wants all three
  • Revisit each renewal, Microsoft has been re-bundling AI-adjacent capabilities as Copilot expands

Azure, dual-write, license validation and other hidden lines

Dynamics 365 Commerce runs on Azure, and several of its runtime components meter separately from the per-user and per-tenant licenses. The Commerce Scale Unit hosts the Commerce Runtime, the headless commerce engine, and the channel-side retail services exposed to POS, e-commerce, call-center, and (with MCP) agent clients. A cloud CSU is provisioned inside your environment, but the Azure infrastructure it depends on, compute, storage, data egress, search, and any Azure-hosted integrations, is billed through your Azure subscription on consumption.

Dual-write is free as an integration capability when you already hold F&O (including Commerce) rights to replicate data with Dataverse, but it is not a free CRM. Customer Engagement apps (Sales, Customer Service, etc.) still need their own user licenses, and dual-write data consumes Dataverse capacity that may require extra storage purchases. Retailers who want call-center CRM next to Commerce HQ should model CE seats + Dataverse storage as separate lines, not as "included with dual-write." A Microsoft Entra ID tenant is mandatory to use Dynamics 365 at all.

From January 2026 Microsoft has been rolling out improved assigned-license validation for Finance and Operations apps (Finance, SCM, Commerce, HR, and related operations apps). Users without the correct assigned license can lose access after renewal-driven enforcement windows. That makes "share one HQ login across the store team" a compliance and outage risk, not a clever saving, device licenses and named Activity users exist precisely so the estate stays licensed under enforcement. Self-hosted Retail Store Scale Units remain available for offline store scenarios without an extra license fee, but every user and device touching them must still be properly licensed.

  • CSU runs in Azure, compute, storage, egress, search, and integration runtimes meter through your Azure subscription
  • Dual-write is not a free CRM: CE licenses + Dataverse capacity are separate; dual-write only entitles replication for licensed F&O data
  • Improved F&O license validation (2026) blocks unlicensed users after enforcement windows, plan real device/named seats
  • Self-hosted Retail Store Scale Units are license-free for offline scenarios, but every user/device must still be licensed
  • Plan a steady Azure + capacity line on top of licenses, a TCO exercise, not a license tally, sizes the program

Dynamics 365 Commerce vs Business Central plus Shopify: cost and fit

Not every retailer needs Dynamics 365 Commerce. Three common paths compete on price and depth: Commerce on the F&O platform, Business Central with a retail extension, and a Shopify storefront connected to Business Central or another ERP. Choosing wrong is expensive because moving between them is a second project. The long Commerce versus Shopify Plus comparison, including the flat-fee and sales-share pricing, lives in the Commerce vs Shopify Plus article.

As of November 2026, Business Central Essentials lists at $80 per user per month and Premium at $110, paid yearly (CAD 108.50 and CAD 149.20 in Canada). That is well below Commerce at $210 per user, and many mid-market retailers pair Business Central with Shopify Plus or another storefront rather than the $4,000 per tenant Commerce add-on. That stack wins when store count, order-routing complexity and multi-entity retail rules are moderate. Commerce wins when you need enterprise distributed order management, deep F&O inventory and warehouse integration, headquarters merchandising with Store Commerce across many stores, or the headless and MCP channel model on one Scale Unit.

A practical rule: if you already run Finance or Supply Chain Management and need omnichannel retail, Commerce attach ($30) plus devices and the e-commerce tier is usually cheaper than rebuilding F&O depth on Business Central. A company with one or a few stores will usually land a lower three-year bill on Business Central plus Shopify, or on Odoo (covered below). Price the whole stack: POS hardware, payment fees, tax engines and the integration statement of work, not only Microsoft seats.

  • Commerce is enterprise F&O retail, not the default for every store that needs a website and a till
  • Business Central at $80 to $110 per user plus Shopify is often cheaper for small multi-channel retailers
  • Already on Finance or Supply Chain Management? Commerce attach often beats re-platforming retail on Business Central
  • Price POS hardware, payments, tax and integration services: seats are one line of several
Where each stack typically wins (planning view, not a formal Microsoft product matrix). USD list prices, annual commit, as of November 2026 where shown.
StackTypical license entryBest fitWatch-outs
Dynamics 365 Commerce (F&O)$210 user or $30 attach, plus $4,000 e-Commerce tenant add-on, plus devicesMulti-store retail, order management, deep F&O, headless and MCPTenant add-on floor; Scale Unit and device complexity; implementation weight
Business Central plus ShopifyBC $80 to $110 per user, plus the Shopify plan and connectorSmall and mid-size retail, lighter order routing, fast digital channelTwo platforms to integrate; less native enterprise order management
Odoo Standard (eCommerce and POS)$24.90 per user per month in year one, all appsCost-bound omnichannel retail with moderate complexityLess enterprise order management and Microsoft ecosystem depth
Commerce attach on an existing Finance or SCM base$30 per user, plus add-ons and devicesCompanies already running F&OQualifying-base rules; confirm on a CSP quote

Business Central native webstore: there isn't one

Business Central does not include a native web storefront. Microsoft's documentation for the connector says you need a Shopify account and a Shopify online store, and that the Shopify Connector app is preinstalled for new Business Central sign-ups and trials. That connector is the documented path for a Business Central company that wants to sell online.

Software cost on that path is Business Central users plus a Shopify plan, and Shopify's paid POS add-on if you want in-store selling. Check the plan amounts on Shopify's own pricing page for your country, because they change and this guide does not restate them. Commerce is the other Microsoft design: the storefront is a tenant add-on on the same pricing, inventory and promotions engine as POS and the call center. You do not upgrade Business Central into Commerce by installing an app, and the partner skills, back office and license math change with the product.

Worked comparison, with assumptions stated: 8 users, US list prices as of November 2026, yearly billing, tax ignored, Shopify plan excluded. Business Central Essentials is 8 x $80 = $640 per month. Eight Commerce users are 8 x $210 = $1,680, and the e-Commerce add-on adds $4,000, for $5,680 per month. Choosing the headless add-on instead gives $1,680 + $4,200 = $5,880. In Canada the same 8 users are CAD 868 on Business Central Essentials, and CAD 2,279.20 + CAD 5,427.20 = CAD 7,706.40 on Commerce with e-Commerce, before tax. Add the Shopify plan to the Business Central side before comparing.

  • Business Central: online selling is documented through Shopify, not a native webstore
  • Commerce: a retail application on the same headquarters platform as Finance and Supply Chain Management
  • One shared retail engine across store, web and call center points to Commerce; ERP plus a Shopify storefront points to Business Central
  • Business Central Team Members at $8 (CAD 10.90) are not Commerce register licenses

Is Dynamics 365 Commerce right for a company of 20 to 100 people?

Microsoft does not publish a revenue cutoff or a store-count gate for Commerce. The useful test is operational. If one location sells through a website and a simple till, the $4,000 or $4,200 per month tenant fee is a high floor before you add a single user. Business Central plus Shopify matches that shape, and it is the pattern Flectic scopes first for many companies in the 20 to 100 person range.

Commerce starts to fit when more than one selling surface must share inventory and promotions: stores, the website and a call center, sometimes a B2B catalog as well. It also fits when the company already needs Finance or Supply Chain Management class operations, because headquarters is built so those financials sit with commerce. It is a weak fit when the main pain is launching a marketing site quickly, or when Business Central already works as the system of record.

Use the license sketch before a demo. Count the Commerce users who configure products, take phone orders or run stores. Add one tenant add-on only after the reseller states whether e-Commerce, headless, both or neither applies. Then lay the Business Central plus Shopify total beside it. Odoo is the non-Microsoft option Flectic implements when a company wants ERP, point of sale and a web store as one application suite and is not committed to Dynamics. Services are extra on every path.

Decision criteria for companies of about 20 to 100 people. These are scoping tests, not Microsoft eligibility rules.
SituationPath to price firstWhy
One store or a simple web catalog; Business Central already covers financeBusiness Central plus ShopifyNo native Business Central webstore; Shopify is the documented connector. Avoids the Commerce tenant floor.
Stores, website and call center must share inventory, price and promotionsDynamics 365 CommerceOne Scale Unit runs those channels. Budget users plus the add-on written on the quote.
Multi-entity finance is the real project; retail channels come secondFinance first, Commerce only if the channels need itUS Finance lists at the same $210 per user as Commerce, and the Commerce page does not require Finance.
Cost is the binding constraint and retail complexity is moderateOdoo with eCommerce and POSOne subscription covers ERP, POS and the web store; compare against the Microsoft lists above.
You need sales pipeline or cases, not storesSales or Customer Service pricingSee the Sales pricing guide and the Customer Service pricing guide; neither buys Commerce.

What drives a 3-year Commerce TCO

Sticker price is the floor. Over a three-year horizon, a Dynamics 365 Commerce program's cost is driven by five levers that the pricing page never quantifies: the standalone-versus-attach mix, the device-to-named-user ratio across the store estate, the e-Commerce transaction tier, the separately licensed modules and Azure/search consumption, and, the largest single line for greenfield programs, implementation.

The attach mix is the biggest per-seat lever. A 30-user merchandising and operations team licensed standalone at $210 costs $75,600 a year; the same team attached to an existing Finance or Supply Chain Management base at $30 costs $10,800, a saving of $64,800 a year, repeated every year of the term. If your organization already runs Finance or Supply Chain Management, this one decision outweighs every other optimisation. The device-to-named-user ratio is the second lever: a 25-store estate with two POS terminals per store usually licenses 50 devices, not 50 named Commerce users, so ask your CSP to quote those devices against the $126,000 a year that 50 named users would cost.

Implementation is the line most retailers underestimate. A consistent industry rule of thumb, cited across implementation partners, is that for every dollar you spend on Dynamics 365 licenses, expect to spend roughly two to five dollars on implementation, depending on complexity, customization, and integration scope. Dynamics 365 implementation projects routinely range from around $25,000 for a simple scoped deployment to well over $1 million for a complex enterprise rollout with heavy integration. For Commerce specifically, where POS hardware, e-commerce theming, payment and tax engines, and ERP integration all converge, implementation tends toward the upper end of that band, which is why the worked TCO below treats it as the dominant one-off cost.

If you are pricing the finance side of the same program, the Finance and Operations pricing guide covers the F&O ladder, and the attach licenses guide explains which bases qualify. Total cost of ownership for Finance and Operations follows the same method as the worked cases below: license lines for the full term, add-ons, Azure consumption and a services line.

  • Five levers: attach mix, device-to-named-user ratio, e-Commerce tier, modules/Azure, implementation
  • Attach mix is the biggest per-seat lever: 30 standalone users vs 30 attaches is a $64,800 a year swing
  • For a multi-shift store estate, price device licenses against named users on the CSP quote
  • Implementation rule of thumb: $2 to $5 on implementation for every $1 on licenses; Commerce sits toward the upper end
  • Implementation scope: ~$25K simple to $1M+ complex enterprise, POS, e-commerce, payments, and ERP integration all converge

A worked cost case for a 5-store retailer

Take a retailer with 5 stores running two POS terminals each (10 devices), 20 named Commerce users across merchandising, operations and store management, and an online channel on the Tier 1 e-Commerce add-on. Partners commonly cite a 20-license minimum for Commerce, and Microsoft sets minimums in its Product Terms, so confirm it on the quote. All figures are USD list prices. The 10 device licenses are quoted by your CSP and sit outside the totals, and the formulas are shown so you can swap in your own counts.

Standalone: 20 users x $210 x 12 = $50,400 per year. e-Commerce: $4,000 x 12 = $48,000. That is $98,400 per year, or $295,200 over three years. With attach for the same 20 users: 20 x $30 x 12 = $7,200, which brings the annual total to $55,200, or $165,600 over three years. A POS-only rollout without the storefront costs $50,400 per year standalone and $7,200 per year with attach. Add the CSP quote for the 10 device licenses to each of these totals.

Implementation is the part to scope separately. Applying the partner rule of $2 to $5 of services for every $1 of annual licenses to the $98,400 case gives roughly $196,800 to $492,000. The same rule on the $50,400 POS-only case gives roughly $100,800 to $252,000. These are planning arithmetic, not quotes: a fixed-scope first phase can come in below the rule, and heavy integration can exceed it.

Annual Dynamics 365 Commerce license cost for a 5-store, 10-device, 20-user retailer. USD list prices, excluding the device licenses (quoted by your CSP), discounts, implementation and Azure.
Line item (per year)StandaloneAttach
20 Commerce users ($210 standalone vs $30 attach)$50,400$7,200
10 POS device licensesQuoted by your CSPQuoted by your CSP
e-Commerce add-on ($4,000 per tenant per month)$48,000$48,000
Annual licenses with storefront, before devices$98,400$55,200
Annual licenses, POS only (no storefront), before devices$50,400$7,200

A worked 3-year TCO for a 25-store retailer

A worked example makes the levers tangible. Take a mid-market retailer with 25 stores running two POS terminals each (50 devices), 30 named Commerce users across merchandising and operations, and an online channel doing roughly 2,500 transactions a month. We model two scenarios: standalone licensing (the retailer is new to F&O) and attach licensing (the retailer already runs Finance or SCM as its ERP). All figures are annual-commit list-price planning numbers in USD, negotiated partner and enterprise-agreement discounts routinely reduce them. The 50 device licenses are quoted by your CSP and sit outside the totals below.

In the standalone scenario, the 30 named users cost $210 x 30 x 12 = $75,600 a year. The e-Commerce add-on (Tier 1, covering up to 3,000 monthly transactions) costs $4,000 x 12 = $48,000 a year. That is $123,600 a year in licenses before the 50 POS devices, or $370,800 over three years. Add an estimated implementation at roughly 2.5 times annual license spend (a one-off of about $309,000, reflecting POS, e-commerce, payments and ERP integration) and steady Azure, CSU, search and per-tenant modules at about $2,000 a month ($72,000 over three years). The three-year TCO lands near $752,000 before the device quote.

In the attach scenario, the same 30 users attach to an existing Finance or Supply Chain Management base at $30 instead of $210: $10,800 a year instead of $75,600, saving $64,800 every year. Licenses drop to $58,800 a year ($176,400 over three years) before devices, implementation is lighter because Commerce layers onto an existing ERP (modelled at about $250,000), and Azure and modules stay similar. The three-year TCO lands near $498,000 before the device quote. The $210 to $30 swap saves $194,400 in licenses over three years, and the lighter implementation assumption accounts for the rest of the roughly $253,000 gap, which is why a licensing review should precede any retail implementation. For a broader frame on the full cost picture across platforms, the erp-total-cost-ownership guide covers the cross-platform TCO method.

  • Standalone 3-year TCO before devices: about $752K (licenses about $371K, implementation about $309K, Azure and modules about $72K)
  • Attach 3-year TCO before devices: about $498K; the $210 to $30 swap saves about $194K in licenses and the lighter implementation assumption the rest
  • Implementation is the dominant one-off line; lighter in the attach scenario because Commerce layers onto existing ERP
  • All figures are list-price planning numbers, negotiated discounts and exact device quotes change the total
3-year Dynamics 365 Commerce TCO planning model for a 25-store, 30-user, about 2,500-transaction-per-month retailer. USD list prices; the 50 device licenses are quoted by your CSP and excluded. Excludes negotiated discounts. Implementation per the partner rule of thumb ($2 to $5 per license dollar).
Line item (3-year total)Standalone scenarioAttach scenario
30 named Commerce users ($210 standalone vs $30 attach)$226,800$32,400
50 POS device licensesQuoted by your CSPQuoted by your CSP
e-Commerce add-on Tier 1 ($4,000/tenant/month)$144,000$144,000
Implementation (one-off)about $309,000about $250,000
Azure/CSU/search + per-tenant modules (3 years)about $72,000about $72,000
3-year TCO before devices (approx.)about $752Kabout $498K

Dynamics 365 Commerce implementation cost and phases

Microsoft does not publish a Dynamics 365 Commerce implementation price. Its FastTrack program gives eligible customers guidance, workshops and go-live reviews, but delivery labor is a separate quote from an implementer. The planning band in circulation is $2 to $5 of services for every $1 of licenses, with whole Dynamics 365 projects ranging from about $25,000 for a simple scope to over $1 million for complex enterprise rollouts. The two worked cases above apply that band to a 5-store and a 25-store chain.

Flectic sets the timeline for a first phase in the written scope, with a fixed price. That phase is one your staff can sell in; it does not cover every store, every historical order and every custom front end. The Flectic Accelerated Delivery Framework is designed to deliver up to 3x faster than a traditional phased ERP project, with a consultant reviewing each step.

The services quote is driven by visible work. Product and price data must be clean enough to publish to a channel. Each store needs a channel, registers, workers, payment methods and a Hardware Station where the lane uses drawers or printers. Windows devices are needed where offline selling matters. Distribution jobs must run so stores receive configuration, and staff need time on a staging environment that behaves like production. A sensible first phase for a company of 20 to 100 people is one legal entity, the stores that open on cutover day, shared pricing and inventory, and either the native storefront or a deliberate decision to stay on Shopify with Business Central.

Commerce implementation phases to ask an implementer to price. Durations are agreed in discovery.
PhaseWork that should be pricedLicense note
DiscoveryChannel map, fit against Business Central plus Shopify, data samples, success measuresNo Commerce seats are needed to finish a written recommendation
Headquarters and Scale UnitLegal entity, cloud or self-hosted Scale Unit, tax, payments, delivery modesCommerce users for the people who configure; add-on only if the quote includes a storefront
Stores and POSStore Commerce on the right operating system, Hardware Station, offline test, payment gatewayDevices follow the Operations license rules, not the Commerce price card
Data and acceptance testingProducts, prices, customers, stock; scripts for sale, pickup and returnCRM seats only if sales or service teams join the program
Cutover and hypercareFinal load, channel activation, floor support, fixes after the first selling daysFlectic stays through launch stabilization

Dynamics 365 Commerce vs Odoo cost for a 25-store retailer

Flectic implements both Microsoft Dynamics 365 and Odoo, so the answer is sometimes Dynamics 365 Commerce and sometimes Odoo at a much lower per-user cost. As of October 2026, Odoo's Standard and Custom plans include all apps, eCommerce and point of sale among them, for a single per-user fee. Odoo lists Standard at $24.90 per user per month on yearly billing in year one, then $31.10. That is Odoo's license price, not a Flectic fee.

Take 30 retail users. Odoo Standard at $24.90 comes to 30 x $24.90 x 12 = $8,964 per year in year one. Thirty standalone Commerce users at $210 come to $75,600 per year, before the $4,000 per tenant e-Commerce add-on and device licenses. Odoo's price covers the apps, and implementation is extra on both sides. The gap narrows when the retailer already holds a qualifying Dynamics 365 base and licenses Commerce as a $30 attach.

What the extra Commerce spend buys is depth in Microsoft's ecosystem: distributed order management, integration with Finance and Supply Chain Management, the Power Platform, and headless and MCP agent channels. Choose Commerce if you already run Finance or Supply Chain Management, need that order management, or have standardized on Microsoft. Choose Odoo if per-user cost is the binding constraint, you want eCommerce, POS and ERP under one subscription, and your retail rules are moderate. For the full Odoo price breakdown, read the Odoo pricing guide.

  • Odoo Standard: $24.90 per user per month in year one on yearly billing, then $31.10; includes eCommerce and POS
  • 30 users: about $8,964 per year on Odoo Standard in year one vs $75,600 per year for 30 standalone Commerce users, before add-ons and implementation
  • Choose Dynamics 365 Commerce for distributed order management, Finance and Supply Chain integration, Power Platform and headless channels
  • Choose Odoo if per-user cost is the binding constraint and retail rules are moderate
  • Flectic implements both, so the recommendation follows your scenario

How Flectic can help

Flectic implements Dynamics 365 and Odoo for retailers and e-commerce companies of 20 to 100 people in the US and Canada, and prices Commerce against Business Central plus Shopify and Odoo before you commit. We connect your POS, eCommerce, inventory and finance so each unit is counted once. A consultant reviews the license mix, attach eligibility and add-on tier against your store estate, and Flectic sends a written proposal with a fixed price for each phase before work starts. Read how we approach ERP for retail and e-commerce, then Book a free discovery call.

Sources

  1. As of November 2026, Dynamics 365 Commerce is $210.00 per user per month, the e-Commerce add-on is $4,000.00 per tenant per month and the headless add-on is $4,200.00 per tenant per month, all paid yearly. Microsoft states the prices are informational and the checkout price applies.

    microsoft.comChecked 2026-11-08
  2. The Dynamics 365 Licensing Guide (November 2026) prices Commerce as an attach at $30 per user per month on a Finance, Finance Premium, Supply Chain Management or Supply Chain Management Premium base, and defines the Operations Device and Activity licenses.

    go.microsoft.comChecked 2026-11-08
  3. Commerce Cloud Scale Unit (CSU) capacity tiers: Basic ≈ 3,000 e-commerce transactions/month or 65 POS devices; Standard ≈ 10,000 transactions or 225 devices; Premium ≈ 25,000 transactions or 500 devices. e-Commerce add-on tiers align (3K / 10K / 25K) with overage increments.

    linkedin.comChecked Verified August 2026, Commerce licensing explainer documenting CSU and e-Commerce tier structure; consistent with Microsoft licensing decks.
  4. Commerce Scale Unit (CSU) Core hosts the Commerce Runtime, headless commerce engine, and channel-side retail services for POS, e-commerce, and call-center clients; cloud CSU runs in Azure.

    learn.microsoft.comChecked Verified August 2026, Microsoft Learn CSU Core overview.
  5. Dynamics 365 Commerce MCP server (preview) exposes headless commerce tools (catalog, cart, inventory, orders, promotions) to MCP-compatible AI agents on the same CSU as other channels.

    learn.microsoft.comChecked Verified August 2026, Microsoft Learn Commerce MCP documentation (published June 2026).
  6. Microsoft Copilot supports product and marketing content authoring in Dynamics 365 Commerce Site Builder; cloud-powered search uses Azure AI Search integrated with Commerce channels.

    microsoft.comChecked Verified August 2026, Microsoft Commerce Copilot announcement; Azure search integration also documented on Microsoft Learn cloud-powered search.
  7. Dual-write provides near-real-time interaction between customer engagement apps and finance and operations apps; F&O license entitlement covers replication but not CE app use rights or unlimited Dataverse capacity.

    learn.microsoft.comChecked Verified August 2026, Microsoft Learn dual-write overview.
  8. Improved assigned-license validation for Dynamics 365 Finance and Operations apps (including Commerce) rolls out from January 2026 based on renewal timelines; unlicensed users can lose access after enforcement windows.

    encorebusiness.comChecked Verified August 2026, Encore Business summary of Microsoft improved user license validation; AlphaBOLD 2026 licensing guide also notes Nov 2025 / Jan 2026 enforcement timeline.
  9. As of November 2026, Business Central Essentials is $80, Premium is $110 and Team Members is $8 per user per month in the US, paid yearly.

    microsoft.comChecked 2026-11-08
  10. For every dollar spent on Dynamics 365 licenses, expect to spend roughly two to five dollars on implementation; implementation projects range from ~$25,000 for simple scoped deployments to over $1 million for complex enterprise rollouts.

    reachinternational.aiChecked Verified August 2026, Reach International D365 cost breakdown; implementation band corroborated by AlphaBOLD, Velosio, and Houseblend TCO analyses.
  11. Microsoft raised prices on several Dynamics 365 apps (including a large Commerce increase in the 2024 wave) and partners continue to flag 2025 to 2026 license and attach planning against current Product Terms.

    msdynamicsworld.comChecked Verified August 2026, MSDynamicsWorld coverage of D365 price increases (Commerce among apps with large prior jumps).
  12. Practitioner and partner chatter on X emphasizes license-stack surprises (attach vs full, device estate, CSU) and SOW clarity over sticker price; Commerce Scale Unit Basic Cloud is sold as a discrete NCE SKU.

    x.comChecked Verified August 2026, X post listing Dynamics 365 Commerce Scale Unit Basic Cloud (NCE) as a licensed SKU; aligns with CSU as a separate capacity line.
  13. As of November 2026, Canada Commerce list prices are CAD 284.90 per user per month, CAD 5,427.20 per tenant per month for the e-Commerce add-on and CAD 5,698.50 per tenant per month for the headless add-on, paid yearly, plus applicable tax.

    microsoft.comChecked 2026-11-08
  14. As of November 2026, Canada Business Central is CAD 108.50 Essentials, CAD 149.20 Premium and CAD 10.90 Team Members per user per month, paid yearly, plus applicable tax.

    microsoft.comChecked 2026-11-08
  15. Connecting Business Central to Shopify requires a Shopify account and a Shopify online store; the Shopify Connector app is preinstalled for new Business Central sign-ups and trials.

    learn.microsoft.comChecked
  16. Store Commerce runs on Windows, iOS, Android and macOS; Store Commerce for web runs in Edge and Chrome and cannot access POS hardware directly or work offline; Store Commerce for Windows has built-in offline mode and a local Hardware Station; Modern POS was deprecated in October 2023; the Commerce Scale Unit can be deployed in the cloud or in the store.

    learn.microsoft.comChecked
  17. Odoo Standard and Custom plans include all apps, including eCommerce and POS, for a single per-user fee. Flectic's ERP comparison tool lists Odoo Standard from $24.90 per user per month.

    odoo.comChecked

Frequently asked questions

How much does Dynamics 365 Commerce cost per user?

As of November 2026, the standalone Dynamics 365 Commerce license is $210.00 per user per month in the United States and CAD 284.90 in Canada, paid yearly, per Microsoft's Commerce pricing pages. If the user already holds Finance or Supply Chain Management, standard or Premium, the same workload is available as an attach for $30 per user per month, per the Dynamics 365 Licensing Guide.

What does Dynamics 365 Commerce cost in Canada?

Microsoft's Canada page lists Commerce at CAD 284.90 per user per month, the e-Commerce add-on at CAD 5,427.20 per tenant per month and the headless add-on at CAD 5,698.50 per tenant per month. All three are paid yearly, plus applicable tax. Microsoft notes the amounts are informational and the checkout price applies.

Is Dynamics 365 for Retail the same as Commerce?

Dynamics 365 for Retail is the earlier name of the product Microsoft now sells as Dynamics 365 Commerce. Microsoft's current pricing pages show one Commerce card, $210 per user per month in the US, and no separate Retail SKU. Price any Retail-era proposal with the current Commerce lines.

What is the Dynamics 365 Commerce e-Commerce add-on and what does it cost?

The e-Commerce add-on switches on e-commerce management and costs $4,000.00 per tenant per month, paid yearly, in the US. It is licensed per tenant, not per user, and needs at least one Commerce base or attach license. Capacity is sized by transaction tier: up to 3,000, 10,000 or 25,000 transactions per month, with overage in 500-transaction increments.

What is Dynamics 365 Commerce attach pricing?

Attach pricing lets a user who already holds Finance or Supply Chain Management (standard or Premium) add Commerce for $30 per user per month instead of the standalone $210. The core Commerce capabilities are the same, and platform and storage entitlements stay with the base. The Dynamics 365 Licensing Guide (November 2026) sets the price and the qualifying bases.

How do I license point-of-sale (POS) devices in Dynamics 365 Commerce?

Shared POS terminals are licensed with an Operations Device license assigned to the device, so any number of staff can use it across shifts, and lighter-use named staff can use an Activity license. Microsoft publishes no list price for either; your Cloud Solution Provider quotes them. The Scale Unit device cap is a capacity entitlement, so being under it does not exempt a terminal from a device license.

When should I choose Dynamics 365 Commerce vs Business Central with Shopify?

Choose Commerce when you need enterprise distributed order management, deep F&O inventory integration, many stores on Store Commerce, or headless channels on one engine. Choose Business Central ($80 to $110 per user per month in the US) plus Shopify when order-routing needs are moderate and the $4,000 tenant add-on would dominate a small online channel. If you already run Finance or Supply Chain Management, Commerce attach often beats rebuilding retail depth on Business Central.

How much does a Dynamics 365 Commerce implementation cost?

Microsoft publishes no implementation price. A common partner planning band is $2 to $5 of services for every $1 of annual licenses, and whole Dynamics 365 projects run from about $25,000 for a simple scope to over $1 million for complex rollouts. Commerce tends toward the upper end because POS, storefront, payments, tax and ERP integration converge in one project, so get a scoped quote.

Is Dynamics 365 Commerce cheaper than Odoo for retail?

On per-user license cost, no. Odoo's Standard and Custom plans include eCommerce and POS with the other apps in one per-user fee, from about $24.90 per user per month. Thirty Odoo users run about $8,964 per year, against $75,600 per year for 30 standalone Commerce users before add-ons. Commerce wins on enterprise order management and Microsoft ecosystem depth for established retailers, especially those already on F&O.

What is a Commerce Scale Unit (CSU) and does it cost extra?

The Commerce Scale Unit hosts the Commerce Runtime and the headless services used by POS, e-commerce, call center and agent clients. One is typically provisioned with the e-Commerce or device licenses, and higher volume may need additional Basic, Standard or Premium capacity SKUs from a partner price list. A cloud Scale Unit also drives Azure consumption, and a self-hosted one adds no Microsoft license fee, though every user and device must still be licensed.

More on the blog: Choosing an ERP or CRM