Microsoft Dynamics 365 Finance and Operations: Dev Setup
Developer series · Episode 1
Microsoft Dynamics 365
Finance & Operations Development environment structure and preparation
JGS has worked with Dynamics AX 2009, AX 2012, and Dynamics 365 Finance & Operations. Our team brings together finance, costing, and tax specialists with expertise in system and development architecture. We begin this series with an introduction to the Microsoft ERP system.
Developing for Microsoft Dynamics 365 Finance & Operations requires tools for editing code and an environment for running the changes. The configuration determines whether Visual Studio runs inside a development virtual machine (VM) or on your PC connected to the cloud. First, we will explain that structure, the tools, and their connections. Environment setup follows in the next episode.
01How the development environment is arranged
Start by identifying where the development tools, application runtime, and business database are located. There are two main development environment types, and they place these components in different locations.
OneBox (LCS development VM): Visual Studio, the application runtime (AOS), and the business database share one virtual machine. Deploy an Azure development VM from an existing LCS project, or download a VHD from the LCS Shared Asset Library and run it locally in Hyper-V.
Unified Developer Environment (UDE, PPAC): a single-developer sandbox environment created from an ERP-based template in the Power Platform admin center (PPAC). Source, metadata, and the X++ compiler stay in Visual Studio on the developer PC; code is deployed to and runs in the cloud environment.
No new LCS projects. Since February 16, 2026, new Finance, Supply Chain Management, and Project Operations customers cannot create new cloud implementation projects in LCS and use PPAC instead. Existing LCS projects continue to work. For new customers, Azure OneBox is therefore not the default route, and UDE is replacing LCS cloud-hosted development VMs.
Their strengths and limits are summarized in the table below.
Image description and source
A table comparing OneBox (LCS development VM) and UDE (PPAC). Layout: OneBox keeps Visual Studio, AOS, and the database in one VM; UDE keeps Visual Studio on the PC with the runtime in the cloud. Strengths: OneBox lets you develop and check in one place and existing LCS projects keep working; UDE is created in PPAC without LCS, works with Dataverse and Power Platform, and is capacity-based with faster setup. Limits: OneBox has VM running cost and upkeep, limited Dataverse connection, and the LCS new-project freeze; UDE needs a cloud connection, is single-developer with one AOS, and offers no version choice (10.0.39 or later). Best for: OneBox with an existing LCS project; UDE for new customers as the default route.
Source: Microsoft Learn
Sources: LCS project creation freeze · Environment types and templates · Unified admin overview · UDE FAQ
A development environment lets you make and check changes separately from live business work. Validate the business results in a test environment before moving a change into production.
OneBox: develop and run in one virtual machine
Image description and source
The developer connects to an Azure development VM through RDP, or opens a local Hyper-V VM through its console. Visual Studio, application runtime, and business database are inside the same OneBox VM. This is a responsibility diagram, not evidence of deployment or direct browser-to-database access.
Source: Microsoft Learn
The developer connects to the VM and uses Visual Studio inside it. An Azure development VM uses Remote Desktop. A local Hyper-V VM can also be opened through the Virtual Machine Connection window. Tools, application components, and business data are together, so you prepare the complete VM.
Why LCS is used here. Use an existing LCS project to prepare an Azure development VM or find its access details. New customers cannot create new LCS projects, so this route applies when an active project already exists. For local OneBox, download a VHD from the LCS Shared Asset Library and run it with Hyper-V. New VHDs are released twice a year, after the April and October releases, and use of the VHD is subject to Microsoft's software terms. LCS does not replace the code editor or the VM connection tool.
Sources: LCS project creation freeze · VHD setup · VHD release cadence
Unified Developer Environment: develop on a PC and run in the cloud
Power Platform admin center (PPAC) development environment (UDE): develop on your own PC with Visual Studio and Power Platform Tools.
Image description and source
The PC contains Visual Studio 2022, extensions, compiler, source, and metadata. Application execution and business data are in a connected developer-focused cloud Sandbox. The developer operates the remote debugger from the PC. Arrows describe connection, deployment, and debugging work, not a single protocol or port.
Source: Microsoft Learn
In a Unified Developer Environment (UDE), the development tools, source code, and metadata are on the PC. Metadata includes form and table definitions. Code execution and business data are in the cloud, so deploy your changes to the connected environment before checking them.
Why PPAC is used here. Use PPAC to manage the developer cloud environment and check its provisioning prerequisites. Once that environment is ready, connect through the Visual Studio extensions. Check licensing, capacity, and permissions for the developer environment separately.
Compare with Microsoft images
Image description and source
Microsoft diagram of the development environment: Visual Studio, the local runtime (AOS and IIS) with batch, storage, the business database and model store in one development environment, with packages deployed to the cloud.
Source: Microsoft Learn · CC BY 4.0
OneBox · Microsoft development environment diagram. Visual Studio, the local runtime (AOS and IIS) with batch, storage, and the business database and model store sit in one development environment, and packages are deployed to the cloud.
Image description and source
Microsoft diagram comparing the LCS architecture (left) with the unified admin experience in the Power Platform admin center (right), where Finance and Operations and Dataverse are managed together. It shows administration, not the developer tool layout.
Source: Microsoft Learn · CC BY 4.0
UDE · Microsoft administration diagram. The left side shows LCS-based administration; the right side shows unified administration in PPAC. A UDE is managed on the PPAC side together with Dataverse. Microsoft documentation has no UDE-specific diagram of the developer tool layout, so use the JGS diagram above for the PC/cloud split.
In short, OneBox keeps the tools, runtime, and data in one VM, while UDE keeps the tools on the PC and the runtime and data in a cloud environment managed in PPAC.
02Tools and technology used in development
How do Visual Studio and UDE differ?
Visual Studio is the program you use for development. An integrated development environment (IDE) brings the editor, build tools, and debugger together. UDE connects the PC with those tools to a cloud runtime. IDE names the development tool; UDE describes the environment arrangement.
Image description and source
Four panels compare tool responsibilities on the developer PC in UDE: Visual Studio provides the IDE, extensions add environment connections and product tooling, the X++ compiler converts source to .NET intermediate code, and source/metadata define logic and structure. These are roles, not an installation sequence. Business transaction data is separate in the cloud runtime.
Source: Microsoft Learn
What the four parts of the diagram do
The diagram shows the four things you prepare on the developer PC in a Unified Developer Environment (UDE). They are explained in the order of the diagram panels.
① Visual Studio 2022 · the IDE you work in
Write code in Visual Studio, then build and debug it there. An integrated development environment (IDE) brings the editor, build tools, and debugger together. Visual Studio alone is different from a configured installation with the required extensions.
② Extensions · Power Platform Tools and the product extension
Power Platform Tools connects to the online environment and downloads development assets. The product extension adds features such as Application Explorer and designers.
③ X++ compiler · converts X++ to .NET intermediate code
The compiler checks syntax and converts X++ into .NET intermediate code (CIL). A build performs compilation and checks such as metadata validation to create the output used for execution. Running and testing the change still determines whether the business rules work correctly.
④ Source and metadata · business logic and form/table definitions
Source is X++ code describing business logic. Metadata defines items such as forms, tables, and fields. For example, a quantity field's type is a definition; a purchase order quantity of 10 is business data. Related source and definitions are grouped into models, and models belong to packages, which are compilation and deployment units. Later object-development episodes explain how to organize them.
Sources: Visual Studio and IDE · Extension setup · X++ compilation · Models and packages
From an edit to checking the result
Image description and source
A route map with four stations: edit and build on the developer PC, then deploy to the developer cloud and run and check the result. A dashed branch from deploy marks database synchronization when table structures change. The browser and remote debugger are operated on the PC while business code runs in the cloud. A successful build is not a passed business test.
Source: Microsoft Learn
①·② Edit and build · developer PC
Change X++ code and metadata in Visual Studio on the PC (①), then build to check and compile the output used for execution (②).
③ Deploy → ④ Run and check · developer cloud
Deployment applies changes from the PC to the runtime environment. In UDE, deploy to the cloud and try the function in the browser. Debugging lets you pause at a breakpoint and inspect values and code execution. You operate the browser and debugger on the PC; business code executes in the cloud.
DB sync · the branch from ③ Deploy (when table structures change)
Database synchronization aligns the actual database schema with table definitions. If you change a table's structure, check the synchronization requirements too. Options can combine building and deployment. The route map distinguishes the meaning and order of each operation; it does not require running each stage separately every time.
Sources: Build and database synchronization · Deployment and remote debugging
Where do you connect in Visual Studio?
Image description and source
The Tools menu contains Connect to Dataverse and Download FinOps assets. This official example shows the menu used after installing UDE extensions; no local installation or connection was performed.
Source: Microsoft Learn
This is an actual menu example from Microsoft documentation. Use Connect to Dataverse and Download Dynamics 365 FinOps assets to connect and download assets. The crayon diagram explains responsibilities; this screenshot shows where to start in the real tool.
Image description and source
The Dynamics 365 menu under Extensions in Visual Studio, including Deploy, Model Management, Build Models, Synchronize Database, Configure Metadata, and Launch Debugger.
Source: Microsoft Learn · CC BY 4.0
The full development menu is under Extensions > Dynamics 365. Build Models (② build), Deploy (③ deploy), Synchronize Database (DB sync), and Launch Debugger (④ debugging) map the stations of the route map above to actual menu items.
Browser, remote connection, and VM tools
Image description and source
A table of three tools. Web browser: sign in to the business app and check the results; used with both OneBox and UDE. Remote Desktop (RDP): open the development VM's Windows desktop; used for Visual Studio inside an Azure OneBox VM. Hyper-V: run a virtual machine on a local PC; used to run a downloaded OneBox VHD.
Source: Microsoft Learn
Use the web browser with both OneBox and UDE; use Remote Desktop (RDP) and Hyper-V with OneBox.
03How developers connect to the tools and application
- OneBox development workDeveloper PC → Remote Desktop (RDP) → Development VM
Open the Azure VM's Windows desktop and use Visual Studio inside it. For a local Hyper-V VM, you can also use the Virtual Machine Connection window.
- UDE development workVisual Studio on the PC → Authentication and tool connection → Cloud environment
Authenticate with your organizational account through the extensions and obtain metadata. Build locally, deploy the change, and debug the cloud code. Port and firewall details depend on the selected environment and are checked during setup.
- Checking the business applicationWeb browser → HTTPS → Application runtime
This is the connection used to open the application and check its results. Signing in to a OneBox Windows desktop is separate from signing in to the app, so verify their accounts and permissions independently.
These arrows describe work paths. Authentication, deployment, and debugging are not claimed to use a single protocol or port.
04The roles of LCS and Power Platform admin center
LCS and PPAC are management portals opened in a browser. Use them to prepare development environments and check their status. Write application code in Visual Studio.
Image description and source
LCS provides existing eligible projects with development VM setup/access details and assets such as downloadable VHDs. PPAC manages unified environments and apps, with licensing, capacity, permission, and developer-environment prerequisites. The browser windows are explanatory sketches, not portal screenshots, automatic migration, or a promise of provisioning eligibility.
Source: Microsoft Learn
What do you check in LCS?
Microsoft Dynamics Lifecycle Services(LCS) is a portal for managing projects and environments. In an existing active project, find Azure development VM deployment and connection details, or development assets such as a VHD for local OneBox. Available assets and deployment operations depend on account and project access.
Sources: Development VM and VHD guidance
What do you check in PPAC?
Microsoft Power Platform admin center (PPAC) manages unified environments and their installed apps. Check the target environment and the product's licensing, capacity, and permission prerequisites. UDE uses a developer-focused Sandbox; creating a generic Sandbox alone does not complete preparation. Verify the supported provisioning route and its prerequisites.
Sources: Unified administration overview · Developer-environment preparation
The LCS new-project freeze (since February 16, 2026, for new customers) is explained in section 01. Existing active LCS projects remain available. You do not always need both portals; choose the route that fits your environment and creation eligibility.
Sources: Current LCS transition guidance
05Prepare the environment in this order
Installing tools before choosing an environment can leave you with mismatched accounts and components. The setup episodes follow this sequence.
Image description and source
Five stations: check the available route, prepare identity and licensing, provision one environment (Azure OneBox with an existing LCS project, a local VHD in Hyper-V, or UDE created in PPAC), connect the tools, then confirm the first build, run, and debugging session. Choose the route before installing tools.
Source: Microsoft Learn
- Check the available development route
Check existing Lifecycle Services access and eligibility for a Unified Developer Environment.
- Prepare identity, licensing, and permissions
Confirm the Microsoft Entra organizational account, product entitlement, and environment-creation permissions. An Azure development VM also requires a subscription and the appropriate resource access.
- Provision the selected environment
Follow the relevant procedure for Azure OneBox, local VHD, or UDE.
- Configure and connect the development tools
Check the tools, extensions, and metadata on the VM or PC, then connect to the target environment.
- Check the first build, execution, and debugging session
Confirm that the change builds and runs in the intended environment.
This episode explains the structure and preparation sequence. The next setup episode starts with the required account and subscription checks for your selected route.
Documentation review: environment structure on October 16, 2026; tools and portal additions on October 17, 2026. This is a documentation-based draft. No account creation, permission changes, VM provisioning, build, or application execution was performed.
Microsoft source documents
- Application stack and server architecture
- Environment planning
- Deploy and access development environments
- Lifecycle Services project creation freeze
- Install and configure development tools
- Unified environment types and templates for finance and operations apps
- Tutorial: Provision a new environment with an ERP-based template
- Tutorial: Write, deploy, and debug X++ code
- Application Explorer
- What is Visual Studio?
- X++ language reference
- Build operations
- Models and packages
- Overview of unified admin experience for finance and operations apps
Comments
Post a Comment