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
Microsoft’s 2024 release wave 2 plan covered Dynamics 365 capabilities scheduled for October 2024 through March 2025. The plan spanned business applications and Copilot-related developments. It is now archived, so it should be used to understand that release period rather than as a statement of current availability.
Make release review specific to your environment
Begin with the applications and business processes your organisation actually uses. Identify changes that may affect a configured workflow, integration or user experience. Give each relevant item an owner who can assess the detail and explain why it matters to the business.
Test the journeys that matter
A release check should include the processes whose failure would interrupt important work. Use representative records and include handovers between applications. Keep a record of expected behaviour so the review can distinguish a product change from an existing data or configuration issue.
Turn relevant capability into a deliberate improvement
Some changes support existing processes, while others introduce an opportunity for a different experience. Evaluate those opportunities separately from routine release readiness. Confirm the business need, dependencies and adoption work before adding an enhancement to the delivery backlog.
Questions for your team.
- Which configured workflows need validation?
- Who confirms that the business is ready for the change?
- Which new capability deserves a separate evaluation?
Explore Microsoft guidance