Lifecycle Services (LCS) explained

Lifecycle Services (LCS) is the operational portal for Dynamics 365 Finance and Supply Chain Management implementations. If Microsoft 365 admin centre manages users, LCS manages the application lifecycle: environments, code, updates, and support. Anyone working on a Finance/SCM project will live in LCS daily.

Projects

Everything in LCS belongs to a project workspace — a logical container for a single implementation or operations engagement. A project has a type (Implementation, Migrate, etc.), an Azure subscription mapped to it for environment hosting (for sandboxes that need it), an LCS partner, and roles assigned to users (Project owner, Environment manager, Developer, etc.).

Environments

From the project, environments are requested, provisioned, started, stopped, deallocated, and decommissioned. Each environment has a lifecycle screen showing its state, the platform and application versions running, and a history of changes.

Deployable packages

Custom code and binary content move into environments as deployable packages built from a developer's Visual Studio. The developer uploads the package to the LCS asset library, then an authorised user applies it to an environment. There is no direct deploy from VS to production.

Updates

Microsoft's platform and application updates flow through LCS as packages. Customers can preview, schedule, and apply them per environment. LCS shows which environments are on which version.

Business Process Modeller (BPM)

The Business Process Modeller is a library of standard business processes (procure-to-pay, order-to-cash) maintained as flow diagrams in LCS. Customers walk through the standard process, mark fit vs gap, and link to BPM tasks recorded with the Task Recorder — which captures user actions in the application as reusable scripts for training and testing. Those recordings matter beyond documentation: they are the input format for RSAT (Regression Suite Automation Tool), which replays them as automated regression tests against sandbox environments — the standard way F&O customers survive the mandatory update cadence without manually retesting everything twice a year.

Issue search

A searchable knowledge base of known issues, hotfixes, and platform releases, with the ability to file support tickets that route to Microsoft.

Asset library

Beyond deployable packages, the asset library stores GER configurations, data packages, BPM exports, and other artefacts shared across the project team.

Working in LCS without hurting yourself

A few practices separate calm F&O projects from ones that fight their tooling:

• Treat LCS roles as production access. An Environment manager can refresh a sandbox from production or apply a package; that's the power to destroy a test cycle or leak production data into a loosely-controlled environment. Assign roles per person, prune leavers, and keep the partner's access reviewed like any other privileged account.
• Name and version asset-library uploads. The asset library accumulates dozens of deployable packages with names like Final_v2_new. Adopt a convention (build number, date, branch) on day one — during a production incident, "which package is actually running" must be answerable in seconds.
• Schedule updates, don't absorb them. Microsoft's One Version cadence means updates arrive whether you plan or not. Use the update settings to pin a predictable window, run the update through a sandbox with RSAT first, and keep one environment a version ahead for early warning.
• File support tickets through LCS with the diagnostics attached. Tickets raised through the project workspace carry environment context Microsoft can act on; tickets raised cold start with a week of "please provide your environment ID".

The transition to the Power Platform admin center

Microsoft is retiring LCS for customer projects in stages and moving its functions into the Power Platform admin center (PPAC), aligning F&O with Dataverse and the rest of the Dynamics 365 estate. New F&O environments are increasingly provisioned and managed as unified environments in PPAC — same portal as Dataverse environments, same admin model — and capabilities like environment operations, update management, and history have been landing there wave by wave, while some classic LCS features (BPM among them) are being deprecated outright rather than ported.

Practically: if you run an existing implementation, expect a hybrid period where you touch both portals, and follow Microsoft's migration guidance per feature rather than assuming a flag-day switch. If you're starting a new project, learn the PPAC-first model and treat LCS knowledge as transitional. The environment-planning side of this — what topology to run and where each piece is managed — is covered in Finance environments and LCS.