At a glance

  • From September 2026, Microsoft discloses Dynamics 365 changes on one always-on roadmap as they’re committed, replacing the two release waves a year.
  • The Release Planner retires on November 15, 2026, and there is no 2026 release wave 2.
  • Updates still arrive on Microsoft’s schedule, and some features switch on for users automatically.
  • Control comes from a named owner, a test copy of your business, and a short note to users before each change lands.

For a COO, the risk is a Monday morning when the dispatchers’ screen looks different and nobody told them. A CFO faces a new agent feature using credits nobody budgeted, and a CIO loses the planning rhythm the team relied on.

A standing practice with a named owner handles all three.

What changed is how you hear about changes

On August 25, 2026, Microsoft announced that it would stop publishing new release plans for Dynamics 365, Power Platform, and Dataverse. New capabilities now appear on the AI at Work roadmap as they’re committed, marked In Development, Rolling Out, or Launched.

The transition runs from September to November. The Release Planner retires on November 15, 2026, and Microsoft has confirmed there is no 2026 release wave 2.

Updates keep arriving.

Microsoft’s guidance says the customer engagement apps and Power Platform get minor service updates weekly, region by region. The finance and operations apps take at least two and up to four service updates a year, in February, April, July, and October. You can pause one consecutive update to fit your own schedule.

So planning moves from a twice-a-year event to a monthly habit.

Give the update calendar one owner, with the business at the table

Microsoft says its single-version model doesn’t remove your responsibilities. You still plan each update, assign the tasks, tell people what’s coming, and support adoption. Microsoft also says preparing takes the admins, the project team, and the business users who champion the system.

In practice, name one release owner, usually the platform admin. Pair them with an operations lead who knows what a change means on the floor.

Hold a monthly review. Check the roadmap items for the apps you run, the notices Microsoft sends admins through the message center and email, and any removal dates. Give each item one of three decisions: ignore it, test it, or plan for it.

Microsoft offers an RSS feed of the roadmap, and a Release Communications MCP server that brings roadmap data into your own tools. Software can draft the monthly list; the owner decides what reaches your people.

If a managed-services partner helps, it should run this cadence alongside your owner.

Test in a copy of your business before it reaches your people

Microsoft lets you try production-ready, fully supported features early in a sandbox. For the customer engagement apps, it recommends a new environment copied from your test environment and opted in to early access. You can also set a sandbox to the monthly release channel.

Test with your own data and your own processes. Run the regression tests, and write down every screen or navigation change a user will notice. For the finance and operations apps, Microsoft recommends taking updates early in the user acceptance test environment and running automated regression tests there.

Adopt one of Microsoft’s timing rules as policy. Don’t turn on early access in the same window as one of your own releases to production. If something breaks, you want to know which change caused it.

Tell people what changes on their screen before it changes

Some changes arrive without waiting for you. Microsoft sorts features into three groups: some turn on automatically for users, some turn on automatically for admins and makers, and some need an admin to switch them on. Each item in the release notes says which group it’s in.

The automatic ones need a note to the people affected, sent before the change lands. Microsoft’s own example is a large call center, where every second on a call counts. One paragraph per role is enough: what looks different, what to do, and who to ask.

The features an admin must switch on are your choice. Turn them on when the business and the training are ready.

A removal notice needs a plan the day it arrives

Microsoft announces features marked for removal with a timeline. They keep working and stay supported until the removal date, and then they stop. The time between the notice and the date is your budget window.

The clearest current case is the Field Service integration with the finance and operations apps, which won’t be available after February 28, 2027. Microsoft is moving the capability to the Field Service and Project Operations integration. Our guide to that deadline covers how to sequence the move.

Agents change what a regression test has to cover

A configured screen either behaves the same after an update or visibly breaks. An agent can keep running and start giving different answers. Success by Design tells teams to keep watching agent output after launch, including changes in model behavior after platform updates, and to re-run evaluations on a regular schedule.

Status matters too. Microsoft says public preview features aren’t meant for production use. The Field Service Scheduling Operations Agent is still in preview, so keep it out of production processes until it’s generally available.

Cost belongs in release control as well. Every Dynamics 365 agent consumes Copilot Credits, and Copilot Studio agents are switched off above 125 percent of prepaid capacity. When a new agent capability goes live, the release owner and finance should both know what it will use.

Some teams need less, and some need more

If you run one app with standard features and supported customizations, Microsoft expects updates to have little or no effect on it. A monthly look at the roadmap and a test before each finance and operations update may be enough.

Regulated manufacturers need more: a standing regression and validation cadence, budgeted as a running cost. And if you run other vendors’ apps on top of Dynamics 365, you have two sources of updates. Microsoft advises coordinating each vendor’s timing well ahead, so there’s time to regression-test the whole solution.

What operations and IT leaders should do this quarter

Name a release owner and a business partner. Put a monthly review on both calendars.

Point your planning to the AI at Work roadmap before November 15. Plans that rely on the Release Planner will lose their source.

Keep a test copy of your business on early access. Run your regression tests there before each change reaches production.

Send a one-paragraph note per role before automatic changes land. Say what looks different, what to do, and who to ask.

Put agents in the test plan and the budget. Re-run evaluations after updates, and review credit use with finance.

How we know this

This guide comes from Ludia’s Dynamics 365 delivery and managed services. Roadmap change: Microsoft, One always-on roadmap: Dynamics 365, Power Platform, and Dataverse join the AI at Work roadmap (Aug 25, 2026), and the AI at Work roadmap. Update cadence, early access, feature groups, removals, and the call-center example: Microsoft Learn, Stay current with Dynamics 365 service updates (July 2026). Agent monitoring: Introduction to the Success by Design framework (Aug 2026). Integration end date: Field Service integration with finance and operations applications (Sept 2026). Agent status: Microsoft, Dynamics 365 announcements (Sept 23, 2026). Credits: Dynamics 365 Licensing Guide (Sept 2026) and Copilot Studio capacity management. Vendor apps: Extend Dynamics 365 apps without compromising performance. Regulated manufacturers: ERP Today (Aug 26, 2026).