| title | description | author | ms.date | ms.topic | ms.prod | ms.technology | audience | ms.reviewer | ms.custom | ms.assetid | ms.search.region | ms.author | ms.search.validFrom | ms.dyn365.ops.version |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Service update availability |
This article provides information about the different release options. |
hmahl |
03/02/2023 |
article |
IT Pro |
sericks |
Global |
hmahl |
2017-10-31 |
Platform update 11 |
Service update availability
[!include banner]
Microsoft is committed to delivering predictable service updates. These service updates will be made generally available for self-deployment approximately 2 weeks prior to Microsoft automatically applying the update.
Customers will be able to take up to 7 service updates per year and are required to take a minimum of 2 service updates per year. Customers can choose to pause up to 3 consecutive updates at a time. Pausing a service update can apply to the designated user acceptance testing (UAT) sandbox, production, or both environments. After the pause window has ended and if the customer has not self-updated to a supported service update, Microsoft will auto-apply the latest update based on the configuration selection made available in Lifecycle Services (LCS). To learn more about how to pause service updates, see Pause service updates through Lifecycle Services.
[!NOTE] Service updates will not be provided during the months of January, March, June, September, and December.
Targeted release schedule (dates subject to change)
[!NOTE] Sandbox auto-update takes place 7 days prior to the production update. End of service indicates the date when no new cumulative service updates will be provided.
| Version | Preview availability | Generally available (self-update) | Auto-update schedule (via LCS Update Settings) production start date | End of service |
|---|---|---|---|---|
| 10.0.38 (The "February" release) |
October 13, 2023 | January 12, 2024 | February 2, 2024 | April 12, 2024 |
| 10.0.37 (The "November" release) |
September 1, 2023 | October 20, 2023 | November 3, 2023 | March 15, 2024 |
| 10.0.36* (The "October" release) |
July 31, 2023 | September 15, 2023 | September 29, 2023 | January 12, 2024 |
| 10.0.35 (The "August" release) |
May 26, 2023 | July 14, 2023 | July 28, 2023 | October 20, 2023 |
| 10.0.34 (The "July" release) |
April 21, 2023 | June 16, 2023 | June 30, 2023 | September 15, 2023 |
| 10.0.33 (The "May" release) |
March 3, 2023 | April 14, 2023 | April 28, 2023 | July 14, 2023 |
| 10.0.32* (The "April" release) |
January 30, 2023 | March 17, 2023 | March 31, 2023 | June 9, 2023 |
| 10.0.31 (The "February" release) |
October 14, 2022 | January 13, 2023 | February 3, 2023 | April 14, 2023 |
| 10.0.30 (The "November" release) |
September 2, 2022 | October 21, 2022 | November 4, 2022 | March 17, 2023 |
| 10.0.29* (The "October" release) |
August 1, 2022 | September 16, 2022 | September 30, 2022 | January 13, 2023 |
| 10.0.28 (The "August" release) |
May 27, 2022 | July 15, 2022 | July 29, 2022 | October 21, 2022 |
| 10.0.27 (The "July" release) |
April 22, 2022 | June 17, 2022 | July 1, 2022 | September 16, 2022 |
| 10.0.26 (The "May" release) |
March 4, 2022 | April 15, 2022 | April 29, 2022 | July 15, 2022 |
| 10.0.25* (The "April" release) |
January 31, 2022 | March 18, 2022 | April 1, 2022 | June 10, 2022 |
* Denotes a major release.
[!NOTE] The Software lifecycle policy applies to customers enrolled in First Release and when the service update is made generally available.
[!NOTE] Beginning in 2022, we are making adjustments to end-of-year service update availability. Servicing for the major October release will be extended into January. Similarly, servicing for the November release will be extended into March. The January release has been cancelled.
[!Note] The name of the month given to a release doesn't always indicate when the auto-update may occur. For example, you'll notice in the table above that the auto-update schedule for the "October" release in 2022 actually starts on September 30, 2022.
Previews are made available as a deployable package via the Shared Asset Library in Lifecycle Services. For more details, see One Version service updates FAQ.
Service update overview
Service updates are continuous, touchless updates that provide new features and functionality. They eliminate the need to do expensive upgrades every few years. The service updates maintain backward compatibility, which means there is no need to ‘merge your code’. We recommend leveraging tools such as the Regression suite automation tool (RSAT) for regression testing.
You are in control and manage how your organization receives these updates. For example, you can sign up for the First Release program so that your organization receives updates first. You can apply the updates to any of your environments manually (self-update) or remain on the default release schedule and receive the auto-updates when you schedule them using LCS.
Service updates contain both application and platform changes that are critical improvements to the service, including regulatory updates.
Release processes
Each new release is designed and developed by the Dynamics 365 team. Any new release is first validated by the feature team, then by the finance and operations teams. During this time, extensive testing is done on various test topologies. A compatibility checker also runs tests to ensure backward compatibility.
Early access to the upcoming service update is available to all customers by taking advantage of its preview. The preview service update is used to validate customizations, learn about new features, and provide feedback to Microsoft. During this phase, the service update must be deployed on a Dev/Test environment. This release cannot be used in production. Once released, the package can be downloaded from the Shared Asset Library in LCS. You agree to the program terms at install time. Sign up for access to preview (formerly known as the Preview Early Access Program (PEAP)) is no longer required.
The First Release program is open to all customers. Customers who join the First Release program will be the first, select group of customers to take the service update all the way to production. Microsoft will manage the deployment of this service update to a UAT sandbox and then 7 days later will auto-deploy the update to production. Customers participating in this program have the additional benefit of having dedicated Microsoft engineers closely monitoring the environments for any issues after updates have been applied. To join First Release, see the First Release Program: Microsoft Dynamics 365 Finance and Operations applications form.
The service update will be made generally available using the action center in LCS. When the service update is available, it can be manually applied to all environments including production. If the service update has not been applied to the designated sandbox or production environment, Microsoft will auto-apply the update based on the Update settings for the LCS project. To learn more, see Configure service updates through Lifecycle Services.
[!INCLUDEfooter-include]