Dynamics 365 Release Plans: What Customers Need to Change
Reading Time: 3 minutes
Microsoft is retiring its traditional Dynamics 365 and Power Platform Release Plans and moving new capability announcements to the always-on AI at Work roadmap. The change makes continuous release monitoring, impact assessment and regression testing even more important.
Instead, new capabilities will appear through Microsoft’s AI at Work roadmap, creating what Microsoft describes as an always-on roadmap.
Existing release plans will remain available for historical reference.
At first glance, this looks like a change in documentation.
For organisations running Dynamics 365 Finance, Supply Chain Management or other business-critical Microsoft applications, it has wider implications.
Release planning is becoming less about reviewing a document twice a year and more about continuously understanding what is changing.
What is actually changing?
Microsoft’s familiar release-wave plans grouped upcoming features into six-month periods. The 2026 release wave 1 plan, for example, covered features planned for Dynamics 365 between April and September 2026. Those published Release Plans are now being retired.
Future feature information will instead appear in the AI at Work roadmap.
This does not mean Microsoft has stopped updating Dynamics 365 or that every existing product-update cycle disappears.
Business Central, for example, still follows a six-month release-wave cycle, while Finance and Supply Chain Management have their own service-update processes.
The change is primarily about how Microsoft communicates upcoming capability. But that can still change how customers need to manage their environments.
Why does this matter?
For many organisations, the release-wave document provided a natural point to stop and review what Microsoft was introducing. Teams could examine the planned features, identify what mattered and decide what needed testing.
An always-on roadmap makes that process more continuous. Organisations running Dynamics 365 now need a reliable way to:
- monitor upcoming Microsoft changes;
- identify which features affect their environment;
- understand whether changes are automatic, optional or require action;
- assess extensions and integrations;
- decide which business processes need regression testing;
- prepare users and support teams;
- monitor production after deployment.
That is especially important where Dynamics supports finance, supply chain, warehousing or other critical processes.
The challenge is not knowing that Microsoft has changed something
The harder question is:
What does the change mean for our environment?
A new Microsoft capability may have little impact on one organisation. For another, it could affect:
- a customised process;
- an integration;
- an ISV application;
- security roles;
- batch processing;
- reporting;
- testing;
- user training.
That is why release management should not simply mean reading Microsoft’s roadmap. It should connect Microsoft’s product changes to the organisation’s own technology and business processes.
DigX’s recent Dynamics 365 SCM 10.0.48 update illustrates the point. The important task is not simply listing new features. It is deciding which changes affect existing processes, integrations and extensions before they reach production.
Regression testing becomes even more important
A continuously changing cloud ERP needs a repeatable testing process.
When an update could affect procurement, finance, inventory or warehousing, organisations need confidence that their important end-to-end processes still work. That means knowing what needs to be tested before the change arrives.
For example:
Purchase order → goods receipt → supplier invoice → financial posting
or:
Sales order → warehouse processing → dispatch → invoice
Testing should also include the integrations around Dynamics, not just the application itself. A technically successful Microsoft update can still create a business problem if a connected process fails.
This strengthens the case for continuous release management
The change to Microsoft’s roadmap reflects a wider reality. Dynamics 365 is not software that organisations implement and then leave unchanged for several years. It’s a cloud platform that continues to evolve.
The operating model therefore needs to evolve with it. That means release management should become part of normal business-as-usual support, alongside:
- environment management;
- integration monitoring;
- testing;
- incident management;
- change control;
- continuous improvement.
DigX’s Managed Services include Dynamics 365 release and change management, environment support, testing and ongoing monitoring.
For organisations using Dynamics 365 Finance and Supply Chain Management, this type of continuous oversight becomes more important as Microsoft’s product roadmap becomes more dynamic.
The practical question for Dynamics 365 customers
The retirement of the old Release Plans does not require organisations to redesign their entire Dynamics operating model. But it is a useful reason to review it.
Ask:
Who monitors Microsoft’s roadmap?
Who decides which changes matter to us?
Which processes must be regression tested?
Who owns testing across Dynamics and connected systems?
How do we communicate upcoming change to the business?
How do we know an update has not affected a critical process?
If the answers depend on somebody remembering to check Microsoft’s website every few months, the process may no longer be strong enough. The new model points towards a simpler principle:
Dynamics 365 release management needs to be continuous because the platform itself is continuously changing.
For more background on where Finance and Supply Chain Management fit within the wider technology estate, see DigX’s Dynamics 365 F&SCM guide.
Need help managing Dynamics 365 change, testing and updates?
Talk to DigX about Dynamics 365 Managed Services and release management.
Frequently asked questions
Is Microsoft ending Dynamics 365 release waves?
Microsoft is retiring the traditional published Release Plans from September 2026. This should not be confused with the end of all underlying product release or service-update cycles.
What replaces Dynamics 365 Release Plans?
Microsoft says new Dynamics 365, Power Platform and Dataverse capabilities will be published through its AI at Work roadmap.
Will old Dynamics 365 release plans disappear?
Microsoft says existing plans will remain available for historical reference until further notice.
What does this mean for Dynamics 365 customers?
Customers should have an ongoing process for monitoring new capabilities, assessing their impact, planning testing and managing changes into production.
Does this affect Dynamics 365 Finance and Supply Chain Management?
Yes. New capabilities for Finance and Supply Chain Management will be communicated through the new roadmap model, while their underlying service-update and operating requirements continue.
