Study guide

1.2 Customization Lifecycle: Cloud (SaaS) vs. On-Premises

Microsoft Dynamics 365 Business Central Developer MB-820

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Business Central Architecture & Platform Foundation

1.1 Business Central Architecture & Extensions Model 1.2 Customization Lifecycle: Cloud (SaaS) vs. On-Premises 1.3 Base Application, System Application & AppSource

2 Chapter 2: Development Environment & Configuration

2.1: Development Environment Setup: VS Code, AL: Go! Projects & Sandboxes 2.2: AL Configuration Files: app.json & launch.json Parameters 2.3: Multi-Root Workspaces & Project Dependencies

3 Chapter 3: Extension Lifecycle: Debugging, Deployment, Multilanguage & Maintenance

3.1 Debugging & Snapshot Debugging in Visual Studio Code 3.2 Extension Deployment & Schema Synchronization Modes 3.3 Multilanguage Development with XLIFF & Translation Files 3.4 Extension Maintenance, Deprecation & Breaking Changes

4 Chapter 4: Tables, Table Extensions & Data Modeling

4.1: Building Tables, Fields, Keys & Data Types 4.2: Table Extensions & Table Modifications 4.3: FlowFields, FlowFilters & Table Relations 4.4: Enums, Enum Extensions & Extensible Types

5 Chapter 5: Pages, Page Extensions & Role Centers

5.1: Page Types, Anatomy & Control Structure 5.2: Building Card, List & Document Pages 5.3: Page Extensions & Page Customizations 5.4: Role Centers, Headlines & Cue Data Modeling

6 Chapter 6: Reports & Document Generation

6.1 Report Architecture, DataItems & Dataset Design 6.2 Report Layouts: RDLC, Word, Excel & Multilanguage 6.3 Document Reports & Request Page Programming 6.4 Processing-Only Reports & Report Substitutions

7 Chapter 7: XMLports & Data Exchange

7.1 XMLport Architecture, Formats & Properties 7.2 XMLport Node Hierarchy, Triggers & Stream Manipulation

8 Chapter 8: Codeunits, Events, Triggers & Interfaces

8.1 Codeunit Types, Execution & SingleInstance Codeunits 8.2 Events, Publishers, Subscribers & Event Isolation 8.3 Interfaces, Polymorphism & Dynamic Codeunit Invocation 8.4 Installation & Upgrade Codeunits, Data Transfer & Archive

9 Chapter 9: Entitlements, Permissions & Queries

9.1 Permission Sets & Permission Set Extensions 9.2 Inherent Permissions, Inherent Entitlements & Security Scoping 9.3 Query Objects: Joins, Aggregation & Query as Report Data Source

10 Chapter 10: UI Customization, User Assistance & Onboarding

10.1 Profile Objects & Custom Page Views in AL 10.2 User Assistance: ToolTips, Teaching Tips & In-App Tours 10.3 Assisted Setup, Guided Experience & Onboarding Checklists

11 Chapter 11: Business Central Design Patterns & Data Process Model

11.1 Functional Table Types: Master Data, Supplemental & Setup Patterns 11.2 Document Standards: Header, Line, History & Journal Architectures 11.3 Data Process Model & Posting Routine Architecture

12 Chapter 12: AL Language Fundamentals, Data Types & Variables

12.1 AL Syntax, Variable Scope, Primitive & Complex Data Types 12.2 Expressions, Control Flow Statements & Built-in Functions 12.3 Access Modifiers (Public, Internal, Local) & Code Scoping

13 Chapter 13: Data Manipulation, Streams & Error Handling

13.1 Record Operations: Get, FindSet, ModifyAll & Filter Functions 13.2 Streams, File Management & TempBlob 13.3 Error Handling: ErrorInfo, TryFunctions & Collectible Errors

14 Chapter 14: Testing, Test Toolkit & Automation

14.1 Testing Architecture & the Test Toolkit 14.2 Authoring Test Codeunits & UI Handler Functions

15 Chapter 15: Telemetry, Performance Optimization & Analyzers

15.1 Telemetry Configuration & Azure Application Insights 15.2 Custom Telemetry Signals with Session.LogMessage & KQL 15.3 Performance Profiler, SetLoadFields & Query Optimization 15.4 AL Analyzers: CodeCop, AppSourceCop, UICop & PTECop

16 Chapter 16: REST Web Services & JSON in AL

16.1 HttpClient, HttpRequestMessage & REST API Consumption 16.2 JSON Processing: JsonObject, JsonArray, JsonValue & JsonToken

17 Chapter 17: API Pages, OData, Read Scale-Out & OAuth

17.1 API Pages (PageType=API), OData Web Services & REST Endpoints 17.2 Bound and Unbound OData Actions with [ServiceEnabled] 17.3 Read Scale-Out Architecture & DataAccessIntent Configuration 17.4 Microsoft Entra ID App Registrations & OAuth 2.0 Integration

1.2 Customization Lifecycle: Cloud (SaaS) vs. On-Premises

Key Takeaways Explain This Topic AI

Microsoft delivers two major release waves annually (Wave 1 in April, Wave 2 in October) and monthly cumulative quality/security updates.

Preview sandboxes become available 30 days prior to major release General Availability (GA), allowing partners to test extensions against the upcoming runtime.

Microsoft executes automated validation pipelines on all installed AppSource and Per-Tenant Extensions (PTE) in customer cloud environments, alerting administrators to compilation breakages.

Business Central Online (SaaS) enforces strict runtime boundaries: direct SQL access, local file system I/O, and unrestrained .NET Framework interop are completely blocked in AL.

On-Premises deployments grant full server and SQL administration control but transfer complete responsibility for infrastructure, high availability, telemetry setup, and manual update patching to the customer.

Last updated: August 2026

1.2 Update Lifecycle, Release Waves & Cloud vs. On-Premises

Understanding the software release cadence and operational differences between Business Central Online (Software as a Service / SaaS) and Business Central On-Premises is critical for developers. Developers must design extensions that remain resilient across automated platform updates and respect the strict security and resource sandbox boundaries of the public cloud.

1. Microsoft Release Cadence & Update Cycles

Microsoft maintains a continuous delivery model for Business Central Online, structured around two major release waves each year and regular monthly updates: +-----------------------------------------------------------------------------------------+

  • | ANNUAL RELEASE TIMELINE |
  • +-----------------------------------------------------------------------------------------+
  • JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC
  • ▲ ▲ ▲ ▲
  • │ │ │ │
  • Wave 1 Preview Wave 1 GA Wave 2 Preview Wave 2 GA
  • (30-Day Window) (Major Update) (30-Day Window) (Major Update)
  • └───────┼───────────────────────────────────────┴───────┼──────────────────
  • │ │
  • Monthly Minor Updates Monthly Minor Updates
  • (Cumulative Bug Fixes & (Cumulative Bug Fixes &
  • Regulatory Patches) Regulatory Patches)
  • Major Release Waves (Wave 1 & Wave 2)

Release Schedule: Wave 1 is released in April ; Wave 2 is released in October .

Scope of Changes: Major releases introduce new AL language capabilities, new platform features, broad user interface updates, structural data schema enhancements, and deprecated object retirements.

Runtime Compilation: Major updates may increment the AL compiler platform version (e.g., from runtime 13.0 to 14.0 ), introducing new compiler rules, warnings, and analyzer checks.

Update Window Management: Administrators can configure update windows in the Business Central Admin Center (specifying the exact hours during low-traffic periods when the update should apply) and can postpone major updates for up to a designated grace period (typically 60 days post-GA).

Minor Monthly Updates

Release Schedule: Shipped monthly between major release waves.

Scope of Changes: Minor updates deliver critical bug fixes, regulatory and tax compliance patches, performance optimizations, and non-breaking application improvements.

Zero-Downtime Rollout: In the cloud, monthly updates are applied automatically by Microsoft with near-zero downtime, applying schema updates and recompiling active extensions seamlessly.

The 30-Day Preview Sandbox Window

Approximately 30 days prior to the General Availability (GA) of a major release wave (March for Wave 1, September for Wave 2), Microsoft provisions preview platform builds in Azure:

Administrators and developers can create new Sandbox (Preview) environments via the Business Central Admin Center.

Preview sandboxes run the upcoming major release platform and application bits.

Developers deploy their production Per-Tenant Extensions (PTE) and AppSource apps into the preview sandbox to test end-to-end regression workflows before the production tenant is upgraded.

Loading diagram... Automated Extension Validation & Major Release Lifecycle

2. Automated Extension Validation Pipelines

In Business Central Online, Microsoft guarantees that platform upgrades do not corrupt customer data or cause unhandled runtime crashes. To ensure this, Microsoft executes an Automated Extension Validation Pipeline against all production and sandbox environments in advance of scheduled major upgrades.

How Automated Validation Operates

Automated Background Compilation: The validation service takes copies of all active .app packages installed on the tenant (including PTEs and AppSource ISV apps) and attempts to compile and link them against the upcoming major version metadata.

Schema Compatibility Check: The engine verifies that table extensions, companion tables, and key definitions can be synchronized cleanly without data loss.

Failure Notifications: If an extension fails compilation (for example, due to referencing a removed obsolete field or relying on an altered procedure signature):

An automated high-priority alert email is dispatched to all registered notification recipients configured in the Business Central Admin Center.

A failure telemetry event is emitted to the customer's connected Azure Application Insights resource — LC0021 ( Extension failed to compile ), LC0023 ( Extension failed to update ), or the runtime event RT0010 ( Extension Update Failed ).

The upgrade of the customer's production environment is paused until the incompatible extension is updated or uninstalled.

Remediation Requirement: The developer must resolve the breaking changes in AL, update the version in app.json , and upload the updated package prior to the expiration of the upgrade grace window.

3. Deprecation Architecture & Obsolete Lifecycle

To prevent sudden breaking changes from destabilizing extensions during major updates, Microsoft enforces a strict multi-wave Deprecation Policy using the ObsoleteState , ObsoleteReason , and ObsoleteTag AL attributes. // Example of a Table Field undergoing Microsoft's Deprecation Lifecycle:

  • tableextension 50100 "Custom Customer Ext" extends Customer
  • {
  • fields
  • {
  • field(50100; "Legacy Tax Code"; Code[20])
  • {
  • Caption = 'Legacy Tax Code';
  • DataClassification = CustomerContent;
  • ObsoleteState = Pending;
  • ObsoleteReason = 'Replaced by standard Tax Group Code in compliance with Wave 2 tax engine.';
  • ObsoleteTag = '24.0';
  • }
  • }
  • }
  • The Three Deprecation States

ObsoleteState = No (Active): The object, field, procedure, or enum value is fully supported and active.

ObsoleteState = Pending (Deprecation Phase): The element remains fully functional at runtime, but the AL compiler flags every reference to it with a compiler warning ( AL0432 ). Microsoft guarantees that an element marked Pending will remain in the codebase for at least 1 full year (2 major release waves) before removal.

ObsoleteState = Removed (Retired Phase): The element's code logic or field definition is permanently removed. Any extension attempting to reference a Removed object or field will fail compilation with a hard error ( AL0433 — "{0} '{1}' is removed." ).

4. Cloud (SaaS) vs. On-Premises: Technical Comparison

While AL is the common programming language across all deployment models, Business Central Online (SaaS) imposes architectural restrictions to guarantee cloud multitenancy security, high availability, and resource governance.

Technical Dimension Business Central Online (SaaS) Business Central On-Premises

Hosting & Infrastructure Fully managed by Microsoft on Azure; auto-scaled elastic computing. Self-hosted on physical servers, Hyper-V, VMware, or Azure VMs.

Database Access Direct SQL connection/T-SQL queries strictly forbidden. Access via APIs, OData, and queries. Direct SQL Server Management Studio (SSMS) access and T-SQL querying allowed.

File System Access No access to local host drives ( C:\ ). File operations use InStream/OutStream and Cloud Storage. Direct access to local and network file paths ( System.IO.File , UNC paths).

.NET Framework Interop Forbidden ( "target": "Cloud" ). No DotNet variables or native DLL loading. Allowed ( "target": "OnPrem" ). Direct DotNet interop supported if configured.

Background Execution Limits Page background tasks default to a 2-minute timeout (10-minute maximum); a maximum of 10 background sessions run concurrently per environment. Configurable timeouts on the NST instance; hardware-limited concurrency.

Platform Updates Fully automated by Microsoft (major waves + monthly patches). Manually applied by partner/DBA via cumulative update installers and scripts.

Telemetry Monitoring Native Azure Application Insights integration via Admin Center telemetry key. Windows Event Log, SQL Server Profiler, or optional Application Insights.

Licensing Model Named-user monthly subscription (Cloud Solution Provider / CSP). Named user subscription, perpetual licenses, or Bring-Your-Own-License (BYOL).

Key Developer Constraints in Cloud (SaaS)

File Management via Streams: SaaS developers cannot use File.Create('C:\export.csv') . All file import/export logic must be handled using InStream , OutStream , TempBlob codeunits, or direct streaming to Azure Blob Storage / SharePoint REST endpoints.

Isolated Storage: For sensitive settings (such as integration API secrets, OAuth tokens, and encryption keys), developers must use the IsolatedStorage API ( IsolatedStorage.Set() , IsolatedStorage.Get() ) rather than writing credentials into custom setup tables.

Operational Request Throttling: Cloud environments enforce operational request quotas. OData v4 calls that exceed the environment rate limit (600 requests per minute in production, 300 in a sandbox) return HTTP Status Code 429 (Too Many Requests) .