This article explains the process of updating or upgrading to the latest release of Microsoft Dynamics 365 for Finance and Operations. It describes the overall process and supported scenarios.

• Upgrade

The process of moving from one official release of D365 Finance and Operations to the next release, for source environments prior to version 8.0. Some examples are the move from 7.1 to 7.3, or from 7.3 to 10.0.1. The process involves setup of a free sandbox environment, code upgrade and data upgrade.

• Update

The process of applying a binary package to an environment to move it from one official release of D365 Finance and Operations to the next release, for source environments starting with version 8.0. This process has lower downtime requirements and doesn’t involve data upgrade.

Microsoft Dynamics 365 F&O Upgradation Paths to One Version

There are three primary paths to perform Microsoft Dynamics 365 F&O Upgradation. Each path is referenced below with a link to detailed steps.

• Self-service Upgrade

Applicable starting version: Microsoft Dynamics 365 for Finance and Operations 7.0 (RTW), 7.1 (1611), 7.2 (July 2017), 7.3. This path involves code refactoring to Extensions and Data Upgrade in a DevTest, Sandbox and eventually a Production environment.

1. Understand which version to select for upgrade

To align the self-service upgrade process to support continuous updates, each new release will cause the oldest release version to be discontinued.

2. Refactor your customization’s as extensions

To prepare for upgrade, you must refactor any customization’s that were overlays as extensions.

3. Run the data upgrade in a development environment

Run the data upgrade process on a copy of your source database.

• Rebuild and Update

Applicable starting version: Microsoft Dynamics 365 for Finance and Operations 8.0. This path involves removing Microsoft X++ hotfixes, and creating a merged update package.

The high-level process to update from version 8.0 to 10.0.X includes the following:

1. Deploy 10.0.X developer and build environments.
2. Branch in version control and remove any application hotfixes.
3. Recompile custom extensions and/or ISV solutions.
4. Produce a single software deployable package.
5. Merge a deployable package with the 10.0.X binary update package.
6. Deploy to target environments for validation.
7. Deploy to Production.

• Automatic Update

Applicable starting version: Microsoft Dynamics 365 for Finance and Operations 8.1.0+. This path involves configuring your project for continuous updates.

In Microsoft Dynamics Lifecycle Services (LCS), you can specify how and when you receive service updates from Microsoft for your Microsoft Dynamics 365 for Finance and Operations environments. Only users (customers or partners) who are assigned to the Project owner role in LCS can configure updates.