If you run Dynamics 365 Finance & Operations implementations, you already know Microsoft Lifecycle Services (LCS) is going away. Microsoft announced the deprecation of LCS in favor of Power Platform Admin Center, with the transition underway in 2026.
For implementation teams, the question is: what actually replaces what LCS did?
The answer depends on which part of LCS you're talking about. Some capabilities move cleanly to Power Platform Admin Center. Others move to Azure DevOps. And a significant portion — the implementation project management layer — has no clear native replacement at all.
What LCS actually did
Lifecycle Services was Microsoft's cloud-based collaboration portal for D365 Finance & Operations. At full use it covered project setup and team access, environment management (deploying and managing D365 environments), Business Process Modeler (BPM) for fit-gap analysis and requirements documentation, customization tracking, Microsoft's issue search database, an asset library for deployable packages and configuration files, and implementation methodology support aligned to Sure Step and Success by Design.
Like SolMan, most implementation teams used a fraction of LCS's capabilities. Environment management and the asset library were heavily used. Business Process Modeler was theoretically useful but in practice most teams found it too rigid and under-maintained to rely on. Customization tracking was minimal and usually supplemented by Azure DevOps.
Where LCS capabilities are going
Environment management → Power Platform Admin Center. The core infrastructure management capability moves to Power Platform Admin Center. This is the most straightforward transition — it's a mature platform and environment management capabilities are comparable.
Source code and package management → Azure DevOps. Custom code, deployable packages, and release management were already largely managed in Azure DevOps by most implementation partners. This remains the recommended approach.
Issue search → Microsoft Learn and Support. LCS's issue search database migrates to standard Microsoft support channels.
Business Process Modeler → No direct replacement. BPM provided a structured library of D365 business processes for fit-gap analysis — mapping standard processes and identifying gaps. Microsoft has not announced a direct replacement. The guidance is to use Microsoft's process documentation on Microsoft Learn. In practice, teams will continue doing what most were already doing: running fit-gap workshops with their own process libraries and documenting gaps in Excel or Jira.
Implementation project management → Also no direct replacement. LCS had limited project-level features for tracking implementation progress and coordinating the team across phases. Power Platform Admin Center is an infrastructure management tool — it has no implementation project management capability. Azure DevOps handles development tasks and source control but was never designed as an ERP implementation management system.
The gap nobody is filling
Here's the honest state of D365 implementation tooling in 2026, post-LCS:
What's covered:
- Environment management: Power Platform Admin Center ✓
- Source control and deployment: Azure DevOps ✓
- Sprint and task management: Azure DevOps or Jira ✓
- Defect tracking: Azure DevOps or Jira ✓
What no native Microsoft tool covers:
- Fit-gap workshop capture and management
- Extension/customization lifecycle tracking — identification through scoping through approval through spec through test to deployment
- Test script management with traceability to requirements
- PMO visibility across workstreams with go-live readiness indicators
- Cross-phase traceability from business requirement to production deployment
This gap existed before LCS deprecation — LCS never filled it well. The deprecation just removes the thin scaffolding LCS provided without replacement.
What implementation teams are actually doing
The post-LCS stack for most D365 implementation partners: Power Platform Admin Center for environment management, Azure DevOps for source control and development task tracking, Excel for fit-gap registers and extension logs, SharePoint for document storage, Azure DevOps for defect management (often in a separate project from the development work, creating its own traceability gap), and weekly status emails assembled manually by the PMO.
A 5–7 tool stack with no connective tissue between the implementation management layer and the DevOps layer. Every status update requires manual reconciliation. Every PMO report is assembled from multiple sources. Traceability from requirement to defect requires cross-referencing multiple systems.
What to do now if you're a D365 implementation partner
1. Complete your LCS migration to Power Platform Admin Center. If you haven't already, prioritize this. Environment management is operational — you need it working cleanly.
2. Standardize your Azure DevOps configuration. If teams use inconsistent configurations across projects, now is the time to standardize.
3. Be honest about the implementation management gap. LCS deprecation is the forcing function to acknowledge that the tools you've been using for fit-gap management, extension tracking, and PMO visibility were never adequate. Replacing LCS with the same Excel-and-SharePoint approach isn't a solution — it's just removing the thin wrapper that made it look like one.
4. Consider a purpose-built implementation management layer. The gap between "development task tracking in Azure DevOps" and "implementation project management" is real and significant. It needs a system of record that Azure DevOps and Excel can't provide.
Axia fills the implementation management layer that LCS never adequately covered and that Power Platform Admin Center doesn't touch. Fit-gap analysis, extension and customization tracking (the D365 equivalent of SAP's RICEFW), guided test execution, and PMO visibility in one platform — from the first workshop to go-live.
Works with D365 Finance & Operations and Business Central, alongside your existing Azure DevOps and Power Platform tooling.