Set up on-premises projects in Lifecycle Services (LCS)

You must use Microsoft Dynamics Lifecycle Services (LCS) to deploy and update an instance of Dynamics 365 Finance + Operations (on-premises). After you purchase a server and user license through the Volume Licensing flow or the Dynamics Price List flow, see the article, Buy Finance + Operations (on-premises), to create an Microsoft Entra account or use an existing Microsoft Entra account, and then complete all the sign-up steps. You will be redirected to LCS, where an on-premises implementation project will be provisioned for you.

On-premises implementation project.

The on-premises project has all the tools that you require in order to implement, maintain, and operate an on-premises solution. Here are some of the tools that are available in the on-premises project:

  • Methodology – The on-premises methodology provides best practices that will help customers implement and manage on-premises projects.
  • Business process modeler – Business process modeler (BPM) is used to capture requirements and do fit gap analysis.
  • Cloud-hosted environments – Cloud-hosted environments are used to deploy developer and build topologies, and to complete Dev Application Lifecycle Management (ALM) for on-premises solutions.
  • Code upgrade – These tools will help you upgrade code to a newer release.
  • Issue search – Search for published KBs that are related to application and platform issues.
  • Localization and translation – Localize and translate assets.
  • Support – File and track support incidents.
  • Project users – Assign users to a project.
  • Project settings – Edit project-level settings, such as connectors, the project name, organization users, and the license number.
  • Asset library – The Asset library is a library for various assets, such as packages.
  • SharePoint online library – Connect to an online Microsoft SharePoint library.

To start your on-premises implementation, you must follow the steps in the methodology to correctly set up the project, deploy the developer and build environments, and then deploy sandbox and production environments. To help you with deployments, two environment slots are pre-allocated to the on-premises project. One slot is for a sandbox environment, and the other slot is for a production environment. These slots will be used during the Servicing flow to help guarantee that packages are tested in the sandbox environment before they are applied in the production environment.

Environment limits

Customers and partners are limited in the number of specific environment types they can deploy in a given on-premises project. These are outlined in the below table.

Organization type Production environments Sandbox environments
Customer 1 1 or more
Partner (with on-premises license) 1 1 or more
Partner (without on-premises license) 0 1