How Microsoft's AI at Work Roadmap Changes the Way You Should Plan for Copilot Investments
What Changed in August 2026
Microsoft announced in August 2026 that it was replacing its semi-annual release wave model for Dynamics 365 and Power Platform with a single continuous Microsoft AI at Work Roadmap. The release waves, Wave 1 and Wave 2, had been the primary mechanism through which Microsoft communicated upcoming feature delivery for Business Central, Copilot, Dataverse, and related products. That model gave customers and partners a predictable, if imperfect, view of what was coming and when. The AI at Work roadmap changes that structure significantly.
How Release Waves Worked and Why They Were Useful
The release wave model operated on a twice-yearly cadence. Wave 1 released features in the spring, Wave 2 in the fall. Each wave came with detailed documentation listing planned features, their expected availability dates, and their release status. Companies used this documentation to plan system updates, training schedules, and feature adoption timelines. IT teams could align their update windows with wave release dates. Finance teams could see when specific Copilot capabilities would be available and build adoption plans around them.
The predictability had limits. Feature dates slipped. Capabilities listed as planned sometimes moved to later waves or were revised. But the structure gave planning teams something concrete to work with, and many organizations built their Dynamics 365 roadmap reviews around the wave release cycle.
What the AI at Work Roadmap Does Instead
The AI at Work roadmap consolidates Dynamics 365, Power Platform, and Dataverse updates into a single continuously updated view. Features ship when they're ready rather than on a twice-yearly schedule. The roadmap is updated more frequently and is available at a single destination rather than across multiple product documentation sites. For companies that want to know what is coming in the next ninety days, the AI at Work roadmap provides more current information than the old wave documents did between publication dates.
The tradeoff is that long-range visibility has decreased. Release waves gave at least six months of relatively stable feature lists. The continuous roadmap provides a shorter, more accurate window. If your planning requires knowing what Business Central and Copilot will look like eighteen months from now, the AI at Work roadmap will give you a directional view, not a detailed feature list.
What This Means for Budgeting Copilot Investments
For companies that have been waiting to invest in Copilot capabilities until a specific feature they need becomes available, the shift to continuous delivery has two implications. First, features arrive more incrementally, which means you may be able to begin realizing value from some Copilot capabilities sooner than a wave-based cadence would have allowed. Second, planning around a specific feature arrival date is less reliable than it was under the wave model. A feature listed on the AI at Work roadmap as coming soon may arrive in six weeks or six months.
The practical budget implication is to treat Copilot capabilities as a compound investment that grows over time rather than a set of features with fixed availability dates. Budget for adoption capacity, training, and process adjustment on an ongoing basis rather than as a one-time effort tied to a wave release.
A Better Approach to Copilot Planning
The organizations that get the most value from Business Central's Copilot capabilities tend to operate on a continuous adoption model. They identify a set of high-priority use cases, adopt the AI capabilities that are available now, and review the roadmap quarterly to identify what to adopt next. This is a different posture than waiting for a comprehensive Copilot feature set to arrive and then deploying everything at once. Continuous adoption is more resource-efficient and produces faster time-to-value for each capability.
What Turnkey Advises Clients
At Turnkey Technologies, we recommend that clients approach the AI at Work roadmap the same way they approach any continuous improvement program: establish a regular review cadence, identify the capabilities with the highest operational impact, and prioritize adoption of what is in general availability. We help clients filter out the noise of announcements and previews and focus on what can be operationalized today. That focus hasn't changed because of the roadmap shift. If anything, continuous delivery reinforces the value of having an experienced partner who tracks these changes and helps you make sense of what is actionable now versus what to watch for later.
Frequently Asked Questions
What replaced Microsoft's release waves for Dynamics 365?
Microsoft replaced its semi-annual release waves with the AI at Work roadmap in August 2026. Instead of twice-yearly batch feature releases, Dynamics 365 and Power Platform now deliver features continuously as they're ready. The roadmap is a single, always-updated destination covering Dynamics 365, Power Platform, and Dataverse.
How does continuous delivery affect planning for Copilot investments?
Continuous delivery means features arrive more incrementally, which can allow earlier adoption of some capabilities. But planning around a specific feature arrival date is less reliable than under the wave model. Companies should budget for ongoing adoption capacity rather than treating Copilot investment as a one-time project tied to a release event.'
How often should we review the Microsoft AI at Work roadmap?
A quarterly review cadence works well for most mid-market companies. This frequency keeps teams current with what's moving into general availability without requiring constant monitoring. Microsoft partners who actively track the roadmap can flag relevant upcoming capabilities before customers would otherwise notice them.
