Microsoft replaces release waves with one continuous AI-at-Work roadmap

Microsoft is consolidating the public release plans for Dynamics 365, Power Platform and Dataverse into its AI-at-Work roadmap, replacing the familiar twice-yearly release-wave document with a continuously updated view of features in development, rolling out or launched.[1]

The company announced the change on 25 August and said new items would begin appearing in September. Existing Power Platform and generally available Dynamics 365 items with dates from 1 June 2026 onward are scheduled to move during a September-to-November transition. Release Planner is expected to retire by 15 November.[1]

For Malaysian IT, operations and finance teams, this is less a product launch than a change to the evidence used for planning. Microsoft explicitly said the communication model is changing, not the way products deploy. A roadmap status therefore remains a vendor signal; it does not prove that a feature has reached a specific tenant, passed local controls or works with local customisations.[1]

The former release-wave cycle gave teams a predictable moment to read a large plan, identify relevant features and schedule testing. Microsoft's new model is intended to show changes continuously across Microsoft 365, Copilot, Security, Dynamics 365, Power Platform and Dataverse. That reduces fragmentation, but it also removes the comfort of treating two planning exercises each year as sufficient release governance.[1]

The new roadmap supports product, platform, release phase and cloud-instance filters, along with full-text search. Microsoft also highlights CSV export, RSS feeds and shareable links. Those tools can make monitoring more systematic, provided teams turn them into an owned process rather than expecting every product administrator to notice changes independently.[1]

Microsoft said items would be migrated in stages. During the transition, information may appear in both Release Planner and the AI-at-Work roadmap. Saved views from Release Planner will not carry over, so administrators who rely on custom filters need to recreate them. The company advises customers to review existing saved views before the old planner is retired.[1]

A sensible Malaysian implementation is small and auditable: inventory every saved view, record its owner and business purpose, rebuild only the views still used, and document the replacement feed or link. Teams should also verify that RSS or exported data is being consumed, because a technically configured feed that nobody reads is not a release-control process.[1]

The three public states are helpful but broad. In Development means Microsoft is actively building a feature. Rolling Out means release has started and availability can still vary. Launched means the feature is generally available, but organisations still need to check geography, cloud instance, licensing, configuration and dependencies. None of those labels confirms that a local business process is ready to change.[1]

That distinction matters for low-code apps, customer systems and financial workflows where an unexpected interface or automation change can affect staff or records. Each relevant roadmap item should become a local decision: ignore, observe, test or adopt. High-impact changes need a sandbox check, named business owner, rollback path and evidence from the organisation's own tenant before production use.[1]