The announcement
Microsoft has placed Dynamics 365, Power Platform, and Dataverse under one always-on AI at Work roadmap. The move ends the practice of delivering updates in discrete release waves for these three offerings. The change was posted on the Microsoft Source site on August 25, 2026.
Prior structure
Release waves had given customers a repeating calendar of major updates. Teams could map internal projects, training, and testing cycles to those fixed dates. The new arrangement treats AI-driven features as a steady stream rather than a series of bundled drops. The post carries the title “Moving beyond release waves with the AI at Work roadmap” and states that the three services now share the single roadmap.
What the post says
The announcement contains no feature list, no dates for specific capabilities, and no migration timeline. It simply records the decision to consolidate the three products onto the existing AI at Work path. Readers are directed to that roadmap for future updates. No additional technical specifications appear in the source.
Reactions and counterpoints
No customer statements, partner reactions, or competing announcements have surfaced in the provided material. The post stands alone as the record of the change.
Why it matters
Customers who built upgrade plans, budget cycles, and training programs around the twice-yearly wave schedule now lose that external clock. They must instead track an open-ended feed whose pace is set inside Microsoft. For organizations that treat release notes as project milestones, the shift removes a predictable checkpoint and replaces it with continuous monitoring of the AI at Work site.
Teams that coordinate across multiple Microsoft services face an added layer of alignment work. Previously, a single wave document covered several products on the same date; now each capability arrives when it is ready, and the only common reference is the shared roadmap. This can shorten the gap between development and availability, but it also removes the natural pause that waves once provided for documentation, testing, and internal communication.
The absence of concrete dates or feature details in the announcement itself means that planning documents must now point to an external page rather than a published wave schedule. Administrators who once printed or archived wave PDFs will need new processes for capturing changes as they appear. Over time this may reduce administrative overhead, yet it also concentrates more responsibility for staying current on the teams that consume the updates.
For smaller organizations without dedicated Microsoft relationship managers, the change increases reliance on public channels. Larger enterprises with formal change-management offices will likely create internal dashboards that pull directly from the AI at Work feed. In both cases the old rhythm of “wave one this month, wave two that month” disappears.
The decision reflects a broader pattern in which AI features are released as soon as they meet internal quality bars rather than waiting for the next wave boundary. Whether that produces faster value or simply faster change depends on how quickly each customer can absorb incremental updates. The source supplies no data on adoption speed or customer readiness, so the practical effect remains to be measured in the field.
The strongest signal in the announcement is the removal of a familiar planning anchor. Every team that once aligned its own calendar to Microsoft’s release waves must now decide what replaces that anchor.
---
Sources:
{"word_count": 612, "sources_used": 1, "expansion_focus": "implications and planning impact"}
No comments yet