Apply updates to cloud environments

  • 10 minutes

Keeping your finance and operations cloud environment up to date helps ensure you have the latest features, performance improvements, and security fixes. Microsoft provides regular service updates through Lifecycle Services as part of the One Version strategy. You can schedule, test, and apply these updates to keep your system running smoothly while meeting compliance requirements.

Supported environments

All customer-managed and Microsoft-managed environments deployed through Lifecycle Services are supported. A build environment is where code gets compiled, tested, and validated before moving to other environments. In Lifecycle Services, you can apply Binary updates and Data upgrade packages. However, Application Deployable Packages, which include custom code and extensions, can’t be applied through Lifecycle Services in a build environment. Instead, they need to be deployed in a test or production environment to be properly validated and used.

For other environment types listed below, you must use Remote Desktop Protocol to connect and install updates via the command line. For guidance on manual package deployment, see Install deployable packages from the command line.

Supported environments requiring manual deployment are:

  • Local development environments (Downloadable Virtual Hard Disk [VHD])
  • Multi-box dev/test environments in Microsoft Azure (Partner and trial projects)

Key concepts

Before applying updates, you should understand deployable packages, runbooks, and the AXUpdateInstaller, because they play an important role in the deployment process.

A deployable package is a self-contained unit that can be applied to any environment to deliver updates or new functionality. These packages may include:

  • AOT deployable package – A package generated from application metadata and source code within a development or build environment.
  • Application and platform binary update package – A Microsoft-released package containing dynamic-link libraries (DLLs), binaries, and metadata that both the platform and application rely on. This package is available through the All Binary Updates tile in Lifecycle Services.
  • Platform update package – A Microsoft-released package specifically for platform-related DLLs, binaries, and metadata. It can be accessed via the Platform Binary Updates tile in Lifecycle Services.
  • Commerce deployable package – A package that results from combining various Dynamics 365 Commerce-related updates after the Commerce code is merged.
  • Merged package – A package that consolidates different update types, such as a binary update package with an AOT package or an AOT package with a Commerce deployable package. Merging is done within the Asset Library in Lifecycle Services.

The AXUpdateInstaller manages the installation of deployable packages. It generates a runbook, which serves as a structured execution plan for deploying updates. The runbook ensures updates are applied systematically and minimizes the risk of errors during installation.

Apply a package to a nonproduction environment by using Lifecycle Services

Before starting, ensure that the deployable package has been uploaded to the Asset Library in Lifecycle Services.

  • For binary updates, directly upload the package to the Asset Library. For instructions on downloading updates from LCS, see Download updates from Lifecycle Services (LCS) .
  • For an application deployable package (such as one from an X++ hotfix or customizations), create the package in your development or build environment, and then upload it to the Asset Library.

Next, follow these steps to apply the update:

  1. Open the Environment details view for the environment where you want to apply the update.
  2. Select Maintain > Apply updates to start the process.
  3. Select the package you wish to apply. Use the filter at the top to locate the package.
  4. Select Apply. The status in the upper-right corner of the Environment details view will change from Queued to In Progress, and a new Environment updates section will show the progress of the package application. Refresh the page periodically to monitor the status.
  5. Continue refreshing the page to see status updates. When the package has been successfully applied, the environment status will change to Deployed, and the servicing status will update to Completed.