Starting in September 2026, Microsoft is retiring the release wave 1 and release wave 2 model that has governed how it discloses upcoming Dynamics 365, Power Platform and Dataverse capabilities, replacing it with continuous publishing. There will be no September 2026 Release Wave 2 plan.
New capabilities will appear as they become committed. New release plans will also stop appearing on Release Plans on Microsoft Learn once the change takes effect, though existing plans stay online for historical reference. Release Planner itself is being retired, and personalized saved views built inside it will no longer be available once it goes.
Why This Changes Planning for Dynamics 365 Customers
Release wave 1 and release wave 2 gave organizations a fixed, twice-yearly moment to gather stakeholders and plan for upcoming ERP and business application changes. That moment functioned as a built-in checkpoint on governance calendars, a date IT and business teams could count on for reviewing what was coming before it arrived.
Microsoft’s guidance calls for organizations to build their own recurring review, monthly or quarterly depending on how quickly they adopt new capabilities, using a saved filter paired with an RSS subscription. Because Release Planner is retiring alongside the wave model, the personalized saved views many teams relied on to track relevant features disappear as well. That review cadence has to be rebuilt on the new roadmap’s filtering and RSS tools.
One Roadmap, More Connected Products
Dynamics 365, Power Platform and Dataverse roadmap content is moving onto the AI at Work roadmap, giving customers one destination to discover upcoming capabilities, track rollout progress and plan adoption across Microsoft’s business applications, productivity and AI portfolio. Microsoft frames the consolidation around how customers actually operate: few organizations run a single Microsoft product in isolation, and Dynamics 365, Power Platform, Microsoft 365 and Copilot increasingly work together to power business processes and AI transformation.
The roadmap reflects that interdependence. Entries covering new agentic capabilities across Dynamics 365 manufacturing, including a Procurement Agent designed to help sense demand and supply risk earlier, sit alongside general availability milestones for Agent 365 and updates to Microsoft 365 Copilot, all inside the same continuously updated view.
Making Release Data Usable by AI
Microsoft is also making the roadmap itself queryable by AI. The Microsoft Release Communications MCP Server is a remote server using streamable HTTP transport that lets MCP-compatible AI clients search, filter and retrieve the latest feature release information in natural language. It exposes tools for pulling recent roadmap items and Azure updates, with underlying data refreshing daily, and it spares users from having to learn a schema or write a query just to find out what is coming next.
Tools such as Visual Studio Code, GitHub Copilot CLI and other MCP-compatible clients can connect to the server, letting IT admins and engineers ask about upcoming features, rollout timelines and product changes directly inside their working tools instead of checking a website. The AI at Work Roadmap admin guidance positions this as one piece of a larger model that also includes an enhanced Message Center and a second server, Microsoft MCP for Enterprise, which gives AI agents conversational, read-only access to an organization’s own Message Center and Service Health Dashboard data.
None of this changes when features actually ship. Microsoft is changing how it communicates releases, not the underlying product deployment schedules, and RSS and Message Center continue to notify customers as changes occur. Message Center remains the source for changes specific to a given tenant.
What This Means for SAPinsiders
Governance calendars lose a built-in checkpoint. Teams that scheduled Dynamics 365 or Power Platform planning around the twice-yearly release wave now need to design and staff their own monthly or quarterly review, built on saved filters and RSS feeds rather than a fixed vendor date.
Roadmap review now spans the full Microsoft stack. Architecture and procurement teams evaluating Dynamics 365 must track a combined view spanning Power Platform, Dataverse, Microsoft 365 and Copilot, since a single-product roadmap no longer captures where the platform is heading.
AI agents can now query release data directly. Governance teams should set policy for MCP-connected AI clients that can pull roadmap and rollout information automatically, shifting part of change monitoring from manual review toward agent-assisted queries that still need human oversight.
