Service update availability


Dynamics 365 for Finance and Operations is now being licensed as Dynamics 365 Finance and Dynamics 365 Supply Chain Management. For more information about these licensing changes, see Dynamics 365 Licensing Update.

Service updates are continuous, touchless updates that provide new features and fuctionality. They elminate 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 Lifecyle Services (LCS). This topic explains the different release options and how you can use them for your organization.

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. In addition, a Release Validation Program is available for customers to join. This program allows customers to share artifacts, such as databases and code, that is used for benchmarking and tested with automation to provide an additional layer of quality assurance.

Preview Early Access Program (PEAP) is available to partners, customers, and ISV’s who opt in through the Insider Program. As a participant in the PEAP program you will have first access and visibility into the preview for the upcoming service update. 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. To join the PEAP program, sign up via the Insider Program.

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, sign up via the Insider Program.

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.

Release cadence

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.


Service updates will not be provided during the months of March, June, September, and December. However, an update will be made available in June 2019.

Customers will be able to take up to 8 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 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 LCS. To learn more about how to pause service updates, see Pause service updates through Lifecycle Services.

Targeted release schedule (dates subject to change)


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 (PEAP) Generally available (self update) Auto-update schedule (via LCS update settings) End of service
10.0.1 Platform update 25 Production starting: May 1, 2019 June 10, 2019
10.0.2 Platform update 26 April 12, 2019 May 17,2019 Production starting: June 1, 2019 August 12, 2019
10.0.3 Platform update 27 May 10, 2019 June 14, 2019 Production starting: July 1, 2019 September 9, 2019
10.0.4 Platform update 28 June 7, 2019 July 12, 2019 Production starting: August 1, 2019 October 14, 2019
10.0.5 Platform update 29 August 2, 2019 (Public Preview) September 17, 2019 Production starting: October 1, 2019 December 2, 2019
10.0.6 Platform update 30 September 6, 2019 October 11, 2019 Production starting: November 1, 2019 January 13, 2020
10.0.7 Platform update 31 October 25, 2019 November 29, 2019 Production starting: January 1, 2020 March 9, 2020
10.0.8 Platform update 32 November 29, 2019 January 17, 2020 Production starting: February 1, 2020 April 13, 2020
10.0.9 Platform update 33 February 1, 2020 (Public Preview) March 13, 2020 Production starting: April 1, 2020 TBD


The Software lifecycle policy applies to customers enrolled in First Release and when the service update is made generally available.

Sign up for the PEAP program by joining the Insider Program available at Once your nomination has been accepted, join the program.

Public 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.