Power Platform moves to the AI at Work roadmap: what teams should change

From September 2026, roadmap content for Power Platform, Dataverse and Dynamics 365 moves into the AI at Work roadmap, and Release Planner goes away. Here is what changes, the dates to know, and how I would set up the new roadmap so it is actually useful.

The timeline

• September 2026 — new capabilities are published to the AI at Work roadmap.
• September to November — existing items with a public preview or general availability date of 1 June 2026 or later move across.
• By 15 November 2026 — Release Planner is expected to retire, and the AI at Work roadmap becomes the main public destination.

Personalised Release Planner views do not carry over. If you rely on saved filters or tracked items, export them now and rebuild them.

What the new roadmap offers

It is meant to support filters, exports, RSS, sharing and feature-level tracking. Microsoft also mentions a Release Communications MCP Server that can bring roadmap information into AI tools and internal planning workflows. I like that direction: a roadmap is most valuable when it connects to the decisions you actually make.

One roadmap, many products

Many organisations still split Power Platform across teams: one watches Power Apps, another Power Automate, another Dataverse, someone else Copilot Studio. That breaks down when one process crosses all four. A customer service improvement can need a model-driven app, a Dataverse change, an automation, an agent and a new policy.

A combined roadmap makes those links easier to see. People on LinkedIn are already describing Power Platform as an AI-powered business platform rather than a set of low-code tools. That is a fair signal, but one view does not mean one licence, one security model or one deployment path. The architecture work is still ours.

Setting it up

1. Save a filtered view with only the products, clouds and capabilities you use.
2. Record the status of each item you care about — preview, rolling out or launched — and its expected timing.
3. Keep interest separate from commitment. A preview item does not go into a committed plan without an explicit risk decision.
4. Note the dependencies: environment, solution, connector, security model, data source, user group.
5. Confirm in your tenant with Message Center, service health and Learn before changing production plans.

The old wave rhythm gave people a moment to pause, but it also meant a burst of reading followed by months of silence. A continuous roadmap should lead to smaller, more regular conversations. My only worry is that a unified view makes the landscape look more coherent than it really is.

A one-page view

Make a single table of the Power Apps, Power Automate, Dataverse, Power Pages and Copilot Studio items that could affect your next six months. Columns: status, timing, environment impact, owner, dependency, decision. Review it in the same meeting as your platform backlog. For turning those decisions into a working rhythm, see the always-on delivery model.