Overview of unified ERP provisioning in Power Platform (Dynamics 365 F&O/D365 FSCM)

-

Dynamics 365 Finance and operations apps are now hosted on Microsoft Dataverse, so you can provision ERP alongside other Dynamics 365 and low‑code apps directly in the Power Platform admin center or via API/PowerShell. 

Templates streamline environment creation by preinstalling ERP workloads, and a dedicated Provisioning app adds ERP capabilities to existing environments that already have Dynamics 365 apps enabled.


1. Prerequisites and licensing

Licenses: You must have a related Dynamics 365 ERP license (e.g., Finance, Supply Chain Management, Project Operations, Commerce) or the Dynamics 365 Operations Application Partner Sandbox. Admins with the Power Platform Administrator or Dynamics 365 Administrator role can create/manage environments without a full user license, subject to a ~12‑hour cache delay after role assignment.

Capacity: At least 1 GB available in both Operations and Dataverse database capacities is required.

Environment type: Use Sandbox or Trial (subscription‑based) with “Enable Dynamics 365 apps” turned on at creation; Production isn’t supported for installing the Provisioning app.

Platform tools: Install the Dynamics 365 Finance and Operations Platform Tools app before installing the Provisioning app.

2. Choosing and using ERP templates

Template mapping: Templates are tied to licenses and include Finance (preview), Supply Chain Management (preview), Project Operations Integrated (preview), and Commerce (trial only). Admin roles can provision without a user license, but the tenant must own the related license.

Environment naming: Names must be globally unique because they affect the finance and operations URL; you can opt into preview features during creation.

Dataverse requirement: Set “Add a Dataverse data store” to Yes and “Enable Dynamics 365 apps” to Yes, then select the ERP template (e.g., Finance (preview)).

Known limitations: Refer to the unified admin experience overview for the latest constraints when using templates.

3. Step‑by‑step: Provision a new environment with an ERP template

Create environment: Sign in to the Power Platform admin center → Manage → Environments → New. Enter a globally unique name, optionally enable early features, and add a Dataverse data store.

Enable apps: Select a security group, set “Enable Dynamics 365 apps” to Yes, choose the ERP template (Finance, SCM, etc.), and Save.

Developer sandbox (optional): Provision a developer‑focused sandbox via PowerShell for X++ work if needed.

4. Step‑by‑step: Install the Finance and Operations Provisioning app

Validate prerequisites: Ensure the environment is Sandbox/Trial with “Enable Dynamics 365 apps” enabled. Do not install on a Dataverse org linked to an LCS‑managed environment—installation will fail.

Install platform tools: In the environment’s Resources → Dynamics 365 apps → Install app → select “Dynamics 365 Finance and Operations Platform Tools” (Enabled status), accept terms, and wait until Status is Installed.

Install provisioning app: Install “Dynamics 365 Finance and Operations Provisioning App” (Configured status). 

In configuration:

  • Enable Developer Tools: Check to get a developer‑enabled sandbox for Visual Studio/X++; leave unchecked for standard sandbox/production.
  • Enable Demo Data: Check to deploy Contoso demo data.
  • Select version: Choose an available supported version (e.g., 10.0.39.4, 10.0.38.9; preview builds like 10.0.40.2 are for early release cycle only). Installation typically takes ~1 hour.

Disclaimer – The content published on this blog is provided solely for informational purposes. Dynamics 365 EZ makes no guarantees regarding the accuracy, completeness, timeliness, suitability, or validity of any information presented. We accept no responsibility for any errors, omissions, or delays, nor for any losses, injuries, or damages that may result from the use or display of this information.

References:

Tutorial: Provision a new environment with an ERP-based template - Power Platform | Microsoft Learn

Tutorial: Install the Finance and Operations Provisioning app - Power Platform | Microsoft Learn

Comments

Post a Comment

Please be patient and polite

Popular posts from this blog

-
Image
🚀 Upgrading Dynamics 365 FSCM (F&O) Dev local VM (VHD) to the Latest Service Pack - December 2025 Recently, Microsoft has released the new service update (10.0.40) for Dynamics 365 FSCM (F&O). K eeping your Dynamics 365 FSCM (F&O) development VM up to date is necessary as each service update brings bug fixes, performance improvements, and new features. In this guide, I’ll walk you through upgrading your local VHD to the latest service pack. Prerequisites Before starting, make sure you: Backup your VM (snapshot or export the VHD). Check your current version under System Administration > About. Access Lifecycle Services (LCS) with appropriate permissions. Step 1: Download the Latest Service Update Log in to Lifecycle Services.  Navigate to Shared Asset Library. Select Software deployable package. Download the latest service update (e.g., First Release Service Update 10.0.46) Step 2: Apply the Update on the Dev VM (VHD) Copy the .zip package into your VM (e.g., C:...
Read more
-
Image
What's new or changed in Dynamics 365 FSCM (F&O) 10.0.46  (December 2025) As enterprise architects, we know that ERP upgrades are not just about new features—they’re about aligning business processes with evolving technology standards. Microsoft’s Dynamics 365 Finance & Supply Chain Management (F&SCM) 10.0.46 release (GA December 2025, auto-update February 2026) is a significant milestone. It strengthens compliance, operational resilience, and extensibility across Finance and Supply Chain workloads. Features included in this release (Microsoft's official page): Finance 10.0.46 Supply Chain Management  10.0.46
Read more

How to use X++ macro in Dynamics 365 F&O (D365 FSCM)?

-
Image
Macros in X++ are precompiler directives that let you define reusable symbols, values, or code fragments before compilation. They are powerful but considered legacy, so Microsoft recommends using language constructs instead. 🔑 Key Points About X++ Macros What Are Macros? Macros are processed before compilation: The compiler never sees the directive itself, only the expanded characters. Legacy feature: They may be deprecated in future releases. Prefer constants or constructs like SysDa for queries. Defining Macros Syntax: #define.MyMacro(Value)   // macro with value #define.AnotherMacro()   // macro without value Case-insensitive: Macro names and directives are not case-sensitive, but best practice is to start names with uppercase. Conditional checks: #if.MyMacro // Code included if defined #endif #ifnot.MyMacro // Code included if not defined #endif Removing Macros #undef removes a macro definition: #undef.MyMacro Using Macro Values Macros can hold character...
Read more