infotech
This article retains its original publication date. The expanded context is reviewed in September 2026; current capabilities should be checked in the linked Microsoft guidance.
The release window
The 2024 release wave 1 plan described Dynamics 365 capabilities scheduled for April through September 2024. It covered developments across customer applications, finance, operations and related experiences. Microsoft now retains this material as an archive, which provides context for decisions made during that period.
Keep historical plans useful
An archived plan can help explain when a capability was introduced or why an earlier design decision was made. Keep that historical context connected to the implementation record, while using current product documentation to assess what is available and appropriate now.
Build a repeatable readiness process
Application owners need a consistent way to assess relevant changes. Maintain a list of important workflows, integration points and representative tests. Assign the business reviewers early so readiness does not depend on a last-minute demonstration to someone unfamiliar with the process.
Connect communication with actual user impact
Explain the change in the language of the task a person performs. Show what is different, what remains familiar and where help is available. When the release creates an opportunity to improve a process, give that work an owner and a clear route through assessment, testing and adoption.
Questions for your team.
- Are we using archived material for history or for a current decision?
- Which users need to review the changed experience?
- What practical guidance will they need before the release?
Explore Microsoft guidance