infotech
What Microsoft has announced
Microsoft’s release-plan documentation states that new release plans will no longer be published from September 2026. New Dynamics 365, Power Platform and Dataverse capabilities will instead be published through the AI at Work roadmap. Existing plans remain available as historical references. The practical implication is a change in where application owners should look for future capability information.
Update the way your team follows product changes
Review the links and subscriptions used by application owners, architects and support teams. Make sure the people responsible for evaluating product changes know where to find the current information. Keep archived plans available for the decisions and implementations they originally informed, while distinguishing them from the material used to plan new work.
Keep the business review connected to the roadmap
A new roadmap entry is a starting point for assessment. Identify which business process it affects, whether it addresses an existing need and what dependencies require investigation. Assign an owner to review the relevant product documentation and the experience available in your environment. This keeps roadmap monitoring connected to an operational decision rather than a list of announcements.
Give useful changes a route into delivery
For a capability worth evaluating, define a small test with representative users and an agreed outcome. Review configuration, licensing, data and adoption needs before adding it to a delivery commitment. Record the assumptions and revisit them as Microsoft’s guidance and availability evolve. Your internal improvement backlog should reflect what the business has evaluated, not simply everything that appears on the roadmap.
Questions for your team.
- Who owns product-roadmap review for each application?
- Which current business priorities could benefit from the change?
- What evidence is needed before the capability enters a delivery plan?
Explore Microsoft guidance