Every October, Dynamics 365 teams used to open the same calendar entry: "Review release wave 2." This year, that entry has nothing behind it. There is no Dynamics 365 release wave 2 for 2026, no release plan document, and no neat list of features to read through over a cup of tea.
That does not mean updates have stopped. It means the way you hear about them has changed. If your business runs on Dynamics 365, the safest response is to build your own Dynamics 365 change calendar: a shared schedule that shows what is coming, who checks it, and when it reaches your users.
This guide shows you how.
What Microsoft Changed
For years, Microsoft delivered updates in two release waves. Wave 1 ran from April to September. Wave 2 ran from October to March. A release plan arrived a few weeks ahead of each wave, so admins could read it, test in a sandbox, and brief their teams.
In August 2026, Microsoft announced the end of that model for Dynamics 365, Power Platform and Dataverse. New features now appear on a single roadmap, called the AI at Work roadmap, once Microsoft commits to them. The older Release Planner site is due to retire by 15 November 2026.
In short, updates now arrive as a steady stream instead of two big announcements a year. The software is not changing less. The warning system is simply different.
Why This Matters for Your Business
The old release plan did one useful thing: it forced a conversation. Twice a year, someone had to read the changes and decide what mattered. Without that rhythm, three risks appear.
Missed changes. A new setting or a change in default behaviour can slip in unnoticed, then show up as a complaint from a user.
Surprise clashes. Custom workflows, integrations and reports can break when a feature changes underneath them. A small update can cause a big problem if nobody tested it.
Unplanned training. Staff find new buttons before anyone has explained them, and confidence in the system drops.
Companies that treat the roadmap as a news feed will struggle. Companies that treat it as an input to their own schedule will stay calm.
How to Build Your Own Dynamics 365 Change Calendar
A change calendar is a simple shared schedule. It lists every update that could affect your system, who reviews it, and when it reaches users. Here is a five-step way to build one.
Step 1: Pick an owner
Name one person responsible for watching Microsoft's roadmap. This could be a functional consultant, a system admin or a technology partner. Without a named owner, the calendar becomes everyone's job, and so nobody's job.
Step 2: Set a fixed review rhythm
Replace the old wave review with a regular check. A monthly review works well for most mid-sized teams. Large organisations with many connected systems may prefer every two weeks. Block the time in advance, the same way you once blocked time for release wave 2.
Step 3: Sort every change into three groups
For each item on the roadmap, ask one question: what does this do to us?
- Act now: it affects live processes, security or compliance.
- Plan: it is useful, but needs testing or training first.
- Watch: it is interesting, but no action is needed yet.
This keeps your list short and your meetings useful.
Step 4: Match each change to a testing window
Choose a test environment and a fixed slot for checking changes before they reach your live system. Test your most important processes every time, such as quotes, orders, invoices, approvals and any link to other tools. Write down what you tested and what you found.
Step 5: Add communication and training dates
Every change that affects users needs a short note and, where needed, a quick training session. Put these dates on the calendar next to the technical dates. A new feature only helps if people know it exists and trust it.
A Four-Week Dynamics 365 Change Calendar Template
If you want a starting point, try this four-week loop.
- Week 1: Review the roadmap and sort new items into act now, plan and watch.
- Week 2: Test priority items in your test environment and check connected systems.
- Week 3: Brief business users and update your guides.
- Week 4: Approve changes for release, then look back at what went well and what did not.
Adjust it to your own size and pace. What matters is that the rhythm repeats, so updates become routine instead of a surprise.
Mistakes to Avoid
- Waiting for a big announcement. There will not be one. Features will appear one by one, and dates can move.
- Treating every item as urgent. Most roadmap items will not touch your business this quarter. Sorting is the real skill.
- Leaving business teams out. Finance, sales and operations know which processes are fragile. Invite them to the monthly review.
- Skipping the record. Keep a short log of what changed, when, and who approved it. It helps with audits and speeds up fixes when something goes wrong.
- Trusting old dates. Roadmap timing can shift. Recheck dates at each review and update the calendar.
What This Means for Dynamics 365 Teams
The end of release waves is a good moment to move from reacting to planning. Teams with a clear Dynamics 365 change calendar spend less time on surprises and more time using new features well.
Teams without one will feel every update as a small emergency.
At Dynamics Monk, we help organisations across the UK, UAE, Australia, Singapore and Southeast Asia keep their Dynamics 365 systems steady as Microsoft's update model changes.
Whether you need a ready-made change calendar, a testing routine, or ongoing support from certified consultants, we can set it up with you.
Talk to our team to build a Dynamics 365 change calendar that fits how your business actually works.
