LCS is going away — what breaks when you move to the Power…

LCS is going away — what breaks when you move to the Power Platform admin center?

Start with the vendor's sentence. Microsoft's platform deprecation register, under Feature deprecation effective February 2026, gives the reason in one line:

"Dynamics 365 Lifecycle Services is being replaced by the Microsoft Power Platform admin center as

part of the unified admin strategy for Dynamics 365 Finance, Dynamics 365 Supply Chain Management,

and Dynamics 365 Project Operations."

The direction is not in doubt. The schedule is — we found no Microsoft page publishing a retirement date for Lifecycle Services as a whole — and so is the answer most risk registers want: what stops working. That has a better answer than the rumour version, and a worse one in two places.

The dates, and the one that isn't published

The Lifecycle Services project creation freeze page, last dated 10 July 2026, publishes three milestones:

**Code freeze in preparation for the Lifecycle Services project creation freeze** — January 2026
**New Lifecycle Services project creation frozen for new customers [DEPR]** — February 16, 2026
**Self-service migration tooling preview for existing Lifecycle Services customers [PLAN]** — Mid-2026

The middle one, verbatim: "Starting February 16, 2026, you can't create new cloud implementation projects in Microsoft Dynamics Lifecycle Services for Dynamics 365 Finance, Dynamics 365 Supply Chain Management, and Dynamics 365 Project Operations."

The freeze is narrower than it sounds, and the exclusions matter more than the rule. The page lists what "aren't affected": existing customers with active projects, Dynamics 365 Commerce, which "continue to be created in Lifecycle Services", AX 2012 upgrade projects, on-premises implementations, and tenant-to-tenant migrations, which "need a Lifecycle Services project". An exception form sits at aka.ms/LCSProjectCreationException — case-by-case, and "Approval isn't guaranteed."

Now the absence, stated as narrowly as we can support it. We looked for a published end-of-life date for Lifecycle Services on four pages: the project-creation-freeze page, the deprecation register, the unified admin overview and the Support-migration page. None names one. The register's February 2026 entry says the opposite of a shutdown — "Existing customers with active Lifecycle Services projects retain access."

The one retirement that is announced has stages rather than dates. From Migration of the Lifecycle Services Support experience: the LCS Support page "is being retired" [DEPR] in three stages, and "Each stage lasts one month or until all required fixes are deployed to production, whichever is later." Stage three blocks access outright. Plan against stages, not a calendar.

The operations remap

Every lifecycle operation has a new name and, in two cases, different behaviour. Microsoft's table from the unified admin overview, reordered to lead with today's name:

**Deploy** — What it is called in Power Platform: Provision · What actually differs: "Not applicable"
**Database refresh** — What it is called in Power Platform: Copy · What actually differs: "In Power Platform, code is always copied with data, giving a full copy of the source environment. However, Lifecycle Services only copy data."
**Database export** — What it is called in Power Platform: Backup (custom or system-defined) · What actually differs: "In Power Platform, a backup is kept in the cloud and never downloaded as a SQL .bak or .bacpac file."
**Point-in-time restore** — What it is called in Power Platform: Restore (custom or system-defined) · What actually differs: "Not applicable"
**Deallocate/delete — What it is called in Power Platform: Delete · What actually differs: "Restoring a deleted environment where Dynamics 365 Finance and Operations Provisioning App** is installed, but isn't yet implemented."

Two operations are absent from the table above because they have no Lifecycle Services predecessor — Microsoft's Lifecycle Services terminology column reads "Not applicable" for both. Reset "isn't yet implemented for environments where Dynamics 365 Finance and Operations Provisioning App is installed". Convert to production is "Supported for unified environments" [GA].

Read the Database export row twice. The database copy someone takes to a local machine, an analytics box or a partner's environment stops existing as an artefact — it is not renamed, and the file does not come out.

The list Microsoft publishes — and what it actually says

Microsoft publishes its own gap list, headed Lifecycle Services features not implemented in the Power Platform admin center. Reproduced whole, destination wording verbatim:

**Methodology** — "Track phases and timelines in Dynamics Implementation portal or in Azure DevOps"
**Project settings and users** — "Dynamics Implementation portal"
**Organization users** — "Microsoft 365 admin center"
**Translation service** — "Dynamics translation connector"
**Asset library** — "Store software packages in Azure DevOps and directly import to Dataverse. Database backups aren't provided for offline use."
**Solution management** — "Microsoft Marketplace"
**Build environments** — "Microsoft Hosted Agents in Azure DevOps"
**Alert service** — "Create a support ticket."
**Business process modeler** — "Business process catalog"
**Task recorder** — "Save files locally."

Here is what contradicts the way this list gets repeated: every row carries a comment, and eight of the ten name a destination. The other two name an action — "Create a support ticket." and "Save files locally." Not one of these ten is documented as simply gone. So the risk question is not what disappeared — it is whether each destination is there, and whether it does the same job. We checked the three that carry most weight.

Three destinations, checked one at a time

Translation service — the destination has a problem. The gap table points at the "Dynamics translation connector". That connector's own reference page is titled **Dynamics Translation Service (Preview)** [PP], carries an ms.date of 1 March 2024, and lists among its prerequisites "An account with access to Dynamics Lifecycle Services." Meanwhile the same deprecation register carries a separate entry: "Microsoft Dynamics 365 Translation Service (DTS) is deprecated. This service will reach end-of-support on October 15, 2025" [DEPR], adding that "The service will be removed from Dynamics Lifecycle Services and the extensions will be unpublished", and pointing instead to Microsoft Custom Translator. We found no page reconciling those two statements. Do not plan against the connector row without confirming the service behind it.

Methodology — the destination exists, and it still points back at LCS. The Dynamics 365 Implementation Portal [GA] is real, carrying a project phase field, project users, reviews and tailored guidance. But its own Manage projects article, ms.date 17 April 2024, states that some fields "are not editable, such as LCS Go-Live date and LCS ID", and instructs: "To change the go-live date, update it in the LCS milestone under the Deploy methodology's go-live date." The named successor to LCS methodology reads its go-live date out of LCS. That is a dependency, not a migration.

Business process modeler — the destination is real and it is a different object. The business process catalog [GA] exists, is downloadable from aka.ms/BusinessProcessCatalog, and Microsoft "update[s] the catalog at least four times each year" — current article titles reflect the July 2026 version. It is a published catalogue of end-to-end scenarios, and a useful one. It is not where you model your process hierarchy. Part of BPM was also gone before this began: the August 2022 LCS deprecation table lists "Business process modeler Visio management" with "Replaced by another feature?" answered No.

Three checks, three different answers. That is why the row-by-row check is the work.

The go-live path is the real discontinuity

This is where the two documentation sets diverge in a way that changes a plan.

The Dynamics side is unambiguous. Prepare for go-live, ms.date 12 June 2026, scopes itself in its first line — guidance for go-live "in Lifecycle Services if you already have a project there" — and states that "the implementation project in Lifecycle Services must complete a go-live readiness review with the Microsoft FastTrack for Dynamics 365 team". Its exceptions note also carries a scoping line: "These steps do no apply to implementations that you manage in the Power Platform admin center." Microsoft's typo preserved.

The Power Platform side describes a different operation. The convert-a-sandbox-to-production tutorial, ms.date 6 November 2025 and updated 13 July 2026, gives three preparation steps — review outstanding tasks, communicate the downtime window, "Confirm production licensing and deployment readiness for business use" — then: select Manage, then Environments, select the sandbox, and choose the Convert to Production button in the action bar. The environment "is inaccessible during the conversion window (up to two hours)", and "This procedure is bidirectional."

That tutorial names no Go-live Readiness Review, no FastTrack step and no Microsoft approval. We searched for one there, on the unified admin overview, and on prepare-go-live — the page that would carry it, and that explicitly puts PPAC-managed implementations outside its steps. We are not claiming the gate is gone. We are reporting that two published paths do not describe the same control, and no page we found says which applies to a unified environment. Get that answered in writing.

One more thing, because it shows how fresh this documentation is: that note announces "four exceptions" and lists three — the third a scope statement, not an exception.

Where we would draw the line

We would not treat this as an admin task. Three of the ten rows are owned by people who never read admin-centre release notes — the translation owner, the build engineer whose pipeline publishes to the Asset library, and whoever pulls a database copy for analytics. The Asset library row ends conversations late: "Database backups aren't provided for offline use", and the alternative runs through a sandbox you must still be paying for.

And we would not wait for the migration tooling to start the inventory. That tooling is a mid-2026 preview [PLAN], and mapping who depends on which LCS surface is the input it will need anyway.

What to do this week

List every human and every pipeline that signs in to lcs.dynamics.com, and what each does there. That list, not the tooling, is the migration plan.
Find every consumer of a downloaded database file. A Power Platform backup is "never downloaded as a SQL .bak or .bacpac file".
If translation is in scope, confirm the supported path with your account team, given the October 2025 end-of-support entry for the Dynamics 365 Translation Service.
Ask, in writing, which go-live control applies to a unified environment — the FastTrack readiness review or the Convert to Production button.
Check whether anything you own is on the not-affected list. If so, February's date is not yours.

About Cognilium Cognilium is the AI optimization layer for Dynamics 365 — complementary apps that optimize the pricing, inventory, warehouse and planning decisions your ERP manages but can't optimize. Built on Power Platform, Dataverse and Azure. https://cognilium.ai · https://www.linkedin.com/company/37180269/

An optimization app installed into your governed estate has to survive this transition too. Book a fifteen-minute call and we will walk your admin-plane dependencies and where an optimizer sits against them — no deck. https://cognilium.ai

LCS is going away — what breaks when you move to the Power Platform admin center?