Microsoft is moving Dynamics 365 finance and operations environments from Lifecycle Services (LCS) to the Power Platform Admin Center (PPAC). New implementations already start in PPAC, and Cegeka expects existing customers to migrate in the second half of 2027. For pharma and life sciences companies, the move changes how you control releases, copy validated environments and trace changes.
Capacity is the first change you will feel. PPAC ties your database storage to your licenses, and your database must fit within that entitlement before you can migrate. The migration can wait, but your capacity check can start today.
PPAC brings finance and operations under the same admin center as Power Apps and Customer Engagement. It also replaces today's setup with three unified environment types.
The unified development environment (UDE) replaces the cloud-hosted development machine. That machine was a pay-as-you-go virtual machine in your own Azure tenant, which needed start and stop scripts to control cost and IP filtering to compensate for outdated security templates. A UDE is Microsoft-managed SaaS. Developers connect from Visual Studio with a licensed user and multifactor authentication, and request time-limited database access when troubleshooting requires it. With a single AOS, it is not built for performance testing.
The unified sandbox environment (USE) runs a user AOS and a batch AOS by default. It covers testing, user acceptance, golden configuration and data migration.
The unified production environment (UPE) no longer depends on a sizing survey and Microsoft approval: you convert a sandbox to production yourself.
For every environment type, the account that creates an environment becomes its environment admin, and you cannot change that afterwards. Decide ownership before you create one.
The PPAC package manager keeps a visible history of every change applied to an environment. That history gives your quality processes the audit trail they depend on.
In LCS, a production release was a manual task scheduled in the portal. In PPAC, you reach production through an Azure DevOps pipeline, like every other environment, and deployable packages live in Azure DevOps instead of the LCS asset library. We recommend building gated approval steps into those production pipelines, so every release carries an approval you can document as part of your change control.
Under LCS, a company with 20 licensed users could run a one-terabyte database without consequence. PPAC calculates your storage entitlement from your licenses. Once you exceed it, you can no longer create new environments.
If you need more, you can always buy extra capacity packages through a billing plan charged to your Azure subscription. PPAC also lets you drill down per environment to the tables taking up the most space. Keeping your ERP footprint under the threshold becomes a recurring task.
Since February 2026, new implementations start in PPAC. For existing LCS environments, Microsoft is running migration pilots that work but do not run smoothly yet.
When your environment becomes eligible, a migration tab appears in LCS listing the prerequisites. The most important one: your capacity must stay within your license entitlement. Waiting for a smoother process makes sense, as long as you plan ahead so the migration never collides with a validation cycle or an audit.
That view is already available for LCS-based environments.
Want to know how your current environments compare with your license capacity? Talk to our team about planning your next steps.