TLDR: The transition of Dynamics 365 Finance and Operations (FinOps) from Lifecycle Services to the Power Platform Admin Center represents a shift from managing isolated environment slots (essentially IaaS under the hood) to governing a unified, capacity-based SaaS ecosystem. Organisations must move beyond basic administration to establish a comprehensive Power Platform governance strategy and transition architecture before Microsoft mandates the change.
Table of Contents
For years, Dynamics 365 Finance and Operations (FinOps) lived in its own exclusive, gated neighbourhood: Lifecycle Services (LCS). LCS, which is the console for Dynamics FinOps governance, is like a secret enclave that only the managers of FinOps know about with its own private security, rules and pricing.
Why is the change from LCS to Power Platform important to your enterprise?
For IT operational leaders, the esoteric nature of LCS made FinOps a black box. It was Microsoft integrated infrastructure that sat adjacent to the rest of the business but operated in its own silo under entirely independent management.
That era is ending. Microsoft is tearing down the gates and [integrating FinOps into the Power Platform Admin Center (PPAC). This isn’t just a change of internet address for the portal or a new UI. Rather, it is a fundamental re-engineering of the management model that demands a new approach to enterprise governance.
Microsoft have this image from Overview of unified admin experience for finance and operations apps – Power Platform | Microsoft Learn
Who does this impact?
This change affects all organisations who are using Dynamics Finance and Operations, also known as the Dynamics 365 ERP Suite, which includes Supply Chain Management, Project Operations and Human Resources.
Especially impacted are organisations that were all-in on FinOps and less so on Power Platform. Microsoft has flipped the script and has forced all organisations to now think of Power Platform as the overall enterprise governance framework.
The fun fact from the field is that many of these organisations had historically separated management of LCS and FinOps from the rest of IT Operations.
To the extent that Dynamics FinOps would sometimes fall under the heads of
- Business System Administration teams like IT-lite within Corporate Services
- Information Systems or Enterprise Transformation type teams
Whereas Power Platform would often be closer aligned with Microsoft 365 management under more Directors of IT Operations.
This change will bring both these teams together to find a shared operating model and therefore affects both hugely.
Why this migration is really a governance transformation: 5 Big Things
The change affects far more than administration tooling. It changes how organisations govern environments, manage access, secure data, and operate development pipelines.
Here are some highlights of what it means for you and why you need to prepare before you are pushed
1. Environments: Slots to Capacity
How do you manage your Dynamics Finance storage capacity?
In the legacy LCS model, you managed by slots. If you had a sandbox license, you had a slot. In the Power Platform, the currency is Tenant-Level Capacity.
- The Shift: To provision an environment, you must have at least 1 GB of available Dataverse capacity and 1 GB of Operations database capacity.
- Strategic Action: Governance teams must think about storage monitoring across Power Platform and FinOps cohesively.
- Tools: We now have tools like Transaction-less copies for non-production environments, which can reduce storage footprints significantly.
2. Identity: Power Platform Admin
How do you manage access to your sensitive Dynamics Finance system?
We are moving away from the “Project Owner” role in LCS toward a unified Microsoft Entra ID and Dataverse security framework.
- The Shift: Administrative authority now flows through the Power Platform Administrator role in Entra ID, granting broad authority across all business apps.
- Strategic Action: This is the time to implement unified access controls and consider the operational model within your IT operations encompassing the management of FinOps. They should self-elevate for specific tasks, creating a secure, auditable trail that was difficult to maintain in LCS.
- Tools: Design and implement Entra Privileged Identity Management (PIM).
3. Data Governance: Closing the DLP Gap
How do you prevent sensitive data from flowing out of your Dynamics Finance system?
Perhaps the most powerful advantage of this transition is the ability to apply Data Loss Prevention (DLP) policies to ERP data.
- The Shift: Because FinOps now resides within a unified environment shell within the wider Power Platform, it can be subject to the same tenant-wide DLP rules.
- Strategic Action: You can now programmatically prevent sensitive financial data from being exported to unauthorized third-party services through connector controls.
- Tools: Leverage tools like Data policies for Managed Environments to control your FinOps production and non-production environments.
4. DevOps: Automation-First Deployments
How do you deploy and release new customisations for your unique Dynamics Finance environment?
The manual “Asset Library” clicks are being replaced by a modern DevOps approach.
- The Shift: Customizations are now deployed as Unified Packages, which are combined artifacts containing both the FinOps X++ modules and the Power Platform Dataverse solutions.
- Strategic Action: Organisations must establish secure, auditable pipelines using machine identities for authentication. The direction is moving away from individual user credentials and ClickOps deployments.
- Tools: Continuous Integration and Continuous Deployment (CI/CD) using Azure DevOps For organisations on GitHub, CI/CD using GitHub Actions is also possible but more involved. Arinco is a certified GitHub partner and can assist in this area.
5. Development: The Death of the “One-Box” VM
How do you quickly and securely develop for Dynamics Finance?
For technical readers, the retirement of LCS’ cloud-hosted developer VMs is a major change.
- The Shift: FinOps currently has One-box developer environments which deploy Microsoft Azure servers into your own Azure subscription. These are being replaced with Unified Developer Environments (UDE) which are sandbox environments provisioned specifically for X++ development by using the Power Platform CLI and Visual Studio.
- Strategic Action: Transitioning to UDE requires a new development governance strategy. The change is from managing underlying Azure VM infrastructure to managing developer access to these sandbox environments, ensuring that the local developer experience is harmonized with the broader Power Platform access and controls.
- Tools: Review the new Unified developer experience FinOps
Key Takeaways
For the business leaders, Heads of Finance, Corporate Services Execs, COOs reading, here are the big ticket items for discussion with your counterparts in IT.
- Dynamics FinOps is moving from LCS to Power Platform Admin Center.
- Power Platform governance becomes the overarching framework.
- Entra ID and Power Platform Admin roles replace traditional LCS ownership models.
- Data loss policies can now apply directly to FinOps environments.
- Customisation and developer workflows are becoming automation-first.
Take action now!
The move is not optional and the clock is ticking. Freeze of new projects on LCS is already in place today (officially since February 2026).
If your organisation needs assistance dealing with this monumental shift, Arinco has a Modern Work practice that can assist with assessing your Power Platform environment and governance strategy with experience in helping customers prepare for such a transition.
Organisations that treat this migration as a simple platform change risk carrying legacy operational models into a modern SaaS ecosystem. Those that use it as an opportunity to modernise governance, security, and DevOps practices will be far better positioned for the future of Microsoft business applications.
Learn more about Arinco’s Modern Work services here.
