Insights · Blog · Licensing · May 8, 2026
Microsoft published sixteen documented changes to the Dynamics 365 license model between October 2025 and May 2026. We read the Licensing Guide so you don't have to — and classify which of the changes are commercial and which are cosmetic.
The May 2026 Licensing Guide for Microsoft Dynamics 365 has been out for two weeks, and anyone who has to deal with licensing in the Microsoft ecosystem knows the ritual: download PDF, open Appendix K, read the change log, verify in the main body what the abstract lines concretely mean. We do this publicly here — with assessment. Not every change in the guide is equally relevant. Some are corrections, some are structural changes, and a few actually move money.
Two weeks ago we had an existing customer with about 80 Sales Premium and 40 Customer Service Premium licenses who asked us whether they needed to adjust anything after the update. The answer was: no, but they should cancel one of their running Copilot Studio pre-purchase agreements. The reason is in the November 2025 entry of the change log. More on that below.
What follows is not a 1:1 translation of the Microsoft document. It is the annotated reading of a Microsoft Partner that has been configuring the same licenses for years. Sources cited with page references to the official guide.
What it is. Since November 2025, the four Premium SKUs — Sales Premium, Customer Service Premium, Finance Premium, and Supply Chain Management Premium — each include 1,000 Copilot Credits per user per month. Previously, these were separate SKUs. Microsoft consolidated them. Concretely: anyone with a Premium license also has a credit budget for Dynamics 365 agents and Copilot Studio workloads (Licensing Guide May 2026, p. 41).
What it is not. The standard licenses — Sales Enterprise, Customer Service Enterprise, Finance, Supply Chain Management, Sales Professional, Customer Service Professional — get no credits. These must continue to be purchased separately via pay-as-you-go, pre-purchase, or the Copilot Credit Pack subscription path.
What this means for existing customers. Anyone with Premium who additionally buys Copilot Credits should calculate. Whoever has 50 Sales Premium users gets 50,000 credits/month in the tenant. That covers most realistic agent usage scenarios we have seen so far — from Sales Opportunity agent to account research workflows in Copilot Studio.
What this means for new customers. Premium is often the cheaper option compared to Enterprise + Copilot add-on now, as soon as agent usage is more than symbolic. We wrote a separate article about this — 1,000 Copilot Credits in Premium licenses — is the surcharge worth it?. Short answer: from about 2,000 credits monthly consumption per user.
For Microsoft Dynamics 365 Business Central, two agents have been formally GA since November 2025: Sales Order Agent and Payables Agent. From public preview to full sale status, which means: you can now work productively with them, they are anchored in the product terms, and they cost Copilot Credits. Before November, Sales Order Agent was a beta, with all the expectation limits attached. Not anymore.
We tested the Sales Order Agent at a wholesaler in Hesse last quarter — with a simple task: automatically convert incoming email orders into BC orders. Technically works, but fails on data hygiene. Anyone who has customer records with three spellings for the same customer also fails here. The agent doesn't do data cleansing. Obvious, but not clear from the marketing demos.
For existing customers: anyone with Business Central Premium has a platform on which these agents technically run. The credits must come separately — because BC Premium is (unlike the D365 Premium SKUs of the CE/F&O world) not in the Copilot Credit inclusive program. That's an important asymmetry we regularly have to explain in the Business Central service area.
In November 2025 Microsoft increased the default capacity for BC Essentials, Premium, and Device (Licensing Guide May 2026, p. 45). That's the kind of change that appears in marketing materials as an "improvement" and in reality only ensures that the price increase hurts less. Both happen in parallel: more capacity, higher list prices. Net for most mid-market companies: slight surcharge, hardly any practical consequence.
We consider capacity increases without TCO comparison fundamentally not meaningful. Anyone licensing BC newly today should run the License Cost Calculator through with concrete user numbers, add-ons, and capacity wishes, rather than do table comparisons.
In October 2025, the overarching Dynamics 365 Agents platform went GA (Licensing Guide May 2026, p. 39). This includes the cross-product agents — so not only the BC-specific ones, but also those in Customer Service, Field Service, Sales, and ERP. In parallel, further agents are available in Paid Public Preview (Appendix B, p. 54).
Important regarding licensing: anyone who wants to use a Dynamics 365 agent needs two things — a valid license for the associated application (e.g., Customer Service) and enough Copilot Credits, because every agent action burns credits. A Sales Opportunity agent without a Sales license is not allowed. A Payables agent without a BC license neither. The Microsoft logic: agents extend an existing application, they do not replace it.
The Sales Opportunity Agent moved from public preview to GA status in April 2026 (p. 33). What it does: it prioritizes opportunities based on behavior signals, pipeline stage, and deal history. What it doesn't do: structured sales coaching tasks that replace a human sales manager. Anyone who wants to use it productively needs Sales Premium or Sales Enterprise + Copilot Credits.
We currently have it in pilot operation at a machinery builder. Half the sales reps find the recommendations plausible, the other half find them too conservative. That's a typical sales AI pilot picture and has to do with data depth, not with the agent.
Microsoft renamed two Project Operations editions:
This is a marketing unification. Functionally nothing changes, license prices stay, use rights identical. But: anyone who maintains training materials, internal wikis, or customer portals with the old names should adjust this, otherwise it gets confusing in the next audit at the latest.
Until September 2025, Copilot for Sales and Copilot for Service were stand-alone add-on SKUs. Since October 2025, they are included by default in the Microsoft 365 Copilot license (pp. 39 and 40). This is a consumer-friendly change — anyone who has M365 Copilot now gets the formerly separately sold Sales/Service extensions for free.
Consequence: anyone who historically paid for these separately should have the contract reviewed. In most CSP settings, Microsoft automatically consolidated the licenses, but for Enterprise Agreements with older contract states, a look is worthwhile.
Microsoft Dynamics 365 Guides and Microsoft Dynamics 365 Remote Assist have not been sellable since November 2025. Existing licenses expire, new licenses are no longer available. Both products were mixed-reality applications for industrial service scenarios — primarily for HoloLens. HoloLens sales ended back in 2024, the end-of-sale for the software stacks was foreseeable.
Anyone who still has licenses here: migrations towards Field Service with classic mobile apps or Copilot Studio agents are feasible, but not trivial. We sketched this once for a plant builder — the effort was about 30 days of customization for 80 active service technicians. Not free.
In March 2026, Microsoft increased the default and accrued Dataverse Database Capacity as well as the Dataverse File Default Capacity for Sales Premium (p. 46). So anyone with Sales Premium licenses gets more storage per user. That is a small improvement, primarily relevant for large setups with many attachments, OneNote notes, or document generation workflows.
In practice, this means: anyone who has been buying capacity add-ons because storage limits were tight should check again before the renewal date whether the add-ons have now become superfluous. Micro optimization, but with 200+ licenses, that can be four- to five-figure amounts per year.
In February 2026, Microsoft introduced the Model Context Protocol (MCP) for Dynamics 365 (p. 41). That is one of the more substantial changes in the update — and at the same time the one with the biggest license consequence for architectures that want to work with their own AI agents.
Briefly summarized: MCP is an open protocol with which AI agents — also outside the Microsoft ecosystem, such as Anthropic Claude or your own Foundry agents — can access Dynamics 365 data. In Copilot Studio, MCP usage incurs no extra charges. Outside Copilot Studio, you need a valid license that covers data access — Premium licenses for D365 data, M365 Copilot USL for non-D365 data, otherwise billable as Copilot Credits.
We have a separate article on this — Model Context Protocol for Dynamics 365 — what MCP means for your AI architecture. Anyone planning their own LLM agents on Microsoft data should read this before every architecture workshop.
Microsoft updated the Field Service and Project Operations integration (pp. 24, 53). Concretely, it's about the data model handover from Field Service work orders into Project Operations transactions. If you use both modules productively — typical in plant engineering and service engineering settings — your customization should be reviewed before the next release wave update hits.
Two sub-modules of Dynamics 365 Commerce have not been sellable since February 2026: Commerce Recommendations (AI-driven product suggestions) and Commerce Ratings & Reviews (customer reviews). Anyone using this productively in web shops or POS setups should talk to the Microsoft account team about migration paths — Microsoft has not named 1:1 successors in its own stack.
That is a remarkable decision. Recommendation engines are a central differentiation tool in e-commerce. Microsoft seems to no longer aggressively develop Commerce as a product line. We consider this a symptom — not the cause. More on this in our ERP knowledge articles.
Since January 2026, Dynamics 365 Contact Center Voice supports Teams Phone extensibility (p. 14). That opens the voice channel architecture for Teams Phone integrations — for example, if you want to use Teams Phone as a telephony backend for your customer service center. License consequence: none directly, but Teams Phone subscriptions need to be licensed separately and must match the Contact Center Voice plan.
In December 2025, Microsoft adjusted the Dataverse and Operations capacity structures (p. 44). Concretely: default capacity was increased, some capacity pools were consolidated. Anyone who historically had a fragmented capacity add-on landscape can simplify here. That's one of the inconspicuous changes that become relevant in practice when you do a larger tenant audit.
Newly added in the current May 2026 Guide: a Procurement Agent in Paid Public Preview (p. 56). It replaces the previous Supplier Communications Agent. That's the only new public preview addition in the May 2026 update — and the only change likely to become structurally relevant in the next twelve months for Supply Chain Management customers.
What it's supposed to do: automated supplier communication around purchase orders, order status inquiries, complaints. Public preview means: usable, but chargeable, without SLA guarantees. Anyone with Supply Chain Management Premium can test it with the 1,000 Copilot Credits / user / month without extra effort.
Additionally, Microsoft refined use rights for Team Members in several places in the update — particularly in the Project Operations, Finance, and Supply Chain Management areas (Appendix C, multiple entries between July 2025 and November 2025). That is administratively relevant because Microsoft closed gray zones here that were historically often misinterpreted. Read our Team Members compliance article on this — it's worth it.
Also, security role names in Commerce were changed (October 2025), and the term "Shop Floor" was replaced by "Production Floor" (February 2026). Both pure nomenclature, without license effect.
Three things stand out above all other changes — when we break this down to consequences for ongoing projects:
What we at arades concretely recommend to most existing customers: a compact license review once every six months — based on the current Licensing Guide, the actual license inventory, and the next twelve months of project roadmap. Not every Microsoft change is worth actively reacting to. But every one is worth being understood once before it becomes unpleasant in the renewal conversation.
If you are unsure whether the May 2026 update is relevant for your license inventory, write to us. A first review based on your license overview typically takes 30 to 45 minutes — free of charge in the initial conversation.
More on the strategic classification of licensing under Microsoft Dynamics 365 licensing, pricing & cost. We deepen concrete sub-topics from the May update in the articles linked below.
30-min initial conversation · free
A pragmatic first review of your current license configuration against the May 2026 update — we'll tell you whether there's adjustment or optimization need.
Related articles
May 8, 2026 · Licensing
Microsoft has a licensing mechanic we find misconfigured at every third client. It's called Base + Attach.
May 8, 2026 · Licensing
Premium SKUs have included 1,000 credits/user/month each since November 2025. Calculate economically — from what usage does it pay off?
May 8, 2026 · Licensing
Team Members is the cheapest D365 license — and the most common violation source in the German mid-market. What the license allows, what not.
May 8, 2026 · Licensing
MCP was introduced in February 2026. License consequences for anyone planning their own AI agents on D365 data.
