Power Platform roadmap: prepare for AI at Work

Track the Power Platform roadmap transition to AI at Work with a practical checklist for feature ownership, Message center checks and adoption decisions.

Harllens George | 2026-09-14

Microsoft AI at Work Roadmap with Announcements, Now available and Coming soon tabs.
The Microsoft AI at Work Roadmap in the August announcement. Use its status tabs to separate available features from planned work. Image source. Used with permission from Microsoft.

Microsoft's August 25 announcement moves Power Platform roadmap disclosures to AI at Work from September 2026. Release Planner retires by November 15; personalized saved views will not transfer. Product delivery schedules stay unchanged. Transition announcement.

Sources checked September 12, 2026. AI-assisted article. Recommended checks, not a tested tenant migration.

Build your roadmap watchlist

Microsoft documents filter-encoded links, CSV exports and RSS for all features or individual items. Use these to maintain your own watchlist. Roadmap guide, updated August 25.

Start with five dependencies tied to live processes or funded projects. Keep speculative experiments separate. Each entry needs a feature ID, source link, observed status, check date and business owner. Record what a delay would affect.

Three checks before acting

  1. Compare with your baseline. Identify what changed since the previous review. Keep the source observation separate from your team's interpretation; do not rely on someone's recollection of a launch month.
  2. Check tenant context. Review relevant Message center notices with an administrator. Microsoft documents service filters and a reader role without broader administration rights. Message center guidance.
  3. Assign the next action. Choose investigate, test, defer or no action, with an owner and follow-up date. Before a pilot, define one user journey, its expected stored result and a rollback condition. Include user instructions and support handover.

A new authoring feature might justify one sandbox screen, not a commitment to rebuild an application. Ask the intended user to complete the process before closing the work item.

Pitfalls

Roadmap dates are estimates that Microsoft may change. Do not promise a customer the displayed month. Public roadmap. Record unavailable features as unavailable and schedule another check. An announcement does not prove access; a vendor release status does not replace your acceptance result.

Related reading

Apply this review to Canvas agentic coauthoring. For a separate operational change, check Power Automate mobile retirement.