For two decades, ERP change management has been organized around dates. A go-live date. A hypercare window. Two release waves a year that gave program teams something to plan against: a regression testing window, a training push, a communications cycle, a steering committee slide. The calendar was never just a schedule. It was the operating model.
That calendar is now being withdrawn. Microsoft has confirmed it is retiring the twice-yearly release wave model for Dynamics 365, Power Platform, and Dataverse in favor of continuous publishing, with capabilities appearing as soon as plans are committed. At DAX Software Solutions, this reads less as a documentation change than as the end of a planning assumption most Microsoft Dynamics 365 change programs were quietly built on.
The Calendar Was Doing More Work Than Anyone Admitted
Release waves gave organizations a permission structure. Twice a year there was a legitimate reason to convene the business, freeze scope, book trainers, and ask users for their attention. Take that away and three implicit things become explicit problems:
- Attention had a schedule. Communication was timed to a known event. Without the event, no one owns the moment.
- Testing had a trigger. Regression cycles were justified by a wave. Continuous delivery removes the trigger but not the need.
- Governance had a forum. The wave review was where business owners saw what was coming. Nothing automatically replaces it.
What Is Changing in the Microsoft Release Model?
Microsoft is moving from two batched annual release waves to continuous publishing, so roadmap information arrives as capabilities are committed rather than twice a year.
The delivery cadence was already faster than the wave narrative suggested:
- The Finance and Operations apps — including Dynamics 365 Finance and Supply Chain Management — receive four service updates a year, with customers required to take a minimum of two and able to pause only one update at a time.
- Business Central online receives two major updates a year alongside monthly minor updates, governed by a defined update period, a grace period, and then an enforced period.
The waves were a communications rhythm layered over a delivery model that had already moved on. What is disappearing is the rhythm, not the change.
The Real Cost of Treating Change as an Event
The tempting response is administrative: update the bookmarks, subscribe to the roadmap feed, ask the ERP manager to check it monthly. That is cheap and insufficient.
The evidence on adoption predates this shift. Gartner research published in July 2025 found that only 32% of mid-to-senior business leaders reported healthy change adoption on their most recent initiative, and that 79% of employees hold low trust in organizational change. Gartner’s framing is blunt: “The nature of change today has made it ungovernable.” For an ERP estate, that shows up as costs that never appear on a change management budget line:
- Silent workarounds. Users meet altered behavior, don’t understand it, and rebuild the process in a spreadsheet outside the system.
- Support load that looks like defects. Tickets rise after updates land, and the organization diagnoses a quality problem when it has an adoption problem.
- Configuration drift. Capabilities arrive un-adopted and un-assessed, widening the gap between what the platform can do and what the business uses.
Gartner also ties adoption to the top line: organizations with better-than-average healthy change adoption see roughly twice the year-over-year revenue growth of those below average. Adoption is a performance variable, not a soft metric.
Agentic AI Makes the Gap Wider
The change now arriving in ERP is no longer only about screens and fields. It increasingly concerns agents and embedded intelligence that participate in finance and operations work — surfacing exceptions, proposing matches, routing decisions.
That change has a different shape. A field that moves is visible; a recommendation that shifts is not. When behavior changes rather than layout, screenshots and click-path training stop carrying the load. What users need is a clear understanding of what the system is deciding, what it is not, and where a human still has to sign.
This is why autonomy and governance have to be funded together. Frameworks such as the NIST AI Risk Management Framework, organized around its Govern, Map, Measure, and Manage functions, treat AI-related risk as an ongoing discipline rather than a launch checklist. The standard worth holding is controlled intelligence with human oversight, not uncontrolled automation.
Building a Change Capability That Does Not Need a Calendar
Nothing external will replace the wave calendar. The rhythm has to come from inside the organization, and it rests on four decisions.
- Separate the capability from the vendor’s schedule. Name a permanent owner for platform change in the business applications function, and fund it as run cost rather than project cost so it survives go-live.
- Routinize change instead of announcing it. Gartner found that when leaders routinize change rather than trying to inspire it, employees are roughly three times more likely to adopt it healthily and on time.
- Instrument adoption, not availability. Track adoption of capabilities actually enabled, post-update ticket patterns separated from genuine defects, and workaround prevalence.
- Govern agent behavior the way you governed releases. Define where an agent may act, where it may only recommend, and where a human must decide.
Continuous change is only absorbable on a stable base. Where master data is inconsistent, integrations are point-to-point, and process ownership is unclear, a faster cadence amplifies the existing problem.
DAX helps clients build that base and that capability:
- Dynamics 365 Managed Services — ongoing support, monitoring, optimization, and enhancement, so continuous platform change is monitored by a named team rather than a dissolved project.
- AI Readiness Assessment — evaluating ERP stability, data quality, governance, and integration before change velocity increases.
- Human-in-the-Loop Operating Models and Data Governance Frameworks — defining where agents act, where people decide, how oversight is evidenced, and who owns the data underneath.
What Leaders Should Do in the Next 90 Days
Days 1 to 30 — visibility. Assign the owner, subscribe the team to the continuous roadmap, and inventory the Dynamics 365 applications and update cadences you actually run.
Days 30 to 60 — assessment. Define how a roadmap item is triaged for business impact, and stand up a monthly business-owner review in place of the wave review.
Days 60 to 90 — response. Set the routine communication pattern, define the adoption metrics you will report upward, and confirm the governance rules for agent-driven change.
DAX Software Solutions: Your Partner in Continuous ERP Change
The organizations that struggle over the next two years will not be the ones that failed to read a roadmap. They will be the ones that kept treating change as an event after the events stopped.
DAX Software Solutions helps organizations modernize Dynamics 365 environments and build the operational foundations — governance, data quality, integration, and managed support — that make continuous change absorbable. If your ERP change management model still assumes two moments a year, this is the moment to redesign it.
Contact Us → DAX Software Solutions