Dynamics 365 Release Planner retires by November 15

Microsoft is retiring Release Planner and stopping publication of Dynamics 365 and Power Platform release plans. If you have ever built an upgrade plan around a release wave document, the thing to get right first is which of three similarly-named things is actually going away.

Three names, one retirement, and only one of them is affected

• Release waves — the twice-yearly servicing cadence. Not retiring. Products still ship on waves and versions still carry end-of-servicing dates.
• Release plans — the published documents on Microsoft Learn describing what is coming in each wave. Stop being published from September 2026.
• Release Planner — the tool for browsing and filtering those plans. Retires by November 15, 2026.

If your organisation runs Business Central on-premises, that first bullet is the one that matters most. The servicing clock on Business Central — version 26.x out of servicing on October 13, 2026, version 25.x already gone since April 4 — is entirely unaffected by this announcement. Those dates keep running. It would be an expensive misreading to conclude otherwise from a headline about release plans retiring.

The two dates, and why they are not equally firm

Microsoft's Learn hub for release plans:

“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.”

Microsoft's announcement blog, written by Richard Riley, General Manager for Agents and Low Code:

“By November 15, 2026, The transition completes and Release Planner retires. The AI at Work roadmap becomes the primary destination for public roadmap information.”

⚠️ Note the word "by". That is a completion target, not a switch-off. And note where it appears: the November date is on the blog, not on the Learn hub — the hub gives September for publication ending and says nothing about November at all. If you are citing a date in a change record, cite the blog and quote it as written, because the documentation page will not corroborate it.

"Until further notice" is the part to plan around

The sentence most likely to matter to a regulated firm is the quiet one: “Existing release plans will remain available for historical reference until further notice.”

That is an intention rather than a commitment, and it has no date attached in either direction. If a change-control record, an upgrade runbook, a project plan or a supplier document cites a release plan URL as its justification, that citation now depends on a page Microsoft has explicitly declined to guarantee. Nothing breaks today. But "until further notice" is the phrasing organisations use immediately before a date exists.

This is a small, cheap thing to fix and an annoying thing to fix retrospectively: where a document needs to show why a change was made, a link is weaker evidence than a quotation. Copy the relevant text into the record rather than pointing at it.

What changes about planning, in practice

A release plan was a twice-yearly, dated, per-wave document: here is what is coming between April and September, organised by product, with dates. A continuously updated roadmap is a different artefact. It is more current and less snapshot-able.

For most mid-market organisations that is a mild improvement and a small process change. For anyone whose upgrade governance is built on "we reviewed the wave 1 plan on this date and made these decisions", it removes the thing being reviewed. The fix is to decide what you now review, and when, before September rather than after. A roadmap that always reflects today is excellent for awareness and awkward for a quarterly governance cycle that needs a fixed version of the truth.

The naming is a signal, and we would read it as one

This next part is our reading rather than Microsoft's statement. The destination is not called the Dynamics roadmap or the Business Applications roadmap. It is the AI at Work roadmap, and Dynamics 365, Power Platform and Dataverse are described as joining it.

Three separate product families losing their own forward-looking publication and being folded into a roadmap named after a strategy is the kind of change that usually precedes packaging and positioning changes rather than following them. We are not predicting anything specific and there is nothing in the announcement that says more than it says. But if you are making a multi-year commitment to a Business Applications platform this year, it is worth noticing which story Microsoft has decided these products are part of — and asking your account team about it while the question is cheap.

What we would do this week

• Search your documentation for release plan links. Change records, runbooks, project plans. Anything citing a Learn release-plan URL as evidence.
• Replace links with quotations where the document needs to justify a decision. Cheap now, impossible later if the page moves.
• Say out loud, to whoever owns Dynamics change control, that release waves are not affected. The headline invites the opposite conclusion and the correction is one sentence.
• Point the governance cycle at the AI at Work roadmap and agree a review cadence. An always-on source needs a decision about when you look, because it no longer tells you when it changed.

Sources

The September date and the "until further notice" wording come from Microsoft's release plans hub on Learn (updated_at 2026-08-27). The November 15 date comes from Microsoft's announcement blog, published August 25, 2026 by Richard Riley, General Manager, Agents and Low Code. Both were read in full on September 5, 2026. We checked whether the Learn hub carries the November date and it does not, which is why the two are attributed separately above.

If you would rather have the documentation audit and the governance-cadence change handled as a bounded piece of work, scope it with us.