Microsoft is changing where partners and customers should look for roadmap information for Dynamics 365, Power Platform, and Dataverse. Beginning in September 2026, Business Applications roadmap content is moving into the AI at Work roadmap, creating a single roadmap destination across Microsoft 365, Copilot, agents, and Business Applications.

For partners, this is not a product launch delay or a deployment change. It is a communications and planning change. The practical impact is that sales, delivery, customer success, and advisory teams need to update their internal playbooks and customer-facing references so they are not pointing customers to roadmap locations that Microsoft is retiring or archiving.

What changed

Microsoft has announced that roadmap content for Microsoft Dynamics 365, Power Platform, and Dataverse will move to the AI at Work roadmap starting in September 2026. This consolidates Business Applications roadmap visibility with the broader Microsoft work and AI roadmap experience, including Microsoft 365, Copilot, and agent-related updates.

The announcement also marks a shift away from the familiar twice-yearly release-wave communication model for Business Applications. Instead of relying primarily on large semiannual release-plan moments, Microsoft is moving toward continuous roadmap and change communications.

A key operational detail is the treatment of existing roadmap items. Microsoft says existing items with public preview or general availability dates on or after June 1, 2026, are expected to migrate to the new roadmap after September 2026. Partners should therefore expect some overlap and transition activity while older release-plan assets are archived and new roadmap experiences become the default reference point.

Microsoft also states that there will not be a September 2026 Release Wave 2 announcement. Release Plans on Microsoft Learn will be archived, and Release Planner is scheduled to be retired by November 15, 2026.

Why this matters for partners

For CSP distributors, indirect resellers, direct-bill partners, scale solution providers, software development companies, and systems integrators, roadmap information is more than a news feed. It supports pre-sales conversations, solution design, change management, training plans, customer adoption roadmaps, and executive briefings.

When the source of roadmap truth changes, partner teams can easily end up working from outdated links, screenshots, or exported release-plan documents. That creates risk in customer conversations: a consultant may reference a retired planning tool, a seller may share an obsolete roadmap link, or a customer success manager may rely on an old release-wave assumption when discussing upcoming capabilities.

The move to the AI at Work roadmap also reflects how Microsoft is increasingly positioning Business Applications alongside AI-driven productivity, Copilot, and agent experiences. Dynamics 365, Power Platform, and Dataverse are no longer best discussed as isolated application roadmaps. They are part of a broader platform narrative around business process automation, data, AI assistance, and agentic workflows.

That alignment can be useful for partners, but it also means field teams should refresh their messaging. Customers evaluating Dynamics 365 or Power Platform will likely expect clearer connections to Copilot, Microsoft 365, and AI transformation initiatives. Roadmap discovery should support that broader story.

What is not changing

Microsoft is explicit that this change affects roadmap communications only. Product release schedules are not being changed by this announcement. Deployment processes remain the same. Message Center notifications remain in place. Product documentation is also not being replaced by the roadmap move.

That distinction is important. Partners should avoid presenting this as a change to when features ship or how updates are deployed. The safer message is: Microsoft is changing where roadmap information is published and how ongoing roadmap communications are organized.

For managed services and support teams, this means operational monitoring should continue through the established channels used today. Message Center remains critical for tenant-specific notices and administrative action items. Product documentation remains the source for how features work. The roadmap is for planning visibility, not a replacement for release notes, admin notifications, or technical implementation guidance.

Default impact partners should expect

The most immediate impact is link maintenance. Any partner portal, sales deck, customer handout, internal wiki, enablement path, or methodology document that points to Business Applications Release Plans or Release Planner should be reviewed. Materials that are customer-facing should be prioritized first.

Partners should also expect questions from customers who are used to the release-wave model. Some customers have built internal planning rhythms around twice-yearly release announcements. They may ask whether the absence of a September 2026 Release Wave 2 announcement means fewer features or less transparency. The recommended answer is that Microsoft is moving to continuous roadmap and change communications rather than concentrating updates into the traditional release-wave format.

There may also be process changes for teams that export roadmap data. Microsoft points partners to AI at Work roadmap capabilities such as filtering roadmap views, exporting information to CSV, and subscribing through RSS. Those options should be evaluated against existing internal reporting workflows.

Finally, partners with automation or advanced reporting needs should note Microsoft’s reference to the Microsoft Release Communications Model Context Protocol Server. Microsoft says partners can access roadmap data through that MCP server at no cost and without a sign-in requirement. For partners building internal copilots, advisory dashboards, or automated customer briefing tools, this may become a useful integration point.

Recommended partner actions

Start with an inventory. Search internal knowledge bases, SharePoint sites, Teams tabs, sales content libraries, customer onboarding materials, and managed service runbooks for references to Business Applications Release Plans, Release Planner, or old roadmap URLs. Replace those references with the new AI at Work roadmap where appropriate.

Next, update customer-facing messaging. Sellers and customer success managers should have a short explanation ready: Dynamics 365, Power Platform, and Dataverse roadmap updates are moving into the AI at Work roadmap, and Microsoft is shifting toward continuous roadmap communication. Emphasize that this is a planning and communications update, not a change to product deployment or support processes.

Partners should also revise governance routines. If your quarterly business reviews or roadmap workshops rely on release-wave summaries, adjust the agenda to include AI at Work roadmap review, Message Center review, and product documentation review as separate inputs. This helps customers understand which source answers which type of question.

For technical and advisory teams, test the new roadmap experience before customer meetings. Learn how filtering, CSV export, and RSS subscription options work so that consultants can provide practical guidance rather than simply forwarding a link. Where customers need recurring roadmap summaries, consider building a repeatable export or subscription process.

Finally, evaluate the Microsoft Release Communications MCP Server if your organization already uses AI assistants, internal knowledge retrieval, or customer briefing automation. Roadmap data that can be consumed programmatically may reduce manual research time and improve consistency, provided the output is still reviewed by qualified consultants before being used in customer commitments.

Bottom line

This announcement is a signal that Microsoft wants Business Applications roadmap planning to live within a broader AI-at-work context. For partners, the near-term task is straightforward: update links, retire references to legacy release-planning destinations, prepare teams for continuous roadmap communications, and reassure customers that product schedules and deployment processes are not changing because of this roadmap move.

The partners that handle this well will avoid customer confusion and may also gain a better way to connect Dynamics 365, Power Platform, Dataverse, Copilot, Microsoft 365, and agents into one strategic planning conversation.

Microsoft source: Business Applications roadmap content moving