Microsoft is dedicated to providing predictable service updates for Dynamics 365. These updates are initially made available for users to deploy themselves before Microsoft automatically applies them. The timing between the self-deployment package release and the automatic production updates can vary. Starting April 2024, significant flexibility has been introduced to update scheduling, particularly concerning Auto Release Dates. Customers now have the power to select an auto-update window that aligns with their needs. With the 10.0.39 release and onwards, users can choose between two distinct auto-update windows, spaced four weeks apart for each service update. This enhancement allows organizations to pick the update window that best fits their validation processes and operational schedules. For detailed timing of self-updates and auto-updates for upcoming releases, including the new second auto-update window, please refer to the Targeted release schedule (dates subject to change) section below. To delve deeper into the dual auto-update window options, consult the One Version service updates FAQ.
Customers are entitled to receive up to four service updates annually, with a mandatory minimum of two. Furthermore, users can choose to pause one update at a time. This pause can be applied to either the User Acceptance Testing (UAT) sandbox environment, the production environment, or both. Once the pause period concludes, if a customer hasn’t updated to a supported service update independently, Microsoft will automatically apply the latest update. This auto-update is based on the configurations set within Microsoft Dynamics Lifecycle Services. For comprehensive instructions on pausing service updates, see Pause service updates through Lifecycle Services.
It’s important to note that service updates are rolled out four times each year, with auto-updates typically occurring in February, April, July, and October.
Targeted Release Schedule (dates subject to change)
Important Changes for 2024 and Beyond
Starting in 2024, Microsoft has transitioned to releasing four service updates every year, scheduled for February, April, July, and October. Significant changes have been implemented concerning preview, update, and servicing durations. Notably, a scheduled update to the preview release build is now a standard component of each release cycle. For detailed answers to frequently asked questions about these changes and their impact on the release process, please consult the One Version service updates FAQ.
Effective February 19, 2024, the maximum number of consecutive updates that can be paused has been reduced from three to one. However, to maintain consistency with service update frequency, the release durations have been extended, ensuring the same minimum requirement of two service updates per year remains in effect. More details on these adjustments can be found in the One Version service updates FAQ.
To facilitate the introduction of the new release cadence with the initial 2024 service update, certain release milestones for version 10.0.38 were adjusted. Additional information about these adjustments is available in the One Version service updates FAQ.
It’s crucial to remember that sandbox auto-updates precede production updates by seven days, allowing for validation in a non-production environment before changes are applied to live systems.
Understanding the Release Schedule Table
The table below provides a detailed breakdown of the targeted release schedule. Key points to note:
- An asterisk (*) in the “Release version” column indicates a major release, signifying significant feature updates and potential architectural changes.
- The “auto-update schedule production start date” column refers to the auto-update schedule configured in the update settings within Lifecycle Services. For guidance on configuration, see Configure service updates through Lifecycle Services. This column is crucial for understanding auto release dates.
- The “End of service” column specifies the date beyond which no new cumulative service updates will be provided for a given release version. It’s essential for long-term planning and ensuring your systems remain supported.
| Release version | Preview availability | Preview latest possible update | General availability (self-update) | First auto-update schedule for production start date | Second auto-update schedule for production start date | End of service |
|---|---|---|---|---|---|---|
| CY25Q4: 10.0.45* | July 28, 2025 | August 8, 2025 | September 12, 2025 | October 3, 2025 | October 31, 2025 | May 22, 2026 |
| CY25Q3: 10.0.44 | April 25, 2025 | May 2, 2025 | June 6, 2025 | July 4, 2025 | August 1, 2025 | February 17, 2026 |
| CY25Q2: 10.0.43* | January 27, 2025 | February 7, 2025 | March 14, 2025 | April 4, 2025 | May 2, 2025 | November 21, 2025 |
| CY25Q1: 10.0.42 | October 25, 2024 | November 1, 2024 | December 27, 2024 | February 1, 2025 | March 7, 2025 | August 22, 2025 |
| CY24Q4: 10.0.41* | July 29, 2024 | August 9, 2024 | September 17, 2024 | October 4, 2024 | Nov 1, 2024 | May 23, 2025 |
| CY24Q3: 10.0.40 | April 26, 2024 | May 3, 2024 | June 7, 2024 | July 5, 2024 | August 2, 2024 | February 18, 2025 |
| CY24Q2: 10.0.39* | January 29, 2024 | February 9, 2024 | March 15, 2024 | April 5, 2024 | May 3, 2024 | November 22, 2024 |
| CY24Q1: 10.0.38 | October 27, 2023 | November 3, 2023 | January 12, 2024 | February 2, 2024 | Not applicable | August 23, 2024 |
| 10.0.37(The “November” release) | September 1, 2023 | Not applicable | October 20, 2023 | November 3, 2023 | Not applicable | March 15, 2024 |
| 10.0.36*(The “October” release) | July 31, 2023 | Not applicable | September 15, 2023 | September 29, 2023 | Not applicable | January 12, 2024 |
| 10.0.35(The “August” release) | May 26, 2023 | Not applicable | July 14, 2023 | July 28, 2023 | Not applicable | October 20, 2023 |
| 10.0.34(The “July” release) | April 21, 2023 | Not applicable | June 16, 2023 | June 30, 2023 | Not applicable | September 15, 2023 |
The Software lifecycle policy governs customers enrolled in the First Release program and the date when a service update becomes generally available.
Understanding Release Naming Conventions
New Naming Convention (10.0.38 onwards):
From release 10.0.38 forward, release labels have been updated to provide greater clarity. The first part of the label indicates the calendar year and quarter in which the auto-update production start date is scheduled. The second part specifies the product version as it appears in Lifecycle Services. An asterisk (*) at the end of the label denotes a major release. For example, CY24Q2: 10.0.39* represents product version 10.0.39, scheduled for auto-update in the second quarter of 2024, and is a major update (the “April” release). This new convention helps in easily identifying the auto release dates and the nature of the update.
Legacy Naming Convention (up to 10.0.37):
For consistency during the transition, release versions prior to 10.0.38 retain the previous naming convention. This format includes the product version, an optional asterisk for major releases, and a broadcast month indicator. An example is 10.0.36* (the “October” release). It’s important to note that the month name associated with the release does not always precisely indicate when the auto-update will occur. For instance, the auto-update schedule for the 10.0.36 (“October”) release in 2023 actually commenced on September 29, 2023. Understanding both naming conventions is key to interpreting auto release dates accurately.
Previews and preview updates are accessible as deployable packages in the Shared asset library within Lifecycle Services. For more detailed information, refer to the One Version service updates FAQ.
Service Update Overview: Continuous and Efficient
Service updates for Dynamics 365 are designed to be continuous and touchless, delivering new features and functionalities without disrupting operations. This approach eliminates the need for costly and time-consuming upgrades every few years. Because these service updates are built to maintain backward compatibility, there is no requirement for extensive code merging, streamlining the update process significantly. It is highly recommended to utilize tools like the Regression suite automation tool (RSAT) for efficient regression testing, ensuring smooth transitions with each update.
Crucially, you retain control over how your organization receives these updates. You have options such as enrolling in the First Release program to receive updates ahead of the general schedule. You can also manually apply updates to your environments (self-update) at your convenience. Alternatively, by adhering to the default release schedule, you will receive auto-updates as per your schedule configured in Lifecycle Services. This flexibility ensures you can manage auto release dates in a way that suits your organizational needs.
Service updates encompass both application and platform changes vital for the service’s integrity, including essential regulatory updates. For further information, consult Service updates.
Release Processes: Ensuring Quality and Predictability
The Dynamics 365 team meticulously designs and develops each new release. Rigorous validation processes are in place, starting with the Dynamics 365 team’s validation, followed by validation from the finance and operations apps team. Extensive testing is conducted across diverse test topologies. Furthermore, a compatibility checker is employed to guarantee backward compatibility, minimizing disruption from updates.
All customers participating in the preview program gain early access to upcoming service updates. This preview phase is intended for customers to validate customizations, explore new features, and provide valuable feedback to Microsoft. During the preview phase, customers are required to deploy the service update in a development/test environment; preview releases are not intended for production environments. Post-release, the update package can be downloaded from the Shared asset library in Lifecycle Services. Program terms must be agreed upon during installation. Sign-up for preview package access (formerly known as the Preview Early Access Program [PEAP]) is no longer required. For version 10.0.38 and later, a scheduled update to the preview build is a standard component of every release cycle, ensuring consistent preview experiences.
The First Release program is available to all customers, offering an opportunity to be among the first to implement service updates into production. Microsoft manages the deployment of these updates to a UAT sandbox environment and subsequently auto-deploys the update to production seven days later. Participants in the First Release program benefit from dedicated Microsoft engineers closely monitoring their environments for any post-update issues. To join the First Release program, complete the First Release Program: Microsoft Dynamics 365 Finance and Operations applications form. In most cases, the First Release build is identical to the General Availability (GA) build. However, in situations where critical issues that cannot be hotfixed are identified during the First Release period, Microsoft may issue a new First Release build and restart the sandbox and production environment updates. First Release customers are notified of such restarts via Lifecycle Services, but pausing these updates is not possible. This program offers early insight into auto release dates in a production-like setting.
Service updates are made generally available through the Action Center in Lifecycle Services. Once available, customers can manually apply the update to all environments, including production. If the service update is not manually applied to the designated sandbox or production environment, Microsoft will automatically apply it based on the update settings configured in Lifecycle Services. For detailed guidance, refer to Configure service updates through Lifecycle Services. This ensures all customers receive necessary updates, leveraging auto release dates for consistent system maintenance.
