AnswersPublished25 sources
Microsoft’s AI at Work Roadmap Replaces Release Waves With Continuous Updates
Microsoft renamed the Microsoft 365 Roadmap to the AI at Work Roadmap on August 25, 2026, with Dynamics 365, Power Platform, and Dataverse content due in September. Release Planner is scheduled to retire on November 15, 2026, while older release plans will remain available for historical reference.
Published byEdited with GPT-5.6 LunaImages generated with GPT Image 1.5
Research answer
Key takeaways
- Microsoft renamed the Microsoft 365 Roadmap to the AI at Work Roadmap on August 25, 2026, with Dynamics 365, Power Platform, and Dataverse content due in September.
- Release Planner is scheduled to retire on November 15, 2026, while older release plans will remain available for historical reference.
- IT teams should replace wave based planning with recurring reviews of filtered roadmap views, RSS feeds, and—where supported—natural language queries through Microsoft’s Release Communications MCP Server.
AI Prompt
openai.comCreate a landscape editorial hero image for this Studio Global article: What does Microsoft’s rebranding of the Microsoft 365 Roadmap as the “AI at Work Roadmap” involve—including the replacement of all existing. Article summary: Microsoft has turned a product-specific roadmap into a single, continuously updated release tracker branded around workplace AI. The operational change is more significant than the rename: Dynamics 365 and Power Platform. Topic tags: general, general web, user generated. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, charts with fak
Microsoft has changed more than the name of its product roadmap. On August 25, 2026, the Microsoft 365 Roadmap became the AI at Work Roadmap, and Microsoft plans to add Dynamics 365, Power Platform, and Dataverse content beginning in September. 2
5
The stated goal is a single place to track planned capabilities across Microsoft’s productivity, business applications, low-code, and AI portfolio. For administrators and enterprise planners, however, the more consequential change is the retirement of Dynamics 365’s twice-yearly release-wave model. Microsoft is moving toward continuous publication instead of packaging updates into Release Wave 1 and Release Wave 2 announcements. 3
5
7
What is changing
The renamed roadmap will cover Microsoft 365, Copilot, agents, and related AI-powered experiences, then expand to include:
- Dynamics 365
- Microsoft Power Platform
- Microsoft Dataverse
- Microsoft 365 and its commercial features
- Copilot, agents, and other related experiences
Microsoft says organizations increasingly deploy these products together. Its argument is that a unified tracker will make it easier to discover upcoming capabilities, monitor rollout progress, and coordinate adoption across products that may be managed by different teams today. 5
The change is primarily to the information architecture and publishing model. Microsoft says users will continue accessing the roadmap as before; the new destination is intended to consolidate planning information rather than create a separate product experience. 20
Release Wave 2 is not coming in September 2026
Dynamics 365 and Power Platform customers have traditionally used semiannual release waves to organize planning around two major disclosure points. That model is being retired.
Microsoft’s published release-plan guidance says new Dynamics 365, Power Platform, and Dataverse capabilities will be published to the AI at Work Roadmap beginning in September 2026, and that release plans will no longer be published from that point onward. Existing plans will remain available for historical reference. 7
As a result, there will be no September 2026 Release Wave 2 plan. New capabilities will instead appear when Microsoft considers the plans committed and ready to share, rather than waiting for a scheduled wave announcement. 3
9
That creates a clear trade-off:
- Potential benefit: information can appear throughout the year instead of being held for a major wave publication.
- Planning cost: customers no longer receive the same fixed-date, consolidated snapshot for preparing budgets, testing, training, and adoption plans.
The new model may provide fresher information, but it shifts more responsibility for finding and interpreting changes to the customer.
Release Planner is being retired
Release Planner is scheduled to retire on November 15, 2026. Its role will be absorbed into the AI at Work Roadmap, which becomes the central destination for the newly combined roadmap content. 1
3
Existing release plans are not being erased immediately. Microsoft says they will remain available for historical reference, giving teams a way to review earlier commitments and compare them with current roadmap entries. 7
How IT teams should adapt
The end of release waves means organizations should not wait for two annual planning events to review Microsoft changes. A more resilient approach is to establish a recurring release-management process, such as a monthly review for most teams or a more frequent review for heavily customized environments.
A practical workflow is:
- Define the products and environments that matter. Separate Microsoft 365, Dynamics 365, Power Platform, Dataverse, Copilot, and agent-related changes according to the teams responsible for them.
- Use roadmap filters. The AI at Work Roadmap provides filters for products, status, release phase, platform, and cloud instance.
10
- Save and subscribe to relevant views. RSS feeds can help teams monitor selected roadmap categories without repeatedly searching the full tracker.
16
- Connect roadmap changes to internal governance. Route relevant items into testing, security, licensing, communications, and change-management workflows.
- Record decisions separately from Microsoft’s forecast. A roadmap item should inform planning, not automatically trigger deployment or purchasing.
The final point matters because Microsoft explicitly describes roadmap dates as estimated release dates and says the information is subject to change. 10 Roadmap entries are useful signals for preparation, but they should not be treated as contractual delivery commitments.
Microsoft is also adding AI-assisted roadmap access
Microsoft’s Release Communications MCP Server provides MCP-compatible AI clients with programmatic access to information that powers the Microsoft 365 Roadmap and Azure Updates. It supports searching, filtering, and retrieving release information through natural-language requests. 30
That makes it possible to query release information from compatible AI tools instead of relying only on manual browsing. Microsoft documentation also describes MCP integration with developer tools such as Visual Studio, while the supplied announcement materials identify environments including Visual Studio Code and GitHub Copilot CLI as examples of compatible workflows. 2
29
30
This does not remove the need for human review. AI-assisted querying can make it easier to find relevant roadmap items, but administrators still need to verify scope, licensing, cloud-instance availability, rollout status, dependencies, and the latest Microsoft documentation before making an operational decision.
Why the new name is controversial
Microsoft’s rationale is straightforward: the roadmap now spans a wider portfolio built around workplace productivity, business applications, low-code tools, and AI. But the label AI at Work Roadmap is less immediately descriptive than Microsoft 365 Roadmap, particularly when the tracker also contains conventional product updates.
Critics argue that the name may make ordinary Microsoft 365, Dynamics 365, or Power Platform changes harder to find. Others see it as part of Microsoft’s broader pattern of using AI-oriented branding across products and services, which can blur distinctions between features, products, and licensing requirements. 8
17
19
Licensing adds another source of potential confusion: some Copilot and AI capabilities are associated with separate licenses or add-ons, so the presence of an item on an AI-branded roadmap does not by itself establish that every customer can use it. 18
What the change means overall
The AI at Work Roadmap is best understood as both a rebrand and a shift from scheduled communication to continuous disclosure.
Microsoft is consolidating roadmap coverage for Microsoft 365, Dynamics 365, Power Platform, Dataverse, Copilot, agents, and related experiences. At the same time, it is ending the familiar release-wave rhythm and retiring Release Planner. 3
5
7
For customers, the practical response is to build an internal monitoring habit: filter the roadmap to the products and environments in use, subscribe to relevant updates, use programmatic or AI-assisted access where appropriate, and validate every forecast before committing resources. The unified tracker may make Microsoft’s portfolio easier to view in one place, but it also makes customer-owned release governance more important.
Studio Global AI
Continue your research
This page includes a source-backed answer you can continue inside Studio Global.
People also ask
What is the short answer to "Microsoft’s AI at Work Roadmap Replaces Release Waves With Continuous Updates"?
Microsoft renamed the Microsoft 365 Roadmap to the AI at Work Roadmap on August 25, 2026, with Dynamics 365, Power Platform, and Dataverse content due in September.
What are the key points to validate first?
Microsoft renamed the Microsoft 365 Roadmap to the AI at Work Roadmap on August 25, 2026, with Dynamics 365, Power Platform, and Dataverse content due in September. Release Planner is scheduled to retire on November 15, 2026, while older release plans will remain available for historical reference.
What should I do next in practice?
IT teams should replace wave based planning with recurring reviews of filtered roadmap views, RSS feeds, and—where supported—natural language queries through Microsoft’s Release Communications MCP Server.
Sources
mc.merill.netMC1461528 - Microsoft 365 Roadmap is becoming the AI at Work Roadmap
learn.microsoft.comMicrosoft Power Platform 2025 release wave 2 plan overview
