Microsoft is dedicated to providing consistent service updates for Dynamics 365. These updates are initially released for users to implement themselves before Microsoft automatically applies them. The timing between the self-deployment package release and the automatic updates to production can vary. Starting in April 2024, Microsoft introduced greater flexibility in scheduling these updates. Customers now have the option to select their preferred autoupdate window. With the 10.0.39 release, users can choose between two autoupdate windows, each separated by four weeks for every service update. This enhancement allows organizations to pick the update window that best fits their validation procedures and operational timelines. For specific timings of self-updates and autoupdates for upcoming releases, including details on the second autoupdate window, refer to the Targeted release schedule (dates subject to change). More information about the dual autoupdate window options can be found in the One Version service updates FAQ.
Customers have the flexibility to take up to four service updates annually but are required to implement a minimum of two each year. There’s also an option to pause one update at a time. This pause can be applied to the designated user acceptance testing (UAT) sandbox environment, the production environment, or both. However, once the pause period concludes, if a customer has not updated to a supported service update, Microsoft will automatically apply the latest update. This automatic application is based on the configurations set in Microsoft Dynamics Lifecycle Services. For detailed instructions on pausing service updates, see Pause service updates through Lifecycle Services.
It’s important to note that service updates are delivered four times a year, with autoupdates typically occurring in February, April, July, and October.
Targeted Release Schedule (Dates Subject to Change)
Important Changes in 2024: Starting in 2024, Microsoft is moving to a schedule of four annual service updates in February, April, July, and October. Key changes include adjustments to preview, update, and servicing durations, with a scheduled update to the preview release build now a standard component of each release. For detailed answers to common questions about these changes and their impact on the release process, consult the One Version service updates FAQ.
As of February 19, 2024, the maximum number of consecutive updates that can be paused has been reduced from three to just one. However, to maintain the requirement of a minimum of two service updates per year, release durations have been extended. More details are available in the One Version service updates FAQ.
To facilitate the introduction of the new release cadence with the first service update of 2024, some milestones for release 10.0.38 were adjusted. Further information is available in the One Version service updates FAQ.
A key point to remember is that sandbox autoupdates precede production updates by seven days.
The following table outlines the targeted release schedule.
| Release version | Preview availability | Preview latest possible update | General availability (self-update) | First autoupdate schedule for production start date | Second autoupdate 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 |
Note: An asterisk (*) in the “Release version” column indicates a major release.
Note: The “autoupdate schedule production start date” column refers to the schedule configured in Lifecycle Services. See Configure service updates through Lifecycle Services.
Note: The “End of service” column indicates the date when cumulative service updates cease to be provided.
Note: The Software lifecycle policy is applicable for First Release program participants and from the date a service update becomes generally available.
Understanding Release Naming Conventions
Current Release Naming (10.0.38 onwards):
From the 10.0.38 release forward, labels are designed to provide clearer release details. The first part of the label indicates the calendar year and quarter of the autoupdate production start date. The second part is the product version as shown in Lifecycle Services. An asterisk (*) signifies a major release. For example, CY24Q2: 10.0.39* denotes product version 10.0.39, scheduled for autoupdate in the second quarter of 2024, and it is a major “April” release.
Legacy Release Naming (Prior to 10.0.38):
For consistency during the transition, releases prior to 10.0.38 retain the older naming convention. This includes the product version, an optional asterisk for major releases, and a month indicator. For instance, 10.0.36* (the “October” release). It’s important to note that the month name doesn’t always align with the autoupdate date. For example, the 10.0.36 (“October”) release in 2023 had its autoupdate schedule start on September 29, 2023.
Preview versions and updates are available as deployable packages in the Shared asset library within Lifecycle Services. For more information, refer to One Version service updates FAQ.
Service Update: An Overview
Service updates are continuous and seamless, delivering new features and functionalities without the disruption of traditional upgrades. They eliminate the need for costly, periodic upgrades. These updates are designed to be backward compatible, removing the necessity for code merging. It is recommended to utilize tools like the Regression suite automation tool (RSAT) for regression testing.
You, as the customer, retain control over how your organization receives these updates. Options include enrolling in the First Release program to receive updates first, manually applying updates to your environments (self-update), or adhering to the default schedule and receiving autoupdates as scheduled through Lifecycle Services.
Service updates encompass both application and platform changes critical for service operation, including regulatory updates. For more information, see Service updates.
Dynamics 365 Release Processes Explained
The Dynamics 365 team meticulously designs and develops each release, conducting initial validation followed by validation from the finance and operations apps team. Rigorous testing is performed across various test topologies. Furthermore, a compatibility checker ensures backward compatibility.
Customers participating in the preview program gain early access to upcoming service updates. This preview phase allows for validation of customizations, feature familiarization, and providing feedback to Microsoft. During preview, updates must be deployed in development/test environments only, not production. Post-release, packages are downloadable from the Shared asset library in Lifecycle Services. Installation requires agreement to program terms. Sign-up for preview package access is no longer needed for version 10.0.38 and later, as a scheduled update to the preview build is now standard with each release.
The First Release program is available to all customers. Participants are among the first to implement service updates into production. Microsoft manages deployment to a UAT sandbox environment and then automatically deploys to production seven days later. Participants benefit from dedicated Microsoft engineer monitoring post-update. To join, complete the First Release Program: Microsoft Dynamics 365 Finance and Operations applications form. In most cases, the First Release build mirrors the GA build. However, in situations involving critical issues that cannot be hotfixed or are found during First Release, Microsoft may issue a new First Release build and restart sandbox and production environment updates, informing First Release customers via Lifecycle Services, though these updates cannot be paused.
Service updates are made generally available via the Action Center in Lifecycle Services. Upon availability, customers can manually apply updates to all environments, including production. If manual application doesn’t occur in designated sandbox or production environments, Microsoft automatically applies the update based on Lifecycle Services project update settings. For details, see Configure service updates through Lifecycle Services.
