Microsoft is retiring release waves. Here’s what that means for Dynamics 365 and Power Platform users

For years, Microsoft’s release waves have given organisations a predictable way to understand what was coming next across Dynamics 365 and Power Platform.

Twice a year, release plans provided a natural opportunity to review upcoming functionality, assess potential impacts and consider where changes could benefit the organisation.

That approach is now changing.

From September 2026, Microsoft is moving Dynamics 365, Power Platform and Dataverse roadmap content to the AI at Work roadmap, replacing the traditional twice-yearly release wave model with continuous roadmap publishing.

At first glance, this might seem like a change to where organisations find information about new features. But the bigger implication is what happens when the twice-yearly planning cycle disappears.

Organisations will need to take a more proactive approach to understanding what is changing, what is relevant to them and where new capabilities could create value.

What’s changing?

Microsoft is retiring the twice-yearly Release Wave 1 and Release Wave 2 model for Dynamics 365, Power Platform and Dataverse.

Instead, new capabilities will be published to the AI at Work roadmap as plans are committed, with roadmap items progressing through ‘In Development’, ‘Rolling Out’ and ‘Launched’. This provides a continuously updated view of upcoming capabilities rather than grouping changes into two major release announcements each year.

The transition begins in September 2026, with existing relevant roadmap content moving to the new experience through the autumn. Release Planner will retire by 15 November 2026, while existing release plans will remain available for historical reference.

Microsoft has also confirmed there will be no September 2026 Release Wave 2 announcement.

Key transition milestones

September 2026
New Dynamics 365, Power Platform and Dataverse capabilities begin publishing to the AI at Work roadmap.

September–November 2026
Existing roadmap content with a public preview or general availability date of 1 June 2026 or later begins transitioning to the new experience.

By 15 November 2026
Release Planner retires and the transition to the AI at Work roadmap completes.

The biggest change is how organisations plan

The technology itself isn’t changing as a result of this announcement. The way Microsoft communicates roadmap information is.

Products with established release schedules will continue to follow those schedules. Message Centre remains the source for tenant-specific notifications, while Microsoft Learn continues to provide product documentation and implementation guidance.

What is changing is the planning rhythm around those updates.

Release waves created a natural checkpoint. Twice a year, organisations had a reason to bring the right people together and review:

• Upcoming capabilities
• Potential impacts
• System improvements
• Training requirements
• Future opportunities

With roadmap information now being published continuously, that checkpoint will no longer happen automatically.

For organisations already struggling to find time to review the functionality available within their existing systems, this could make it easier for important changes to be overlooked.

Without a clear process for reviewing the roadmap, organisations may miss:

• New capabilities that could deliver value
• Deprecations that may require action
• Changes that need testing
• Updates that could affect existing processes

The challenge isn’t keeping up with every Microsoft announcement. It’s knowing which changes matter to your organisation.

What should organisations do now?

The move to an always-on roadmap means organisations will need to create their own approach to monitoring and assessing change.

For Dynamics 365 and Power Platform users, that could include:

• Explore the AI at Work roadmap and create filters relevant to your organisation.
• Subscribe to updates through RSS so important changes aren’t dependent on someone remembering to check manually.
• Continue monitoring Message Centre for tenant-specific notifications and actions.
• Establish regular roadmap reviews involving the relevant business and technical stakeholders.
• Review upcoming deprecations and changes to identify anything that may require testing, configuration or user communication.
• Connect roadmap reviews to business priorities so new functionality is assessed in terms of potential value, rather than simply being treated as another feature to implement.

Microsoft’s roadmap provides tools including filtering, CSV export, RSS subscriptions and shareable views to help organisations manage this process.

The goal isn’t to adopt every new capability.

It’s to understand what’s changing, determine what’s relevant and make informed decisions about what to do next.

A more connected view of Microsoft’s roadmap

There is also a clear benefit to the change.

Most organisations don’t use Dynamics 365 or Power Platform in isolation. Microsoft increasingly positions Dynamics 365, Power Platform, Microsoft 365, Copilot and agents as part of a connected technology ecosystem.

Bringing roadmap information together gives organisations a single destination for exploring upcoming developments across these technologies, rather than requiring them to monitor separate sources.

For organisations already thinking about how different Microsoft technologies fit together, this could make it easier to spot opportunities that span multiple products.

The value, however, comes from knowing what to do with that information.

A new feature only creates value if it addresses a genuine business need, improves an existing process or supports a wider strategic objective.

Looking ahead

The retirement of release waves reflects a broader shift towards continuous roadmap communication and visibility.

For organisations, that means moving away from a twice-yearly review mentality and towards a more consistent approach to understanding what’s changing across their Microsoft environment.

The opportunity is greater visibility of future capabilities and a more connected view of Microsoft’s roadmap.

The challenge is turning that information into useful decisions.

Release waves may be ending, but the need for planning, governance and continuous improvement isn’t going anywhere.

Organisations that establish a clear process for monitoring change, assessing relevance and identifying opportunities will be better placed to make the most of what Microsoft continues to introduce.

Need help keeping pace with Microsoft updates?

At Pragmatiq, we help organisations maximise the value of Microsoft Dynamics 365, Power Platform and Copilot technologies.

Whether you’re assessing roadmap changes, reviewing the impact of new capabilities or creating a process for managing continuous updates, our team can help you understand what matters to your organisation and where technology can support your wider objectives.

Get in touch with us by emailing info@pragmatiq.co.uk or calling 01908 038110.