Skip to main content

Copilot - Create me a new Unified Developer Environment [UDE] in Power Platform Admin Center [PPAC]

UDE represents a shift toward treating F&O apps as part of the broader Dynamics 365 and Power Platform ecosystem, simplifying administration and improving productivity. But wait! What if we could take this one step further? What if deploying a UDE‑enabled environment didn’t require building templates in Power Platform Admin Center, exporting JSON, re‑importing configurations, and manually triggering deployments? What if you could simply ask Copilot:

“Deploy a new UDE‑enabled latest release F&O environment for me  in Australia with the name 'Patrick-Dev'. Keep all other settings same as my last sandbox.”

No templates. No PPAC wizard. No repetitive configuration steps. Just a conversational deployment pipeline. No Drama!

Introduction

Unified Developer Experience (UDE) in the Power Platform Admin Center (PPAC) is a modern approach for developing, testing, and deploying Dynamics 365 Finance and Operations (D365 F&O) applications. It replaces traditional, costly remote desktop (RDP) virtual machines (CHE) with lightweight, cloud-based environments managed directly within PPAC.

Key Aspects of UDE in PPAC:

  • No LCS Footprint: Development environments are created directly via PPAC or PowerShell, eliminating the need for Microsoft Dynamics Lifecycle Services (LCS)
  • Local Development: Developers connect directly to this cloud environment from their local Visual Studio instances.
  • Dataverse Integration: UDE connects F&O with Power Platform tools, allowing seamless integration with Dataverse, dual-write, and virtual entities.
  • Cost Management: By eliminating the need for high-powered, always-on Tier 1 VMs, UDE saves on infrastructure costs, basing pricing on 1GB+ Dataverse storage
Step 1 : Required Tools
To use the MCP‑driven provisioning workflow, make sure the following components are installed and configured:
  • .NET SDK (10.0 or later) 
    Required for running the MCP server and supporting tooling.
  • VS Code with MCP support enabled
    This is your command center  - where prompts, MCP servers, and CLI all come together.
  • Power Platform CLI 
    The engine that actually talks to the Power Platform Admin Center and executes environment operations.
  • Power Platform CLI MCP Server 
    This one is critical. It’s not the same as the Dynamics 365 ERP MCP server — this server specifically exposes Power Platform CLI capabilities to Copilot inside VS Code.
And the best part?
You don’t even need to hunt down installers manually. You can literally prompt your way through setup:
“Can you install the MCP server for Power Platform CLI?” 
VS Code and Copilot will handle the rest.

Step 2: Configure the MCP Server in VS Code
Once installed, VS Code will detect the MCP server automatically.
Check the following:
  • You’re logged into the correct tenant (If you work across multiple tenants, this is the #1 place mistakes happen.)
  • The MCP server is pointing to the Power Platform CLI, not the ERP metadata server
You can run basic commands like:
pac auth list
pac environment list
If these work, you’re ready for the fun part.

Step 3: Creating an F&O Environment Using a Prompt
From the GitHub COpilot chat window in VS Code, type in a prompt like:
“Deploy a new UDE‑enabled latest release F&O environment for me  in Australia with the name 'Patrick-Dev'. Keep all other settings same as my last sandbox.”
The MCP server will interpret this and generate the correct CLI command sequence.

What happens behind the scenes
  1. MCP parses your prompt
  2. It maps your parameters to CLI flags
  3. It executes the provisioning command
  4. PPAC begins deploying the environment

It’s genuinely fun experimenting with MCP + Power Platform CLI, and there are already some great use cases where this model shines. But the real excitement is what comes next. As Copilot becomes more deeply integrated with UDE and environment provisioning, we move toward a world where creating a fully configured F&O environment is as simple as expressing intent. 

Labels:

Comments

Post a Comment

Popular posts from this blog

User Security Governance (Preview) feature in D365 FO

Let's take a first look at User security governance . It is the latest set of features in the D365F&O 10.0.43 update which provides useful tools to System administrators for role management, licenses auditing, enhanced audit trails and versioning, supported with some useful very useful reports around license usage, separation of duties violations etc. Key aspects of this feature include: Role Management: Improved tools for creating, modifying, and managing user roles. Audit Trails: Enhanced tracking of changes made to security settings, helping administrators monitor and review security configurations. Compliance: Tools to ensure that security settings comply with organizational policies and regulatory requirements. Feature management A new feature called (Preview) User security governance has been added to Feature management to control the overall functionality. Navigate to System administration > Security > Security governance to explore all the features. Security analy...
Post a Comment
Read more

Microsoft Dynamics 365 FSCM Licensing - New Multi-License Mapping on Menu Items

Licensing in enterprise systems has long been a game of mapping menu items to license types, ticking boxes, and hoping your role design didn’t trigger unexpected costs. But with the 2025 updates to Dynamics 365 Finance and Operations, Microsoft has flipped the script—ushering in a smarter, more flexible model that reflects how users actually work. Let’s break it down. In the legacy model, each menu item was tied to a single license type. For instance, if a user accessed MenuItemA that had a Finance license type on it, they needed a Finance license. If they accessed MenuItemB with SCM assigned on it, they needed SCM. Simple? Yes. But also rigid, prone to over-licensing, and blind to real-world role overlap. Example:  This model treated licensing like a static blueprint—ignoring the nuance of blended roles, attach licenses, and shared responsibilities across departments. Fast forward to 2025. Microsoft’s new licensing logic is object-level, dynamic, and context-aware. Now, a single m...
2 comments
Read more

Conditionally Hiding Menu Items in D365 FinOps Menus Without Using Feature Keys

In Microsoft Dynamics 365 Finance and Operations (D365 F&O), menu items are the links that can be clicked on to access forms, reports, classes, jobs, and queries. Feature keys are typically used to control the visibility of menu items based on user licenses. However, there are scenarios where you might want to hide menu items conditionally without relying on feature keys.  This can be accomplished by extending the 'SysMenuNavigationObjectFactory' class and modifying the checkAddSubMenu(...) method.  Suppose we want to hide the  Vendor payment journal menu item under Accounts payable > Payments > Vendor payment journal Steps 1. Create an extension of the SysMenuNavigationObjectFactory class [ ExtensionOf ( classStr (SysMenuNavigationObjectFactory))] internal final class SysMenuNavigationObjectFactory_PS_Extension { } 2. Create a Chain of Command (CoC) for the checkAddSubMenu method [ ExtensionOf ( classStr (SysMenuNavigationObjectFactory))] internal final...
Post a Comment
Read more