リリースウェーブを超えて：「AI at Work」ロードマップへの移行Moving beyond release waves with the AI at Work roadmap

Microsoft is changing how it communicates and delivers updates for its core business applications, announcing that Dynamics 365, Power Platform, and Dataverse will move away from the long-standing twice-yearly release wave model and into a single, continuously updated schedule branded the AI at Work roadmap. The shift matters because release waves have shaped how enterprises, administrators, and implementation partners plan deployments for years, and a move to rolling updates changes those planning rhythms.

Historically, Microsoft published two release waves each year for Dynamics 365 and the Power Platform. Release wave 1 broadly covered features arriving in the first half of the year, while release wave 2 covered the second half. Each wave was accompanied by detailed plans, often released weeks or months in advance, that listed upcoming features, general availability dates, and early access windows. That cadence gave organizations a predictable framework for evaluating, testing, and adopting new capabilities, and it became a fixed reference point in many IT and partner planning cycles.

Under the new approach, the company is consolidating these products into an always-on roadmap where features are surfaced and shipped on a continuous, rolling basis rather than grouped into semiannual bundles. The AI at Work name signals that the roadmap is being organized around artificial intelligence, and in particular the Copilot and agent capabilities that Microsoft has been embedding across its business software. Bringing Dynamics 365, Power Platform, and Dataverse together under one roadmap appears intended to present a more unified view of where these interconnected products are heading.

The three products involved are closely linked, which helps explain why they are being combined. Dataverse is the shared data platform that underpins both Power Platform and Dynamics 365, providing a common store and security model. Power Platform includes low-code tools such as Power Apps, Power Automate, and Power BI, along with Copilot Studio for building conversational agents. Dynamics 365 spans business applications for areas including sales, customer service, finance, and supply chain. Because features in one layer often depend on or extend another, a single roadmap is likely meant to reduce fragmentation in how updates are announced and tracked.

The change reflects a broader industry trend toward continuous delivery of cloud software. As AI features are developed and refined at a faster pace than a six-month planning cycle can easily accommodate, fixed biannual bundles can appear out of step with how quickly capabilities actually ship. Microsoft is not alone in this direction; other enterprise vendors integrating generative AI into their platforms have similarly emphasized more frequent, incremental updates rather than large scheduled releases. Framing the roadmap around AI also aligns these business applications with Microsoft's wider Copilot strategy, which spans Microsoft 365, GitHub, and other products.

For customers and partners, the practical implications will depend on execution. A continuous roadmap can make it easier to see new capabilities as they become available, but it may also require organizations to adjust governance, testing, and change management processes that were built around the predictable April and October waves. Teams that relied on the detailed release wave documents for advance planning will likely need to monitor the always-on roadmap more regularly to stay current. How Microsoft handles communication, versioning, and administrator controls under the new model will be an important factor in how smoothly the transition lands.

It is worth noting that a shift in how updates are packaged and announced is distinct from a change in the underlying features themselves. The move consolidates the schedule and presentation of Dynamics 365, Power Platform, and Dataverse updates rather than replacing the products or their functionality. Organizations should watch for further detail on how early access, general availability timing, and regional rollout will be represented now that the fixed wave structure is being retired.

Overall, the announcement positions AI as the organizing principle for Microsoft's business applications roadmap and signals a durable move toward rolling delivery. Whether the continuous model proves easier to follow than the release wave cadence will become clearer as the roadmap matures and as customers adapt their planning to a schedule without fixed semiannual milestones.