Study guide

1.1 Cloud vs On-Premises Architecture & Deployment Typologies

Microsoft Dynamics 365: Finance and Operations Apps Developer Associate MB-500

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Cloud & Ecosystem Architecture

1.1 Cloud vs On-Premises Architecture & Deployment Typologies 1.2 Microsoft Ecosystem Integration & Extensibility Boundaries 1.3 Lifecycle Services (LCS) & Implementation Portal

2 Chapter 2: ALM, Environments & Unified Developer Experience

2.1 Package Deployment & Servicing 2.2 Unified Developer Experience (UDE) & Power Platform Admin Center 2.3 Environment Management & Governance

3 Chapter 3: Visual Studio Development & Metadata

3.1 Visual Studio Extension Models & Packages 3.2 Application Explorer & Element Designers 3.3 Database Synchronization & Visual Studio Debugging

4 Chapter 4: Azure DevOps Version Control & CI/CD

4.1 Version Control Architecture: TFVC vs Git in F&O 4.2 Branching, Merging & Conflict Resolution 4.3 CI/CD Build Pipelines & Artifact Generation

5 Chapter 5: UI Elements: Forms, Menus & Labels

5.1 Form Design & Form Patterns 5.2 Menus, Menu Items & Navigation 5.3 Label Files & Localization

6 Chapter 6: Data Model: Tables & Relational Design

6.1 Table Design & Extension 6.2 Views, Queries & Maps 6.3 Data Entity Design & Modeling

7 Chapter 7: Classes, Attributes & AOT Modifiers

7.1 Class Architecture & Access Modifiers 7.2 Attributes & Reflection 7.3 Event Handlers & Pre/Post Method Events

8 Chapter 8: X++ Core Programming & CRUD Operations

8.1 X++ Syntax, Control Flow & Global Functions 8.2 Data Manipulation & CRUD Logic 8.3 Best Practice Rules & Compiler Diagnostics

9 Chapter 9: Advanced OOP, Chain of Command & Extensibility

9.1 OOP Principles & QueryBuilder Class 9.2 Chain of Command (CoC) Implementation 9.3 Extensibility Patterns & Non-Breaking Changes 9.4 Event Handler Classes & Delegate Architecture 9.5 Variable Scoping, Declaration Placement & Object Lifetime

10 Chapter 10: F&O Frameworks & SysTest Unit Testing

10.1 SysOperation Framework Architecture 10.2 Workflow Framework & SysExtensionSerializer 10.3 SysTest Framework & Test Explorer

11 Chapter 11: Reporting Architecture & SSRS Reports

11.1 Reporting Architecture & Datastores 11.2 Report Data Providers & Contracts 11.3 SSRS Report Design, Deployment & Security 11.4 Determining When to Use a Specific Reporting Tool or Platform

12 Chapter 12: Business Intelligence, Workspaces & Electronic Reporting

12.1 Electronic Reporting (ER) Framework 12.2 Power BI Integration & Analytical Workspaces 12.3 Workspaces, Tiles, Lists & KPIs 12.4 Excel Integration & Office App

13 Chapter 13: Integration Patterns & Service Endpoints

13.1 Integration Pattern Evaluation & API Selection 13.2 Custom Services & SOAP/REST Endpoints 13.3 Consuming External Services & REST/SOAP APIs

14 Chapter 14: Data Management Framework (DMF) & Batch Processing

14.1 DMF Concepts, Projects & Sequencing 14.2 Entity Change Tracking & Recurring Integrations 14.3 Composite Entities & Batch OData API 14.4 Monitoring Entity Status, Availability & Job Execution

15 Chapter 15: Power Platform, Business Events & Azure Integrations

15.1 Dual-Write & Virtual Entities 15.2 Business Events Framework 15.3 Azure Key Vault Integration & Secure Storage

16 Chapter 16: Role-Based Security & Extensible Data Security

16.1 Role-Based Security Architecture 16.2 Extensible Data Security (XDS) Policies 16.3 Security Enforcement & Best Practices

17 Chapter 17: Performance Optimization & Data Access Patterns

17.1 Table & Form Caching Mechanisms 17.2 Temporary Tables & Set-Based Operations 17.3 Query Tuning, Indexes & Concurrency 17.4 Diagnostics: Trace Parser, Async & Sandbox Frameworks 17.5 Tuning Variable Scope, Buffer Lifetime & Memory Pressure

1.1 Cloud vs On-Premises Architecture & Deployment Typologies

Key Takeaways Explain This Topic AI

Dynamics 365 Finance and Operations in the cloud operates as a fully managed Software as a Service (SaaS) platform hosted on Microsoft Azure, where Microsoft manages hypervisor clustering, operating system patching, Azure SQL automated point-in-time recovery, and high availability.

The on-premises deployment typology, known as Local Business Data (LBD), runs on customer-provided hardware orchestrated via a standalone Service Fabric cluster, requiring customer IT teams to manage physical infrastructure, SQL Server Always On Availability Groups, and Windows Server patching.

Cloud deployments rely on Microsoft Entra ID (formerly Azure Active Directory) for modern OAuth 2.0 authentication, whereas LBD deployments strictly mandate Active Directory Federation Services (AD FS) residing in the local domain.

Several cloud-native capabilities cannot function in on-premises LBD deployments, notably embedded Power BI analytical workspaces, automated Microsoft continuous One Version service updates, Azure Synapse Link for Dataverse, and direct cloud machine learning intelligence.

The Application Object Server (AOS) executes as a multi-threaded web application hosting both interactive browser sessions and headless background batch server jobs across distinct batch groups with server affinity controls.

Last updated: September 2026

Cloud vs On-Premises Architecture & Deployment Typologies

Quick Answer: The MB-500 exam requires developers and technical architects to understand the structural divide between Cloud (SaaS) and On-Premises (Local Business Data / LBD) deployments. In the Cloud, Microsoft fully manages infrastructure, high availability (HA), disaster recovery (DR), Azure SQL Database, and Azure Blob storage, while enforcing the One Version continuous update cadence and providing cloud-native features like embedded Power BI . In contrast, LBD deployments require the customer to host and maintain their own hardware, deploy a standalone Service Fabric cluster , configure Active Directory Federation Services (AD FS) , maintain SQL Server Always On Availability Groups , and manage local file storage. LBD lacks embedded Power BI, automated cloud updates, direct machine learning, and Azure Synapse Link.

1. Enterprise Architectural Overview: Cloud (SaaS) vs. On-Premises (LBD)

Dynamics 365 Finance and Operations (F&O) is architected as an enterprise multi-tier business application consisting of a web-based client presentation tier, an application compute tier ( Application Object Server / AOS ), and a relational data tier. While the underlying business logic written in X++ and compiled into Common Intermediate Language (.NET CIL) remains largely identical, the infrastructure topologies, data persistence mechanisms, security perimeters, and operational maintenance responsibilities diverge sharply between deployment types.

Architectural Tier Comparison

Architectural Tier Cloud Deployment (Microsoft-Managed Azure SaaS) On-Premises Deployment (Local Business Data / LBD)

Hosting Model Fully managed Microsoft Azure cloud subscription Customer or partner-owned physical/virtual data center

Orchestration & Compute Microsoft-managed Azure Service Fabric / Azure infrastructure Standalone Windows Server Service Fabric cluster managed by customer

Database Tier Azure SQL Database (Business Critical / Hyperscale tier) with automatic tuning SQL Server Enterprise Edition configured with Always On Availability Groups

Storage Tier Azure Blob Storage (attachments, DMF staging, temporary files) Local network Server Message Block (SMB) UNC file shares or SAN

Identity & Authentication Microsoft Entra ID (Azure AD) using OAuth 2.0 Bearer tokens On-premises Active Directory Domain Services (AD DS) via AD FS

High Availability (HA) Built-in Azure zone redundancy, automatic node failover, 99.9% SLA Customer-configured server redundancy, network load balancers, and WSFC

Disaster Recovery (DR) Microsoft-orchestrated Geo-replication and automated point-in-time restore Customer-architected secondary data center replication and backup validation

Servicing & Updates Automated One Version continuous quality updates delivered via LCS Manually downloaded and applied deployable packages via LCS Local Agent

  • 2. Core Architectural Components
  • Application Object Server (AOS)

The Application Object Server (AOS) is the core runtime execution engine for Dynamics 365 F&O. It runs as an ASP.NET Core / .NET application hosted inside Internet Information Services (IIS) worker processes or Service Fabric guest executables.

Stateless Design: In both cloud and on-premises environments, AOS nodes are strictly stateless. User session states, active forms, and temporary cursors are preserved across database tables or distributed memory caches rather than tied to a single physical machine.

Load Balancing: Client traffic is distributed across multiple AOS nodes using Azure Application Gateway / Azure Load Balancers in the cloud, or hardware/software load balancers (such as F5 or Windows Server Network Load Balancing) in LBD.

Dedicated Batch Server Roles & Processing

AOS instances can be configured to act as interactive web servers, dedicated background batch servers, or a hybrid of both:

Batch Processing Architecture: The batch framework processes asynchronous tasks, scheduled jobs, and integration pipelines without impacting interactive UI responsiveness.

Batch Groups & Server Affinity: Developers and administrators organize batch tasks into Batch Groups . By binding specific batch groups to designated AOS instances, organizations ensure that heavy computational tasks (such as overnight Master Planning, depreciation runs, or massive DMF imports) do not consume CPU or memory allocated to user-facing interactive AOS nodes.

Priority-Based Batch Scheduling: Modern F&O uses priority-based scheduling to prevent low-priority maintenance jobs from starving business-critical financial postings.

SQL Server Reporting Services (SSRS) Architecture

Cloud SSRS: In cloud SaaS environments, SSRS runs on dedicated microservice nodes managed entirely by Microsoft. Reports are rendered into PDF, Excel, or Word formats and streamed directly back to the browser or routed to physical on-premises network printers via the Document Routing Agent (DRA) .

On-Premises SSRS: In LBD deployments, SSRS must be installed and configured on customer-provided Windows Server nodes integrated with on-premises SQL Server instances and configured within the local Service Fabric cluster topology.

Data Management Framework (DMF) Integration Boundaries

The Data Management Framework (DMF) provides high-volume asynchronous batch import/export, data entity staging, and integration packages:

Cloud Storage Boundary: In the cloud, the DMF staging pipeline relies entirely on Azure Blob Storage . When an integration pushes a data package via the DMF REST API, the package is placed in a secure Azure Blob container using Shared Access Signatures (SAS). AOS batch workers retrieve the package, parse the source files into staging tables, and commit them to target transactional tables.

On-Premises Storage Boundary: In LBD, Azure Blob Storage is not accessible for internal staging. Instead, the Service Fabric AOS nodes utilize a high-availability customer-managed SMB network share (UNC path) . If this network share experiences latency or permissions misconfigurations, DMF batch jobs fail immediately.

3. Capabilities Unavailable or Restricted in Local Business Data (LBD)

One of the most frequently tested areas on the MB-500 exam is knowing which advanced capabilities cannot run in an on-premises LBD topology. Because LBD lacks direct native connectivity to Microsoft's hyperscale cloud fabric, the following features are completely unsupported or severely restricted:

Embedded Power BI Analytical Workspaces:

In cloud deployments, rich Power BI analytical reports and dashboards are embedded directly inside F&O workspaces via Azure Analysis Services and Power BI DirectQuery.

In LBD, embedded Power BI is unsupported . Users must rely on standard operational SSRS reports, Electronic Reporting (ER), or build external standalone Power BI Desktop models connecting via custom SQL views or OData endpoints.

Automated Continuous Updates (One Version):

Cloud environments receive automated monthly or bi-monthly service updates orchestrated directly by Microsoft Lifecycle Services (LCS).

In LBD, automated servicing is unavailable. The customer IT team must manually download Software Deployable Packages (SDPs) from LCS, distribute them to local infrastructure, and execute the installation via the on-premises Service Fabric deployment scripts and LCS Local Agent.

Azure Synapse Link & Microsoft Fabric Direct Export:

Cloud environments can continuously stream transactional entities to Azure Data Lake Storage Gen2 and Microsoft Fabric in near-real-time using Azure Synapse Link.

LBD does not support Synapse Link. Organizations requiring external analytics must rely on legacy data export strategies, such as custom batch exports or direct database staging.

Direct Cloud Machine Learning & Cognitive Intelligence:

Features relying on Azure Machine Learning (e.g., Cash Flow Forecasting, Customer Payment Predictions, Intelligent Order Management recommendations) are native to the cloud.

These cognitive predictive services cannot execute natively within an isolated on-premises LBD data center.

Mobile Workspace Push Notifications:

While the Dynamics 365 Unified Operations mobile app can connect to LBD via configured edge proxies, cloud push notification hubs and background push triggers are unavailable.

  • 4. Scenario Walk-Through: Architectural Topology Selection
  • Scenario: Global Manufacturing & Retail Conglomerate (Contoso Global)

Contoso Global operates corporate headquarters in North America with 45 retail stores and 4 manufacturing facilities. They also operate an ammunition and defense contract subsidiary governed by strict national data sovereignty regulations prohibiting any financial, bill of materials (BOM), or inventory records from leaving on-premises domestic hardware.

Architectural Decision Process:

Corporate & Retail Entities (Cloud SaaS):

Deployed on Microsoft-managed Azure Cloud .

Leverages Azure SQL Database with zone-redundant high availability and automated disaster recovery across paired regions.

Enables Embedded Power BI for real-time retail store sales performance monitoring.

Integrates with Power Apps and Power Automate via Dataverse Dual-write .

Enforces Microsoft Entra ID authentication with Conditional Access and Multi-Factor Authentication (MFA).

Defense Contract Subsidiary (Local Business Data / LBD):

Deployed as an on-premises LBD cluster on physical server racks within the subsidiary's hardened data center.

Managed via an on-premises Service Fabric standalone cluster .

Authenticated exclusively against local Active Directory Domain Services via AD FS .

Data stored in customer-administered SQL Server Enterprise with Always On Availability Groups .

Package staging routed through a high-availability local SMB UNC network share .

Custom analytical reporting delivered via SSRS and Electronic Reporting (ER) rather than embedded Power BI.

5. Real-World Exam Traps: Cloud vs. LBD

Warning

Exam Trap 1: Assuming LBD can run Embedded Power BI Workspaces Many exam candidates assume that since Power BI Report Server exists for on-premises reporting, F&O LBD supports embedded analytical workspaces. This is false on the MB-500. Embedded Power BI analytical workspaces require the Azure-hosted Power BI service and entity store data feeds, which are strictly unavailable in LBD.

Warning

Exam Trap 2: Believing Cloud SaaS Customers Can Indefinitely Pause Updates Under Microsoft's One Version policy in the cloud, customers cannot permanently freeze their application version. Organizations may pause up to three consecutive monthly service updates, but LCS will enforce a mandatory update before an environment falls out of Microsoft support boundaries. In contrast, LBD customers can remain on an older build indefinitely, albeit at the cost of losing support and security patches.

Warning

Exam Trap 3: Confusing Identity Management Architecture The exam frequently presents questions where external systems attempt to authenticate against an on-premises LBD instance using Microsoft Entra ID (Azure AD) client credentials. LBD environments rely on Active Directory Federation Services (AD FS) for claim-based identity; they do not authenticate against Microsoft Entra ID natively.

Warning

Exam Trap 4: DMF Storage Misconceptions in LBD Candidates often assume the Data Management Framework operates identically behind the scenes. In Cloud SaaS, DMF packages are staged in Azure Blob Storage containers via SAS tokens. In LBD, DMF staging occurs on local customer-configured SMB file shares . Writing X++ code that explicitly assumes Azure Blob REST storage APIs without abstracting through the DMFPackageExporter / DMFPackageImporter frameworks will fail in on-premises environments.

Loading diagram... Finance and Operations Architectural Topology: Cloud vs. On-Premises (LBD)