TL;DR
Microsoft stopped publishing Dynamics 365 release plans in September 2026 and moved new capability to the AI at Work roadmap. Existing plans stay up.
Microsoft stopped publishing them in September 2026. New Dynamics 365, Power Platform and Dataverse capability now goes to the AI at Work roadmap instead. The existing plans stay online for historical reference — so nothing you bookmarked is gone, but nothing new will appear there either.
What exactly changed, and when?
The notice appears on the release-plan pages themselves. Quoted exactly:
"Release Plans will no longer be published starting in September 2026. New Dynamics 365, Power Platform, and Dataverse capabilities will be published to the AI at Work roadmap beginning in September 2026. Existing release plans will remain available for historical reference until further notice."
Three specifics worth pinning down:
| Question | Answer |
|---|---|
| When | September 2026 — this is in effect now |
| What replaces it | The AI at Work roadmap, at aka.ms/AIatWorkRoadmap |
| What happens to old plans | "remain available for historical reference until further notice" |
| Scope | Dynamics 365, Power Platform and Dataverse — not one product |
Microsoft points to a post titled "One always-on roadmap: Dynamics 365, Power Platform and Dataverse join the AI at Work roadmap" for the reasoning, at aka.ms/ReleasePlannerMigrationBlog.
Do the old release plans still work?
Yes, and they remain the authoritative record of what was promised and when.
"Until further notice" is the operative phrase — Microsoft has committed to keeping them available without committing to how long. If your implementation notes, upgrade plans or customer commitments cite a release-plan URL, those links still resolve today, and the wave pages still carry their own warning that "delivery timelines may change and projected functionality may not be released."
The practical risk is not broken links. It is a stale habit — checking a source that has stopped updating and reading absence as "nothing new shipped."
What did the final wave actually record?
An unusual amount, and most of it is agents. The 2026 release wave 1 page for Business Central — covering April through September 2026 — lists these as having reached general availability, each with a released date rather than a projection:
Agent platform and MCP:
- Create agentic experiences with enhanced MCP server — GA 1 April 2026
- Unlock more Business Central data with MCP server enhancements — GA 12 June 2026
- Enable Troubleshooting MCP Server for AL — GA 1 May 2026
- Connect AI agents to the admin center through MCP server — public preview 1 April 2026
The agent fleet:
- Manage tasks from all agents in dedicated task pane — GA 1 April 2026
- Review content generated by agents directly on pages — GA 1 April 2026
- Stop all active tasks for selected agent — GA 1 April 2026
- Run multiple Sales Order Agents per company with smarter item matching — GA 8 July 2026
- Speed up processing with Known Senders in Payables Agent — GA 7 August 2026
- Try Payables Agent for free without setting up email — GA 6 July 2026
- Manage expenses in Business Central using Expense Agent — public preview 8 May 2026, with a mobile capture preview on 1 July 2026 and travel requisitions listed for September 2026
Developer surface for agents:
- Attach to and debug Business Central agent sessions — 3 April 2026
- Use AI agent tools for AL development — 3 April 2026
- Control content filtering and XPIA when extending Copilot in the AI development toolkit — 3 April 2026
- Evaluate AL coding agents with BC-Bench — GA 1 April 2026
And two that matter more than they look:
- External storage support for document attachments — GA 1 April 2026
- Use new APIs for analyzing approval workflows for auditors and IT staff — GA 14 June 2026
Read that list as a whole. In a single wave, Business Central shipped a generally available MCP server, a task pane spanning every agent, a third first-party agent, debugging for agent sessions, and a benchmark for AL coding agents. This is not Copilot features being added to an ERP. It is an agent platform.
What does the change actually signal?
That capability now ships faster than a twice-yearly document can describe it.
A wave plan is a six-month promise published in advance. That format assumes a release cadence slow enough to forecast, and the list above — with general-availability dates in April, May, June, July and August — does not fit it. An always-on roadmap is the honest format for software that ships monthly.
Two consequences for anyone building on Dynamics:
- Status labels get harder to trust from memory. Preview and generally available now change between the time you read something and the time you quote it, and there is no wave boundary to anchor on. Check the feature page, not your notes.
- The planning horizon shortens. Committing a customer to a capability that is "coming in wave 2" was always risky; without waves, the safest commitment is what is generally available today.
This is the same discipline that already applied, made unavoidable. Microsoft's own warning on every wave page — "projected functionality may not be released" — was the rule; the format change just removes the illusion that a published plan was a schedule.
So what should you actually do?
Four things, none of them urgent, all of them cheap:
- Move your bookmark to the AI at Work roadmap. The old pages stop being a source of new information from this month.
- Re-check any status label you are relying on — in a proposal, a statement of work, or a customer commitment. Read the feature page and record the date you read it.
- Keep the release-plan URLs you have cited. They still resolve and they are the historical record of what was promised.
- Assume the agent surface will keep moving. The wave above shipped a generally available MCP server and a third first-party agent in six months.
For anyone building on top of Dynamics, the last point is the one that matters. A generally available MCP server means the ERP is now addressable by language models as a matter of course rather than as a project — and that changes what an app beside the ERP is for. The sidecar app stops being an integration and starts being a participant.
About Cognilium Cognilium builds AI optimization apps for Microsoft Dynamics 365 — companion apps that optimize the pricing, inventory, warehouse and planning decisions your ERP manages but can't optimize. Dynamics is your system of record. Cognilium is your system of intelligence. https://cognilium.ai · https://www.linkedin.com/company/37180269/
Agentic ERP. We build turnkey AI optimization apps for Dynamics 365 — sidecar applications that run in your own Azure tenancy and solve the calculations a standard ERP is not built to compute. That family includes the Demand & Inventory Optimizer and Contract Review Copilot, and it includes the MCP middleware that lets a language model act inside Dynamics rather than only read from it. Built on Azure OpenAI, Microsoft Fabric and Copilot Studio.
If you are re-checking status labels across a proposal this month, bring the list to a 15-minute call and we will go through what is actually generally available.
Sources
- New and planned features for Dynamics 365 Business Central, 2026 release wave 1 ·
ms.date2026-09-01, updated 2026-09-03 - Envision and design AI agents in Business Central ·
ms.date2026-06-09 - Payables Agent Overview — Business Central ·
ms.date2026-05-03
Sources and fact-check
| # | § | Claim | Tier | Primary source | Verdict |
|---|---|---|---|---|---|
| 1 | 1 | "Release Plans will no longer be published starting in September 2026", the AI at Work roadmap, and "remain available for historical reference until further notice" | T1 — verbatim ×3 | 2026 wave 1 planned-features page, fetched 2026-09-10 | PASS — load-bearing |
| 2 | 1 | Scope is Dynamics 365, Power Platform and Dataverse | T1 — verbatim | Same notice | PASS |
| 3 | 1 | The linked post title and the two aka.ms short links | T1 — verbatim, link text copied exactly | Same notice | PASS |
| 4 | 2 | Wave pages warn "delivery timelines may change and projected functionality may not be released" | T1 — verbatim | Same page | PASS |
| 5 | 3 | Sixteen named features with their GA or preview dates | T1 — read directly from the release-plan tables, feature names copied as published | Same page | PASS — every date taken from the table, none from memory |
| 6 | 3 | "This is not Copilot features being added to an ERP. It is an agent platform." | T2 — ours, a characterisation of the list, labelled as ours | — | PASS — opinion, and marked |
| 7 | 4 | The format change reflects a faster cadence | T2 — ours. Microsoft's stated reasoning is in a post we did not open, so this is our inference and is not attributed to them | — | PASS — explicitly not put in Microsoft's mouth |
| 8 | 4 | Status labels are harder to trust without wave boundaries | T2 — ours, practical guidance | — | PASS |
| 9 | 5 | The four recommended actions | T2 — ours, method | — | PASS |
| 10 | 5 | A GA MCP server changes what a sidecar app is for | T2 — ours, capability framing, no product claim, no customer, no metric | — | PASS |
Tier summary: 5 × T1 (all verbatim or read from the published tables), 5 × T2 — 0 × T4.
Claim 7 is the one to watch and it is deliberately restrained. Microsoft published a post explaining the change — "One always-on roadmap" — and we did not open it. So the article says what the change signals to us, never what Microsoft said it signals. The reasoning is ours and is labelled ours. Anyone extending this article should fetch that post first.
Every date in §3 was read from the release-plan tables on 2026-09-10, not recalled. Feature names are reproduced as Microsoft titles them, including BC-Bench and XPIA.
Status labels. Features are described as generally available or public preview exactly as the table marks them. Expense Agent is described as preview throughout and never as shipped.
No figures of ours. Every number is a Microsoft date. No digits appear in either lifted block.
More on this: AI for legal operations on Dynamics 365 and SAP.
