One Version service updates FAQ

In July 2018 we announced a change to the way we deliver Dynamics 365 updates that will help you stay current in a consistent, predictable, and seamless manner. In June 2019, based on customer feedback we announced New flexible service updates being made available. This FAQ is intended to provide clarity on the service updates, processes, and tools you can use to prepare for it. We will continue to add additional information to this topic as needed.

For more information about One Version service updates, see One Version service updates overview.

Can the update be delayed, what is the policy?

Yes, the customer can pause, delay, or opt-out of an update via Update Settings in the Lifecycle Services projects. A customer can choose to pause up to 3 consecutive updates. The following is an example of a delayed update:

  • The customer is currently on version 10.0.2.
  • The customer can pause updates 10.0.3, 10.0.4, and 10.0.5.
  • The customer must take the 10.0.6 update when it is available.

With a release date in early April, when will the general availability package be made available?

Production updates for a monthly release will be scheduled for the first, second, and third weeks in of the month. Depending on the configuration that you set up in Lifecycle Services (LCS), you will receive updates during that specific week.

For the April 10.0 release, Microsoft will perform updates during the weekends of April 6, April 13, or April 20 based on the configuration that you set up in LCS. Sandbox updates will always be scheduled a week before the update. The configuration setup is available in LCS.

Customers can always choose to apply the update at an earlier time, or if there is a more convenient time than the suggested times in Lifecycle Services. If the customer is on the latest version the auto update will be canceled.

Service updates

What product versions are impacted by service updates?

Version Description
8.1 and later All customers on 8.1 and later will be scheduled for automatic monthly updates with a combined application and platform update starting November 2018. You will be required to be on an update that's no older than 4 months or 3 service updates. To pause an update, refer to Pause service updates.
8.0 Customers on 8.0 can manually apply the monthly platform and financial reporting updates. You will be required to have an update that's no older than 4 months or 3 service updates. The 8.0 application lifecycle ends in April 2019. Customers on 8.0 must update by April 30, 2019 to stay supported. In order to be on a supported application, customers should follow the process to update to the latest version. For more information, see Update environments from version 8.0 to 10.0.X.
7.x Customers on 7.x can manually apply the monthly platform and financial reporting updates. You will be required to have an update that's no older than 4 months and 3 service updates. Customers on 7.x must update by April 30, 2019 to stay supported. If customer stays on version 7.3 past April 30 they will still receive automated platform updates every month. You are required to upgrade to 8.1 by April 2019 (unless extensions are not available). The only overlayered version in market will be version 7.3.

What does the service update contain?

For release 8.1 and later, service updates will contain application (including financial, reporting, and Commerce) and platform changes that are critical improvements to the service including regulatory updates. New experiences will be configurable. The service updates are backward compatible. There will be a single version representing this update.

What is a regulatory update?

A regulatory update is a new feature or an existing feature change required by law (usually for a specific country/region). The regulatory update is always required by a specific law enforcement date (LED) and should be enabled by this date or earlier.

What's the upcoming schedule of updates?

Service updates are available since November 2018. You have the option to apply the update when it is convenient for you, or let Microsoft auto-apply the service updates based on the selected maintenance window. You are required to have an update no older than 4 months.

To see a targeted release schedule, see Service update availability.

Are there any major updates post 8.1?

There will be 2 major updates in April and October where new experiences can be enabled. Major updates will not require code or data upgrade. Breaking changes will be communicated 12 months in advance such that customers can plan accordingly. Such a change will only be introduced during a major update. The 10.0 release, which will be available in April 2019, will also be an update and not an upgrade.

What does it mean when an update is backward compatible?

Backward compatibility covers binary and functional compatibility. Binary compatibility means that you can apply an update on any runtime environment without needing to recompile, reconfigure, or redeploy customizations. This also means that on a development environment at design time, X++ public and protected APIs and metadata are not modified or deleted. If Microsoft needs to break compatibility by removing obsolete APIs, it will be communicated 12 months in advance and follow a deprecation schedule. Functional compatibility is about user experience, all new experiences will be opt-in for a 12-month period.

Backward compatibility does not include non-X++/metadata APIs. Microsoft reserves the right to update versions of any dependencies the product uses, as well as remove dependencies without early warning. Microsoft does not commit to maintain backwards compatibility of dependent software libraries unless expressly stated.

For more information on deprecation guidelines and deprecated methods and metadata elements, see Deprecation of methods and metadata elements.

Can I apply a Platform service update to my existing 8.1 or later environments?

Customers on version 8.1 or later will only be able to apply the 8.1.x or v10.x Service updates. Platform only service updates cannot be applied to version 8.1.x or later. Platform service updates can only be applied to versions 7.x or 8.0.

Will Platform updates be able to be scheduled and delay/pause by customers?

Yes, customers who are on version 7.3 are able to schedule platform updates directly in Lifecycle Services. A delay/pause experience is also available.

Service updates for on-premises deployments

The policy and schedule for service updates are now the same for both cloud and on-premises deployments. This includes, for example, the option to delay applying up to 3 consecutive updates. How to apply each of these updates remains slightly different. For more information, see Apply updates to on-premises deployments.


How will Microsoft ensure quality of releases?

Ensuring quality of the release is a fundamental principle that's enabled through a series of progressive, rigorous, automated validations as described in Service update availability.

Can I select the day and time to update?

Customers can configure the day and maintenance time windows in LCS. The service update, which is based on your update settings, will start within 15 minutes. Email will be sent to customers who opt in to receive LCS notifications with instructions included on how to update. Customers will be able to select the designated tier 2/UAT sandbox for the update. Customers will have 7 calendar days for testing and validation.

Customers can optionally choose to apply the update earlier to all environments through LCS. The production-ready, deployable package will be made available to all customers via the Action Center in Lifecycle Services. Customers are responsible for deploying the update to any additional sandbox or developer/build (tier 1) environments. For more information, see Configure service update.

A service update was applied to the environment, when looking at the tile in Lifecycle Services for this environment what does the number on the tile represent?

The same service update will be auto applied to all customers by Microsoft. Microsoft will continue to service the latest update. The tile in LCS for that environment represents the cumulative number of hotfixes that are available to be applied to your environment. Because Microsoft will only auto apply the same version to all customers, you will be responsible for apply the cumulative hotfix package if it is required.

How do I update to the latest version?

Users can update to the latest version using the tiles on the Environment details page in LCS. After the update is released by Microsoft, the tile will show the update available. Customers can choose to apply the update on their own by going through the update experience on their sandbox and production environments.

How do I update the production environment to the same version after Microsoft updates the sandbox environment?

When Microsoft updates a sandbox environment, the package that is used for the update is saved in the project's asset library. The name of the package is prefixed by the words "Service Update." Because the package was already applied to the sandbox environment, you can mark this package as a Release Candidate. You can then go to the production environment and schedule to apply the package, just as you might schedule to apply any other update.

What is the expected downtime?

The expected downtime for a successful update is 30 minutes to 1 hour. However, we ask for three hours of downtime in case issues occur while the update is applied. We are actively working to reduce the downtime that is required, and you should expect improvements in the next few months.

What's the process for deprecation?

Before any feature is removed from the product, the deprecation notice will be announced in the product documentation 12 months prior to the removal.

For breaking changes that only affect compilation time, but are binary compatible with sandbox and production environments, the deprecation time will be less than 12 months. Typically, these are functional updates that need to be made to the compiler.

Can I delay an update?

You can pause an update up to 4 months or 3 consecutive service updates by way of LCS configuration. After this period, an update will be scheduled and auto-applied by Microsoft. The update experience for a delayed update will incur additional downtime.

Can I delay an update for longer than 3 consecutive service updates due to seasonal activity or other business reason?

No, service updates will be automatically applied to the sandbox, then 7 days later the update will be applied to the production environment if the environments are more than 3 service updates old. A customer can only pause up to 3 consecutive updates in a row. For example, if a customer on version 10.0 chooses to pause updates 10.0.1, 10.0.2, and 10.0.3 then service update 10.0.4 will be auto applied to the sandbox.

What happens to an environment that is running a Finance and Operations version that is no longer supported?

Environments that are running a Finance and Operations version that is no longer supported display a warning message at the top of the environment details page in LCS.

For all Microsoft-managed environments, as well as sandbox and production environments in on-premises implementation projects, some Lifecycle Services (LCS) functionality may not be available when an environment is running a Finance and Operations version that is no longer supported. The LCS functionality that may not be available includes the ability to do the following:

  • Enable maintenance mode
  • Use all capabilities provided for moving databases on an environment or across environments
  • Enable firewall access to SQL Server databases
  • Download RSAT certificates
  • Regenerate RSAT certificates

After you apply a service update for a supported version, this functionality will be available in the affected environment.

What if I find an issue during the sandbox update?

If you find an issue when doing validations in a sandbox environment, you can request to skip the update through LCS directly by providing a valid support ticket number and a business justification.

What if I find a critical issue during sandbox testing and I am not able to pause the Production auto update?

Critical issues should always be submitted to the support team via Lifecycle Services as soon as they are identified. The support staff will work with you on the resolution to the critical issue.

How much time do I get for validation?

You will get 7 calendar days for validation after the update is applied to your sandbox environment. If you need more time, you can access the deployable package via the action center in Lifecycle Service and apply to your environments. This will provide you with additional time to test the update prior to a production roll-out.

What happens when the service update is complete?

Once the service update is applied by Microsoft you will receive a notification if the update was successful or if it was not able to be applied. There can be several reasons an update was unable to be applied:

  • Pending Package Sign-off - If a package is pending signoff, Microsoft will not apply the service update to production.
  • Deployment Failure - If there was a deployment failure, the environment will be rolled-back to the original state.

If there is a failure, can I reschedule the update to be auto applied?

You will not be able to reschedule the update per se, but you may apply the package when it is convenient for you, just as you might schedule to apply any other update.

Will critical hotfixes be automatically applied to my sandbox/ production environment during auto-update?

The service update that will be made generally available, and auto applied to all customers will contain hotfixes and potentially new functionality. If a critical issue is reported after the service update has been applied, customers can pull that cumulative hotfix update from the tile in Lifecycle Services.

How will my ISVs stay current?

Service updates to customer environments will be backward compatible and no action is required by the Independent software vendors (ISVs). ISVs develop on the minimum required platform release that their code depends on. Breaking changes will have a 12-month lead time to enable ISVs to include and validate. We recommend that the ISVs be part of our Partner early access program, so that they can get early access to the platform bits and validate their solutions against the update before it's made generally available.

What about new features?

All new features will be opt-in for a 12-month period and will not require any change management until you choose to enable the feature.

Are batch jobs suspended during a service update?

Batch jobs are suspended during the maintenance windows and resume when the maintenance is completed.


How can I get early access to non-released platform updates?

You can join the First release program, where Microsoft will keep your system always current with the latest updates. If you are not already a member of the Dynamics 365 Insider Program, you will need to:

  1. Sign up for the Insider Program using this URL:
  2. Accept the terms and conditions to become a Dynamics 365 Insider.
  3. After your application has been approved (approximately 24 hours) you can then sign back into the Insider Portal to find the different preview programs available for you to join.
  4. Preview Early Access Program (PEAP) and First Release: The program requires that you accept additional terms and conditions to join. Please look for these programs within the Dynamics 365 Insider Program after your nomination has been accepted.

Is there tooling available to support testing the latest release?

The Regression Suite Automation Tool is available now. This tool significantly reduces the time and cost of user acceptance testing. User acceptance testing is typically required before taking a Microsoft application update or applying custom code and configurations to your production environment. It enables functional power users to record business tasks using the Task recorder and convert them into a suite of automated tests without the need to write source code. Test libraries are stored and distributed in Lifecycle Services using the Business Process Modeler (BPM) libraries and fully integrated with Azure DevOps for test execution, reporting, and investigation. Test data parameters are decoupled from test steps and stored in Excel data files.

How can I test and validate that the integrations continue to work?

Data task automation lets you easily repeat many types of data tasks and validate the outcome of each task. You can also use automated testing of data entities by using task outcome validation. For more information, see the Data task automation topic.

How can I determine what's changed in a service update?

The What’s new or Changed documentation is the primary source for the details contained in each service update. The Release plans are the primary source of information for all new features and changes for a future release. Features will also include help topics in as needed.

How will I know if there is a deprecated feature that will impact me if I’m not doing active development/ recompile my code?

Deprecated features will be documented with each release. For more information, see Removed or Deprecated features.

Preparing for One Version

How can I log an extensibility request?

Extensibility requests can be logged in LCS. Details are available in the Extensibility requests topic. Please note the following timelines to log and use the available extensions.

Date Extensibility requests
January 2019 All extensibility requests must be logged by January 1, 2019. ISVs and customers are requested to analyze the code and make these requests by this time. We will not provide exceptions to stay on 7.3 after April 2019, if the request has not been filed by January 1, 2019.
December 2019 Extensions will be available on/ before December 31, 2019 for the requests logged by January 1, 2019. Customers using these extensions are required to move to current version by April 2020.

What does end of service mean?

Microsoft will not provide any fixes to issues on versions that have reached end of service. Microsoft will also not investigate or troubleshoot any issue that you may encounter on a version that's older than 3 service updates. If you encounter an issue on a version that has reached end of service, you will be required to update to the latest update and report the issue if it persists.

All environments will continue to be operated by Microsoft. All automatic processes around your environments, such as monitoring or self-healing, will also continue as long as the environment is on a supported version.

Will individual hotfixes be supported?

Individual hotfixes will not be supported after 8.1. Customers must update to the latest cumulative update available to apply the fix (such as 8.1.1). Critical fixes will also be cumulative and available through the LCS servicing experience.

Will you notify me about critical hotfixes released for the monthly update that I’m on?

Customer reported issues are searchable via Lifecycle Services Issue Search. You can sign up to be notified when an open issue is resolved.

How can I upgrade to 8.x?

Refer to the Process for moving to the latest update topic to learn how to upgrade to the latest application. Updating from 8.0 to 8.1 will not require any data upgrade and will be a self-serve update with much reduced downtime.

Commerce service updates

What options are available to minimize impact to my Commerce cloud components?

Commerce cloud components will require the same down time as your Dynamics 365 headquarters. In an upcoming release, the Retail Cloud Scale Unit (RCSU) will be available to reduce and further schedule updates to your deployment. Please refer to our published release information on our documentation and release notes sites for additional details on RCSU.

Will there be options to take individual hotfixes for my commerce solution components?

All fixes and updates for commerce components will be cumulative.

What are the maintenance downtime requirements that may impact channel operations?

For retailers with a business need for redundancy, Modern POS offline capability allows core POS operations to be available for use while disconnected from the internet or while the cloud environment is being updated. Stores operating with Commerce Scale Unit will also continue to operate with support for core POS operations during cloud maintenance windows. For more information, see Online and offline point of sale (POS) operations.

When will I need to update my in-store components?

All in-instore components must be running released software that is less than one year old in order to maintain support. Customers are responsible for updating self-hosted components (such as components installed in stores or in privately managed datacenters) and ensuring that the installed versions of these components are actively supported.

Will there continue to be backward compatibility for the in-store components?

Updates to components hosted in the cloud will continue to preserve backward compatibility with component versions self-hosted by the retailer (such as components installed in stores or in privately managed datacenters - Modern Point of Sale, Commerce Scale Unit, Hardware Station) for 12 months after the release date for that version. Self-hosted components do not need to be updated at the same time as cloud-hosted components and can be updated on a separate cadence allowing time to roll out updates to stores.

What options are available for updating in-store components across my organization?

Customers can choose to update self-hosted components manually at each store or use mass update tools such as Microsoft System Center Configuration Manager, Microsoft Intune, etc.

What options do I have to slowly enable new functionality across my channels?

Microsoft provides several mechanisms to progressively roll-out and enable functional enhancements across stores, devices, and users.

  • Screen layout designer – Most visual elements in POS are configured and centrally managed by an administrative user in the customer organization. This means that new POS operations will not automatically be displayed on POS unless explicitly configured for inclusion in corresponding screen layouts. Screen layouts are configured using Screen layout designer and can be specific to a store or POS device. For more information, see Screen layouts for the point of sale (POS).
  • Functionality profiles, POS permissions, Commerce parameters – Significant elements of functionality in POS are typically configurable by the user. This can be configured through functionality profiles, POS permissions, commerce parameters, or other controls which allow for device, register, store, or user-level functionality control in applicable scenarios.
  • Modern Point of Sale and Commerce Scale Unit – Because Modern Point of Sale and Commerce Scale Unit are self-hosted by the retailer, topologies which include either of these components enable roll out of updates at a separate (and slower) cadence, and in a more granular fashion than with cloud-only topologies.