The Dynamics 365 Licensing Guide has moved to a new edition again. Microsoft's own PDF metadata timestamps this file's creation at August 27, 2026, and both the cover page and the "What's new in this licensing guide?" summary box on page 2 read September 2026, which is the label we'll use going forward. The guide holds steady at 90 pages, unchanged from August's edition, which we last checked in on August 3.

We check this edition-to-edition the same way every time: compare Appendix K's Change Log, on page 89 in this edition, against the prior edition we archived. This time it logs exactly one new entry.

The one new entry: Headless Commerce reaches General Availability

PageApplicationChangeStatus
15 Commerce New Headless Commerce General Availability

Headless Commerce add-ons let an organization build a custom digital storefront or third-party integration against Dynamics 365 Commerce's API layer, instead of Commerce's own retail server, cloud point-of-sale website, and channel database. Two add-on SKUs went generally available with this edition:

Add-on SKUWhat it supportsBase capacityOverage capacity
Headless import Importing completed retail transactions captured outside Dynamics 365 Commerce 30,000 retail transaction imports/month, plus one Commerce Scale Unit – Cloud (Headless Commerce scenarios only) 5,000 retail transaction imports/month
Headless orchestration Capturing retail transactions from third-party clients via the Commerce APIs directly 30,000 retail transactions/month, plus one Commerce Scale Unit – Cloud (Headless Commerce scenarios only) 5,000 retail transactions/month

Both capacities are enforced in aggregate annually, not on a hard monthly cutoff, and the guide doesn't publish per-add-on dollar pricing directly; it points to Microsoft's own Commerce pricing page for current figures, consistent with how it treats every other capacity add-on.

Why this one is actually worth reading if you're an F&SC shop

The last two editions of this series were quiet ones for Finance and Supply Chain Management specifically, both new capabilities landed in Customer Insights, an application licensed and priced independently of F&SC. This one is different. The guide's own description of the Headless Commerce add-ons states plainly that they "facilitate native integration with Dynamics 365 Finance and Dynamics 365 Supply Chain Management."

ℹ Why this matters for licensing, not just architecture

If your organization runs Commerce alongside F&SC, a headless storefront changes how retail transactions reach your ERP, not whether they need a license, but potentially which kind of access path they travel through to get there. We've seen this exact pattern drive real license cost before: in one of our published case studies, the single biggest lever on a client's bill wasn't their security roles at all, it was whether an integration authenticated as a named person or as a service account. A new, officially sanctioned integration surface between Commerce and F&SC is exactly the kind of change worth checking against that same question before it's built, not after.

To be clear about what did not change: Finance and Supply Chain Management's own entitlement tables, use rights, and security-role documentation are identical to the August edition, and pricing for both applications is unchanged at $210 per user/month for the base tier and $300 for Premium. Nothing about a user's own license requirement moved. What changed is the sanctioned integration surface between Commerce and F&SC, which is an architecture decision with the same kind of licensing consequence we've already documented once.

Month over month

AreaAugust 2026September 2026
New Change Log entries 2 (both Customer Insights, Paid Public Preview) 1 (Commerce, General Availability)
Finance / SCM pricing $210 / $300 per user/month Unchanged
F&SC entitlement tables Unchanged since June Unchanged
Documented F&SC-adjacent integration surface None Headless Commerce add-ons, per the guide's own text
Guide length 90 pages 90 pages

If you're mid-review right now, nothing you've documented against the August edition needs revisiting for a licensing number. What's worth a closer look, if Commerce and F&SC coexist in your environment, is whether anyone's planning to build against this new headless surface, and if so, how that integration is going to authenticate. We check this guide every time we sit down to write, so a genuinely F&SC-relevant change gets its own coverage the moment we catch it, rather than waiting for the next monthly slot.