# PPAC Unlocked: Deploying Dynamics 365 ERP Environments with and without Demo Data

Let me start with a story…

A few months ago, I was working with a customer who was planning to implement Dynamics 365 ERP. Their approach was structured, predictable, and heavily dependent on LCS (Lifecycle Services). Every environment - DEV, Config, Data migration, SIT, UAT, PROD- was planning to deploy with muscle memory.

Then came the shift.

Microsoft introduced the **Power Platform Admin Center (PPAC)** as the new control plane for managing environments. And suddenly, the familiar LCS-driven deployment approach started fading away.

The customer asked me a simple question:

*“Rakesh, how do we now deploy environments the right way using PPAC with and without demo data?”*

**Understanding the New World: PPAC-based Deployment**

With PPAC, environment provisioning is:

*   More **unified** across Power Platform + ERP
    
*   More **governed**
    
*   More aligned with **low-code/no-code extensibility**
    
*   Less dependent on traditional LCS workflows
    

However, for Dynamics 365 Finance & Operations (F&O), we still need to carefully plan environment topology.

**Typical Environment Strategy in D365 ERP Implementation**

Before jumping into steps, let’s define the environments and their purpose:

<table style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><td colspan="1" rowspan="1"><p><strong>Environment</strong></p></td><td colspan="1" rowspan="1"><p><strong>Purpose</strong></p></td><td colspan="1" rowspan="1"><p><strong>Demo Data Required</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>DEV</p></td><td colspan="1" rowspan="1"><p>Development &amp; Unit Testing</p></td><td colspan="1" rowspan="1"><p>&nbsp;Yes</p></td></tr><tr><td colspan="1" rowspan="1"><p>Config</p></td><td colspan="1" rowspan="1"><p>Functional configuration</p></td><td colspan="1" rowspan="1"><p>&nbsp; No</p></td></tr><tr><td colspan="1" rowspan="1"><p>Data Migration</p></td><td colspan="1" rowspan="1"><p>Data validation &amp; migration</p></td><td colspan="1" rowspan="1"><p>&nbsp; No</p></td></tr><tr><td colspan="1" rowspan="1"><p>SIT</p></td><td colspan="1" rowspan="1"><p>System Integration Testing</p></td><td colspan="1" rowspan="1"><p>&nbsp; No</p></td></tr><tr><td colspan="1" rowspan="1"><p>UAT</p></td><td colspan="1" rowspan="1"><p>Business validation</p></td><td colspan="1" rowspan="1"><p>&nbsp; No</p></td></tr><tr><td colspan="1" rowspan="1"><p>Production</p></td><td colspan="1" rowspan="1"><p>Live operations</p></td><td colspan="1" rowspan="1"><p>&nbsp; No</p></td></tr></tbody></table>

**Step-by-Step Guide to Deploy Environments via PPAC**

**Step 1: Access Power Platform Admin Center**

Navigate to:  
[https://admin.powerplatform.microsoft.com](https://admin.powerplatform.microsoft.com)

*   Login using admin credentials
    
*   Ensure you have **Environment Admin** or **Global Admin** role
    
    ![](https://cdn.hashnode.com/uploads/covers/6154a77b414f78089df3d420/f89ebcd0-b158-474c-a3ee-eba2c3ff1ae0.png align="center")
    

**Step 2: Create a New Environment**

• Navigate to Left side menu pane and click on “Manage”

• Go to **Environments → + New**

• Provide:

1.  Name
    
2.  Make this a Managed Environment -> Yes (optional)
    
3.  Group -> None
    
4.  Region
    
5.  Type (Sandbox / Production)
    
6.  Enable **“Add a Dataverse data store?**” (Yes - required)
    
7.  Pay-as-you-go with Azure? (In case Azure subscription is being) Optional
    
8.  Click on Next
    

Tip:

• Use Sandbox for DEV, SIT, UAT, Config, Data migration etc.

• Use Production only for PROD

![](https://cdn.hashnode.com/uploads/covers/6154a77b414f78089df3d420/51bbf6bc-0777-4359-9e52-03208809df64.png align="left")

Step 3: Add Dataverse

• Provide:

1.  Security group - > None (This setting varies based on Customer Security guidelines)
    
2.  Enable Dynamics 365 apps? - > Yes
    
3.  Automatically deploy these apps -> **None**
    
4.  Click on Save
    

![](https://cdn.hashnode.com/uploads/covers/6154a77b414f78089df3d420/ae1cd272-2496-4a3e-85c2-1d06a4e5b0c2.png align="left")

After environment creation:

*   Select the newly created environment
    
*   Navigate to **Resources → Dynamics 365 apps**
    
*   Click **Install App**
    
*   Select **“Dynamics 365 Finance and Operations Platform Tools”** & click Next
    
*   Click **Install**
    

![](https://cdn.hashnode.com/uploads/covers/6154a77b414f78089df3d420/1398c8e0-f50a-48cf-a2aa-483e9405d793.png align="center")

![](https://cdn.hashnode.com/uploads/covers/6154a77b414f78089df3d420/9fb3b51e-b306-4863-b27d-a6c42cec8c00.png align="center")

![](https://cdn.hashnode.com/uploads/covers/6154a77b414f78089df3d420/5fef6ff3-50b4-47e3-931e-c684a22ec84f.png align="center")

![](https://cdn.hashnode.com/uploads/covers/6154a77b414f78089df3d420/ce9b3812-026d-414c-99b6-9a578b4de203.png align="center")

![](https://cdn.hashnode.com/uploads/covers/6154a77b414f78089df3d420/2a760183-6640-44a4-9f00-ee853f56e550.png align="center")

**Step 4: Install “Dynamics 365 Finance and Operations Provisioning Ap” (With or Without Demo Data)**

This is a **critical decision point**.

**Option 1: Deploy WITH Demo Data (Contoso)**

Used for:

*   DEV
    

Benefits:

*   Pre-configured legal entities
    
*   Sample business processes
    
*   Faster onboarding for developers & testers
    

After Platform tools installation:

*   Navigate to **Resources → Dynamics 365 apps**
    
*   Click **Install App**
    
*   Select **“Dynamics 365 Finance and Operations Provisioning App”** and click Next
    
*   Click **Ok**
    

![](https://cdn.hashnode.com/uploads/covers/6154a77b414f78089df3d420/3dd68877-e4b8-492d-93dc-7eada2cc4178.png align="left")

![](https://cdn.hashnode.com/uploads/covers/6154a77b414f78089df3d420/f38cebd4-80e8-4714-bb29-cb131086b8d0.png align="left")

It will redirect to another page:

*   Select “**Enable Developer tools for Finance and Operations”** ( In case of Developer Environment)
    
*   Select **“Enable Demo Data for Finance and Operations”**
    
*   Select the version of the product
    
*   Select “I agree to the terms of service”
    
*   Click on **Install**
    
    ![](https://cdn.hashnode.com/uploads/covers/6154a77b414f78089df3d420/55b9c79f-358e-4f4e-9a0f-3a769454520b.png align="center")
    

**Option 2: Deploy WITHOUT Demo Data**

Used for:

*   Config
    
*   Data Migration
    
*   SIT
    
*   UAT
    
*   Production
    

Benefits:

*   Clean environment
    
*   Real business data setup
    
*   Avoids contamination from sample data
    

It will redirect to another page:

*   Select “**Enable Developer tools for Finance and Operations”** (In case of Developer Environment)
    
*   Deselect **“Enable Demo Data for Finance and Operations”**
    
*   Select the version of the product
    
*   Select “I agree to the terms of service”
    
*   Click on **Install**
    

![](https://cdn.hashnode.com/uploads/covers/6154a77b414f78089df3d420/99feec55-760f-4ffa-b778-237c9d834fa9.png align="center")

**Key Considerations (Lessons Learned) From real implementations:**

1.  Avoid Overusing Demo Data Demo data is helpful-but: • Can confuse business users • Adds unnecessary cleanup effort
    
2.  Separate Config & Data Migration Many projects combine them-this is risky. 👉 Keep them separate for: • Better control • Easier rollback
    
3.  Governance via Security Groups Always:
    
    • Assign environments to security groups
    
    • Control access centrally
    
4.  Naming Convention Matters Example: • D365-DEV • D365-CONFIG • D365-UAT • D365-PROD
    

# Final Thoughts

The move from LCS to PPAC is not just a tool change- it’s a mindset shift.

As Solution Architects, we must:

• Rethink environment strategy

• Align with Power Platform governance

• Design environments for scalability and clarity

Because in the end…

A well-planned environment strategy is the backbone of a successful Dynamics 365 ERP implementation!

# Thank you for Reading - Let's Connect!

Thank you for reading this piece. If you enjoyed it, please let others know. Hit the subscribe button to read more posts from this blog. [LinkedIn](https://www.linkedin.com/in/rakeshdarge/), [Twitter](https://twitter.com/DargeRakesh?s=08), [YouTube](https://www.youtube.com/user/rakeshdarge/videos)

Stay tuned!