The window runs from September to November 15

Microsoft's post of August 25, 2026 says Dynamics 365, Power Platform, and Dataverse roadmap content is moving to the AI at Work roadmap, with new capabilities publishing there from September 2026. Release Planner retires on November 15, 2026. That gives a platform team eleven weeks to move whatever it built on the old channel, and most teams built more than they remember.

The post describes the change as continuous publishing in place of the twice-yearly release wave announcements, and it lists what the new destination offers: filtering by product and environment, CSV export, RSS subscription, and search by feature ID. It also names what goes away. Release wave 1 and 2 announcements stop. Saved views stop. New release plans will no longer be published to the Release Plans pages on Microsoft Learn after September 2026.

Find out what your team built on Release Planner

Start with an inventory rather than a memo. Somewhere in most Microsoft shops there is a Release Planner saved view that a solution architect set up two years ago, filtered to the three apps the company actually runs, and a bookmark to it sits on the platform team's onboarding page. Microsoft says saved views do not carry over, so that bookmark will open to nothing in mid-November, and the person who set it up may have moved on.

Ask each product owner what they read before a release wave meeting. The answers usually include a Learn URL for one release plan, a CSV export someone loads into a spreadsheet every six months, and a slide of feature names copied from the wave announcement. Each needs a different replacement.

Decide what to do with the June 1 cutoff

The post says existing roadmap content with a public preview or general availability date of June 1, 2026 or later migrates to the new roadmap during the September to November window. Content with earlier dates stays on Microsoft Learn for reference. That is a clean rule for Microsoft and a messy one for you, because your internal tracker probably mixes items from both sides of the line.

Our suggestion is to export what you track today while Release Planner still exists, tag each row by whether its date falls before or after June 1, 2026, and keep the earlier rows as a frozen list with the Learn link as the record of reference. The later rows are the ones you will look up again on the new roadmap, and the post says feature ID search is available there, so keep the IDs in the export. Do it in the first week of September, not the last week of October.

Replace the wave meeting with a dated review

Microsoft's own guidance in the post is to set a monthly or quarterly review rhythm in place of the wave-based one and to subscribe by RSS. It is also where most teams stall, because the wave meeting had a calendar slot and an owner and the new rhythm has neither until someone gives it both.

Put the first review on the calendar for a date in October, before Release Planner is gone, with one agenda item: compare what the team used to see in Release Planner with what the new roadmap shows for the same products and environments. The gap between those lists is your migration backlog. We argued in a companion piece that a single destination still needs local release ownership, and the review is where that ownership becomes a name on an invite.

The RSS feed is the easy part, and also where a filter set at the wrong level produces a stream nobody reads. Filter to the products and environment types you actually run and route the feed to a channel someone already checks daily. Our Release Radar approach applies here too: read for what changes your tenant, not for what sounds interesting.

Keep Message Center and Learn where they are

The post is clear that Message Center remains the channel for tenant-relevant change notifications, that Microsoft Learn remains the documentation home, and that release schedules and deployment processes do not change. The temptation during a transition is to fold every feed into one. A roadmap item says a feature is coming. A Message Center post says it is arriving in your tenant on a date. The boundary between those two is what keeps a change advisory board honest, and we'd keep the feeds in separate channels with separate owners.

Learn is the awkward one because its role shifts. Release plans stop publishing there after September 2026, but documentation and the pre-June content stay. So Learn bookmarks that pointed at release plans need retiring, and those that point at docs need leaving alone. Sort the links before anyone runs a bulk find-and-replace across the wiki.

Write the change into your own release checklist

If your team runs a release checklist for shared solutions, the step that says to check the release plan on Learn needs a new target, and the step that says to review the wave announcement needs a new trigger. With continuous publishing there is no wave date to hang a pre-release review on, so the checklist needs its own date plus a rule for what happens when a tracked item changes status between reviews.

Environment owners have a related question. The new roadmap filters by environment, and the post does not say how those filters map to the environment types you named in your own environment strategy. We'd take that to the first review: do the filters line up with how the tenant is organised, or does someone maintain a mapping.

Before any of that, do the export. Release Planner's version of it stops existing on November 15, 2026, and the new roadmap will only hold what migrated.