Quick Answer:
Microsoft hasn’t yet published the official release plan for the 2026 release wave 2 for Dynamics 365, which covers new features rolling out from October 2026 through March 2027. We expect it in late summer, with early access opening roughly 4 to 6 weeks before general availability. Continuing the trajectory set by 2025 release wave 2 and 2026 release wave 1, we anticipate the next wave to double down on agentic AI, deeper Copilot governance, and tighter integration between Business Central, Dynamics 365 Sales, and the Power Platform.
If you're planning budgets, training, or a go-live around the Microsoft Dynamics 365 2026 release wave 2 update, here's what the last few release cycles suggest is coming, and how we recommend you get ahead of it before the official plan drops.
How the Dynamics 365 Release Wave Cycle Works
Microsoft ships Dynamics 365 updates on a predictable, twice-a-year cadence: Release wave 1 covers features releasing April through September, and release wave 2 covers October through March.
Each cycle follows roughly the same rollout pattern:
Plan publication → Early access opens → Sandbox validation → General availability
The release plan itself is usually published a few weeks before early access begins, giving admins time to read through the changes before anything touches an environment. Early access typically opens in early-to-mid August for wave 2, letting organizations test new capabilities in a sandbox before they hit production in October. That gap is the window IES uses with clients to catch anything that could break a customization or an integration before it's live.
What Wave 1 2026 Tells Us About Wave 2
Like most successful businesses, Microsoft’s roadmap isn’t one that just resets every six months. Each wave tends to extend the themes the previous one introduced, and 2026 release wave 1 leaned hard into a few directions that we believe are likely to carry forward.
The biggest is agentic AI moving from pilot to production. Wave 1 pushed autonomous, role-based agents further into Copilot Studio, with more emphasis on lifecycle management, governance, and admin controls than on adding new agent types outright. In addition, it offered early support for the Model Context Protocol (MCP), which lets agents work across platforms rather than staying siloed inside one app. We expect wave 2 to build on both fronts, with more granular controls over what agents can access and act on, and continued investment in MCP as a way to connect Dynamics 365 agents to the broader Microsoft ecosystem.
Business Central got its own AI push in wave 1, with version 28 introducing agents that automate sales and purchase scenarios. Wave 2 has historically been where Microsoft rounds out a feature set introduced earlier in the year, so expect refinement here rather than a new direction, in the form of things like:
- Better AL testing and debugging tools
- Tighter Copilot extensibility for developers
- Other incremental additions to the agent capabilities already shipped
Another key element Microsoft is pushing is improved governance; there was a focus in wave 1 on strengthening data recovery, search, and platform administration. This is the unglamorous infrastructure that makes AI adoption possible at scale; we think that’s a safe bet to continue.
Expect the customer-facing apps to keep pace too. Dynamics 365 Sales and Customer Service have picked up AI-suggested talking points, deal intelligence, and multimodal support tools over the last two waves, and there's no signal Microsoft is slowing down there. If anything, we would expect to see these strengthened and improved in wave 2.
How To Prepare Now for Dynamics 365 2026 Release Wave 2
You don’t need to see the finished plan – which should still be a few weeks away – to start getting ready. You can execute on these now:
- Audit your current customizations so you know what could be affected by UI, API, or data model changes
- Bookmark the release planner so you're not relying on secondhand summaries once the plan is live (though you can expect us to do just that when it drops)
- Block sandbox testing time on your calendar for early access, before it competes with other priorities
- Loop in your Microsoft partner early if you rely on custom integrations or heavily configured workflows
A good Dynamics 365 implementation partner like IES should be flagging what’s coming and how it impacts your deployment before you have to ask.
IES Tip: Don't wait for general availability to start testing. The moment early access opens, spin up a sandbox copy of your production environment and opt in. If your organization runs heavy customizations on top of Dynamics 365, this is the cheapest insurance you'll buy all year. After all, catching a conflict in a sandbox costs you an afternoon; catching it in production can cost you a bad week and more than a few angry customers writing support tickets.
IES helps organizations plan for, test, and adopt Dynamics 365 updates without disrupting production. Reach out before wave 2 lands to make sure your environment is ready.
Microsoft Dynamics 365 Release Wave 2: FAQs
