For many years, Lifecycle Services had a central role in the Dynamics 365 Finance & Operations world. Creating new projects, managing environments, provisioning cloud-hosted environments, deployments, database operations, and many other operational processes were handled through LCS. For anyone working on Finance & Operations projects, LCS was almost the natural starting point.

However, the direction Microsoft has been taking recently is now quite clear. Finance & Operations environment management is gradually moving toward Power Platform Admin Center. In new projects, PPAC is taking a more central role instead of LCS. Finance & Operations environments are now starting to be managed under the same administration experience together with Dataverse, Power Apps, Power Automate, Copilot Studio, and other Dynamics 365 applications.

I do not think this change should be interpreted simply as “we will now create the environment from another screen.” Microsoft is aiming to manage the Business Applications product family through a more integrated platform. From this perspective, it is quite meaningful that Finance, Supply Chain Management, Commerce, Project Operations, Dataverse, and Power Platform components are moving closer to the same management experience.

Of course, this transition is not fully complete yet. On the Power Platform Admin Center side, not every function we are used to in LCS has a one-to-one equivalent. Some features will be moved to PPAC over time, some will change with a different approach, and some will probably not continue in their old form. On the other hand, PPAC also brings new possibilities in terms of capacity management, environment visibility, Power Platform integration, Dataverse connection, and centralized administration.

For this reason, the transition to PPAC does not only concern teams starting new projects. It also concerns organizations already using Dynamics 365 ERP. In the coming period, as older LCS projects also move into this new structure, knowing Power Platform Admin Center will no longer be an optional topic. Technical teams, consultants, project managers, and decision makers working with Finance & Operations will need to adapt to this new model.

In this article series, I will focus on how this transformation affects the development side of Finance & Operations. One of the first topics will be Unified Development Experience, or UDE for short. I believe it is more accurate to see UDE not only as a new type of development environment, but also as one of the important reflections of the transition from LCS to PPAC on the development side.

In this first article, before going directly into setup steps, I will try to clarify the new management approach, what the transition to PPAC means, and where UDE fits into this change.

The plan for this article series

UDE is not only about creating a new development environment. It also brings many related topics such as Power Platform Admin Center, Visual Studio setup, Git usage, Azure DevOps pipelines, build and deployment processes, and AI-assisted development.

That is why it makes more sense to cover this topic as a step-by-step series instead of one very long article.

After that, I plan to cover Visual Studio 2022 setup, connecting to a UDE environment, Git repository structure, Azure DevOps pipelines, deployable package generation, and AI-assisted development practices in separate articles.

In this first article, before going into buttons and setup steps, I will first clarify what UDE is and how it differs from the classic development VM approach.

What is UDE?

Unified Development Experience can be considered the next-generation development experience for Dynamics 365 Finance & Operations. The main idea is this: the developer no longer has to work on a separate development VM where all components are installed. Instead, the Finance & Operations runtime runs in the cloud, while the developer uses Visual Studio on their own local computer.

In this model, the development experience roughly consists of the following parts:

• The Finance & Operations environment is created and managed through Power Platform Admin Center.
• The environment runs as a sandbox with developer tools enabled.
• The developer uses Visual Studio 2022 on their local computer.
• The required metadata and development components are downloaded to the local machine.
• X++ code is written and built on the local machine.
• Deploy, run, and debug operations are performed by connecting to the UDE environment running in the cloud.

There is a very fundamental difference here. In the classic model, the development machine was both the place where the application ran and the place where we wrote code. In the UDE model, these two responsibilities are separated. Code and development tools are located on the developer’s computer, while the application runtime is located in the cloud.

How is it different from the classic development VM model?

It would not be fair to speak negatively about the classic development VM model. It served us seriously well for many years. Especially for developers coming from AX 2012, it was also easy to understand from a logical perspective. You connect to the machine; AOS is there, SQL Server is there, metadata is there, Visual Studio is there. In a sense, everything is inside a single box.

However, this model also had some practical challenges:

• Creating a separate VM for each developer created cost and management overhead.
• VM performance, disk space, updates, restarts, and access issues could affect development productivity.
• Standardizing and keeping environments up to date became more difficult as teams grew.
• Although Git and modern branch strategies could be used, the development habit often remained VM-centered.
• Onboarding a new developer could take time due to machine preparation and access processes.

UDE tries to offer a lighter and more modern model here. The developer works on their own computer. The code stays inside a local repository structure. The developer connects to the relevant environment using Power Platform Tools. In this way, the development experience moves away from the classic “connect to a remote desktop and work there” approach.

Of course, this change does not mean that everything suddenly becomes easy. The new model also has aspects that need to be learned. Visual Studio configuration, metadata download, correct URL usage, permissions, Git repository structure, and pipeline design become natural parts of this new period.

What does the transition from LCS to Power Platform Admin Center mean?

Lifecycle Services had a central position in Finance & Operations projects for many years. Project creation, environment management, deployment, monitoring, asset library, database operations, and many other critical operations were managed through LCS. Because of this, LCS has a special place in the F&O world.

However, Microsoft now has a more integrated platform approach. Power Platform Admin Center is positioned at the center not only for Power Apps or Power Automate, but also for Dataverse, Dynamics 365 applications, capacity, environments, security, and administration processes.

This transition should not be seen only as a screen change. In my opinion, the main point is that Finance & Operations is moving closer to the Power Platform world from a platform administration perspective. This has several important outcomes:

1. Environment management becomes more centralized

Different Dynamics 365 applications, Dataverse environments, Power Platform resources, and Finance & Operations environments are moving closer to the same management experience. This is especially important in projects where multiple applications are used together.

2. The connection with Dataverse and Power Platform becomes more natural

In many projects today, F&O does not stand alone. Dataverse, Power Apps, Power Automate, Copilot Studio, Fabric, and integration scenarios are discussed in almost every project. Managing environments under the same platform umbrella is therefore meaningful.

3. Capacity and licensing awareness increases

When creating environments in Power Platform Admin Center, topics such as Dataverse database capacity, Operations database capacity, application licenses, and region selection become more visible. In the past, these details could remain more in the background for some teams.

4. ALM and automation become stronger

Creating environments with PowerShell, applying the same standard across different tenants or projects, and making repeatable installations through scripts are becoming more important. Especially for partners, ISVs, or teams managing many environments, this approach provides serious advantages.

It is also important to note this: it would not be correct to say that LCS has completely disappeared from our lives. In existing projects and some operational processes, LCS still appears. However, in terms of the new development experience and the new environment creation approach, it is clear that the direction is shifting toward Power Platform Admin Center.

Why is UDE important?

In my opinion, the importance of UDE does not come only from a technical setup change. UDE moves the Dynamics 365 F&O development culture toward a more modern line. We will see its impact more clearly especially in the following areas.

It makes Git usage more natural

Managing code on the developer’s local machine and inside a repository structure makes Git usage more natural. Topics such as branches, pull requests, code reviews, commit discipline, and package generation can now settle more comfortably at the center of the development process.

Git has actually been usable in F&O projects for a long time. However, with UDE, this usage becomes more a part of the developer’s daily flow. This is an important opportunity in terms of team standards.

It strengthens the pipeline approach

UDE alone does not create a good ALM process. Simply changing the environment does not automatically mean having the right branch strategy or a high-quality build pipeline. However, when UDE is considered together with Git and Azure DevOps pipeline processes, it provides a good foundation for building a cleaner structure.

Especially topics such as building, generating deployable packages, releasing from a release branch, code reviews, and approval processes become more important with this new model.

It can make new developer onboarding easier

In the classic model, VM preparation, access, performance issues, and environment settings could take time for a new developer. With UDE, this process does not completely disappear, but it can become more standardized. With a well-prepared setup document, PowerShell script, and repository structure, onboarding a new developer into the team can be managed in a more controlled way.

It provides a better foundation for AI-assisted development

I think this will be one of the most interesting parts of the coming period. GitHub Copilot, VS Code, CLI tools, MCP approaches, and agent-based development practices are no longer only topics for .NET or web development. The Dynamics 365 F&O development world will also be affected by this change.

Managing code inside a local repository provides a more suitable working structure for AI-assisted scenarios such as code analysis, test data generation, refactoring suggestions, documentation, error analysis, and pipeline automation. For this reason, UDE should not be seen only as a need for today, but also as an infrastructure for the development habits of the next few years.

Is UDE the same as Power Platform Developer Environment?

There is a commonly confused point here: UDE and Power Platform Developer Environment are not the same thing.

The Developer Environment on the Power Platform side is mostly used for low-code development needs focused on canvas apps, model-driven apps, cloud flows, Copilot Studio, and Dataverse.

Finance & Operations UDE, on the other hand, is a sandbox environment with developer tools enabled. The purpose here is to develop in X++, work with metadata, and perform build, deploy, and debug scenarios through Visual Studio.

It is important to make this distinction clear. Otherwise, confusing situations may occur, such as “I created a developer environment, but I cannot do X++ development.”

What should be considered before using UDE?

We will go into the details of creating a UDE environment in the second and third articles. However, at this stage, it is useful to clarify some concepts from the beginning.

Permissions

The user who will create the environment must have the necessary admin permissions in Power Platform Admin Center. Usually, one of the Power Platform Administrator, Dynamics 365 Administrator, or Global Administrator roles is required. The developer also needs to have the required roles inside Finance & Operations.

Licensing

The tenant must have the appropriate licenses that allow Finance & Operations applications to be created. Finance, Supply Chain Management, Project Operations, or partner sandbox scenarios may come into play here. If the licensing side is not clear, unexpected errors may occur during environment creation or provisioning.

Capacity

Power Platform capacity is one of the critical topics for UDE. If Dataverse database capacity and Operations database capacity are not sufficient, environment creation or Finance & Operations provisioning may fail. Therefore, capacity should be checked before starting the setup.

Region selection

The selected region must support Finance & Operations applications. Region selection is not only a technical detail; it is also important in terms of URL, data residency, performance, and tenant strategy.

Naming

The environment name should not be too long or complicated. Short, meaningful names that represent the project make life easier later in terms of both administration and URLs. For example, names such as dmr-ude01 or projectx-dev01 are more readable.

Where does it make sense to use UDE?

UDE is especially a good starting point for new development trials, training environments, partner and ISV development scenarios, and teams that want to move toward a Git and pipeline-based setup. It is also an important alternative for teams that want multiple developers to work in a more standardized structure.

On the other hand, in existing large projects, it may not be the right approach to immediately shut down all development VMs and move to UDE. It is healthier to first create a small trial environment, establish the Visual Studio connection, review the repository structure, make a simple development, and test the build and deployment process.

What does this change expect from developers?

With UDE, the role of the Dynamics 365 F&O developer expands a little more. Writing X++ code alone is no longer enough. Git, branch strategy, pipelines, environment management, Power Platform connection, permissions, and capacity become natural parts of the development process.

This is actually not a bad thing. On the contrary, it brings the F&O developer closer to a more modern software development discipline. However, it is also clear that it requires a change in habits. Especially in teams that have worked on VMs for years, some resistance or question marks at the beginning are normal.

Therefore, the transition to UDE should not be seen only as a technical setup. It should be seen as a transformation that affects the way the team works.

Closing

We are in the middle of an important management change on the Dynamics 365 Finance & Operations side. For many years, Lifecycle Services was at the center. However, in the new period, Power Platform Admin Center is becoming increasingly decisive. Creating new projects, managing environments, capacity, Dataverse connection, and managing Dynamics 365 applications under the same platform umbrella are now topics that cannot be ignored.

For this reason, the transition to PPAC should not be seen only as a technical screen change. This transition means that Finance & Operations is moving toward a more integrated management model within the Microsoft Business Applications family. UDE is one of the most visible topics of this transformation on the development side.

At first glance, UDE may seem like only a new model replacing the development VM. However, behind it there is a closer environment management experience with Power Platform, a development structure more suitable for Git and pipeline processes, and a model more open to AI-assisted development tools.

That is why learning UDE is not only about learning how to create a new development environment. In my opinion, it also means understanding how the Dynamics 365 F&O world will be managed in the coming period and where development processes are evolving.