Lifecycle Services

Microsoft Dynamics Lifecycle Services (LCS) is the central portal for managing Dynamics 365 Finance and Supply Chain Management implementations. Every Finance/SCM project has an LCS workspace where customers and partners manage environments (request, provision, copy, refresh), deploy code as deployable packages, apply platform and application updates, run the Business Process Modeller (BPM), file support tickets, and store assets in the asset library. The Task Recorder integrates with LCS for capturing user actions as reusable scripts. Microsoft is gradually migrating LCS functions to the Power Platform admin centre; today both consoles are in use side by side.

In practice, LCS is where an F&O project's environment lifecycle actually happens day to day — requesting a new sandbox tier, applying a one-version update, or deploying a code package are all LCS actions rather than something done directly against the environment. The Business Process Modeller doubles as a fit-gap and documentation tool: implementation teams model the target business processes against Microsoft's standard library before building anything, which is what makes LCS as much a project-governance tool as an operations console.

Where confusion shows up: LCS project workspaces are tied to a specific implementation project, not a specific environment, so a company running multiple LCS projects (an original implementation plus a later expansion project, say) needs to track which project's workspace actually owns which live environment — losing that mapping makes it hard to know where a specific environment's deployable package history or support tickets actually live. Newcomers to F&O sometimes also assume LCS is optional tooling rather than the required system of record it actually is — environment requests, update scheduling, and deployable package history all live only in LCS, with no equivalent path around it.