If you’ve built your adoption planning around Microsoft’s release waves, you need to know: that’s about to change.
Starting this month, Microsoft is moving Dynamics 365, Power Platform, and Dataverse onto a single unified roadmap. And they’re ditching the twice-yearly release cycle in favour of continuous feature publication.
This isn’t just a reshuffle of where you check what’s coming. It actually changes how you’ll track, plan for, and adopt new capabilities. Here’s what you need to know.
Release Waves Are Dead. Long Live the Roadmap.
For years, Microsoft has operated on a predictable rhythm: Spring Release and Fall Release, twice per year. If you missed a feature announcement, you knew the next batch was coming in six months.
That model is done.
Starting in September, Microsoft is moving to continuous publishing. New features will go live on the unified “AI at Work roadmap” as soon as Microsoft’s plans are committed and ready to share—not on a fixed schedule.
What does that mean practically? Instead of waiting for the next release wave announcement to learn what’s coming, you can check the roadmap any time and see what’s been added since you last looked.
For some organizations, this is liberating. For others, it creates planning challenges. We’ll get to that.
Why One Roadmap Instead of Three?
Here’s the honest reason: because that’s how you actually use these products.
Nobody runs Dynamics 365 in isolation. If you’re using Sales, you’re using Power Automate for workflows. If you’re using Customer Service, you’re integrating with Power BI for visibility. If you’re building custom apps, Dataverse is underneath everything.
Microsoft finally acknowledged this. Instead of maintaining separate roadmaps for products you use together, they’re consolidating into one “AI at Work roadmap” that covers:
- Dynamics 365 (Sales, Customer Service, Field Service, Project Operations, Supply Chain Management)
- Power Platform (Power Apps, Power Automate, Power BI)
- Dataverse
- Microsoft 365 Copilot (AI-related capabilities)
This makes sense. It’s also more aligned with how modern business applications actually work.
What You Actually Get
The roadmap consolidation comes with some practical tools that matter if you’re managing adoption:
CSV Exports — Download the roadmap data into your own spreadsheet. Build custom tracking sheets. Share with your steering committee without having to maintain separate lists.
RSS Subscriptions — Subscribe to updates for specific products, features, or environments. Get notified when something you care about is announced without having to check the roadmap manually every week.
Advanced Filtering — Filter by product, feature type, timeline, environment, and more. Stop scrolling through 500 announced features when you only care about 20.
Feature ID Search — If you’ve bookmarked a feature or someone mentioned “Feature ID 12345” in a meeting, you can search directly.
Release Communications API — For organizations using AI tools or custom workflows, you can integrate roadmap data directly. Build your own adoption tracking systems without manual updates.
These are genuinely useful tools if you’re managing adoption across multiple teams or trying to align feature availability with your deployment strategy.
The Planning Challenge (And How to Handle It)
Here’s where continuous publishing gets tricky: you lose the predictability of release waves.
With Release Waves, you knew:
- New features are announced on a fixed schedule
- You have roughly six months between announcements and general availability
- You can plan major feature rollouts around the wave calendar
With continuous publishing:
- Features are announced whenever they’re ready
- You have to monitor the roadmap actively to know what’s coming
- Planning becomes more reactive unless you have a process to stay current
For most organizations, that’s actually fine. Continuous publishing means features get to you faster. It means Microsoft can respond to feedback and release improvements without waiting for the next wave.
But it also means you can’t ignore the roadmap for six months and expect to stay on top of what’s changing.
What we recommend:
-
Designate a roadmap watcher — Someone in your team (probably IT/business applications) who checks the roadmap weekly and flags relevant new features. This can take 30 minutes per week.
-
Use filters strategically — Set up saved filter views for the specific products and features you care about. Reduce information overload.
-
Subscribe to RSS for key areas — If you’re heavily invested in Power Platform automation, subscribe to Power Automate updates. If you run Dynamics 365 Sales, follow Sales-specific features.
-
Build it into your adoption reviews — Add “what’s coming on the roadmap” as a standing agenda item in your quarterly technology reviews. Thirty minutes per quarter to plan around upcoming capabilities.
This isn’t more work than managing release waves. It’s just a different rhythm.
Timeline: When This All Happens
September 2026 (now): Microsoft starts publishing new capabilities to the AI at Work roadmap as plans are committed.
September–November 2026: Existing content transitions from the old Release Planner to the new unified roadmap.
By November 15, 2026: Release Planner is retired completely.
Message Center: Still exists for tenant-specific notifications. This doesn’t change.
Historical content: Pre-June 2026 features remain on Microsoft Learn. You can still look back at what was announced before, but you’ll be doing that less as you get used to the new roadmap.
The Honest Take
This change is net positive. Continuous publishing means you get features faster. A unified roadmap means you’re not hunting for features across four different Microsoft pages. Better filtering and APIs mean you can integrate adoption planning into your existing tools.
The downside is you lose the predictability and fixed cadence of release waves. Some organizations will love that flexibility. Others will miss the rhythm.
Either way, the change is coming. Starting now, you need a process for monitoring the roadmap that doesn’t involve waiting for official announcements.
For most organizations we work with, a 30-minute weekly check and a standing quarterly review is enough to stay ahead of what’s changing.
If you want help setting up that process or evaluating which upcoming features matter for your roadmap, we can help you work through it.
Need help tracking what’s coming? We can help you evaluate the unified roadmap, identify features that matter for your business, and plan adoption timing that works for your organisation.
