A Business Central developer preparing to extend an online tenant may also need to schedule an MB-820 exam date around project deadlines. Their notes, sample AL work, and preparation checklist all need to reflect current Dynamics 365 Business Central online development practices and be checked against the latest Microsoft documentation before booking.
Consider a NAV developer asked to move a long-standing customer modification into Business Central SaaS while keeping upgrades manageable and integrations stable. The work looks familiar at first, but the extension model, AL tooling, event subscribers, automated tests, and telemetry expectations change how development decisions are made.
Microsoft introduced the Microsoft Certified: Dynamics 365 Business Central Developer Associate certification in January 2024, alongside the MB-820 exam for Dynamics 365 Business Central developers. Microsoft also announced the business applications training update through its Microsoft Learn blog, which marked an important shift: Business Central development now has a dedicated certification route rather than being treated as an extension of functional consulting or older NAV experience.
What the Business Central developer role actually covers
A Dynamics 365 Business Central developer designs, develops, tests, debugs, and maintains solutions built on Business Central. In day-to-day terms, that means creating extensions in AL, changing page and table behaviour without modifying base application objects, integrating with Microsoft and non-Microsoft systems, and troubleshooting defects that may appear only after data, permissions, workflows, or customer-specific processes are involved.
The role is broader than writing code objects. A developer needs to understand how Business Central is used by finance, sales, purchasing, warehouse, and service teams so that customisations support real business processes rather than fighting them. Developers working in Microsoft partner or ISV environments also need to think about packaging, versioning, AppSource rules where relevant, customer-specific per-tenant extensions, and supportability after Microsoft releases a new Business Central wave.
For NAV veterans, the most important change is the move away from direct modification of the base application. AL development depends heavily on extensions, events, interfaces, permissions, and testability. That shift improves upgrade paths, but it also exposes migration gotchas: old C/AL patterns that relied on direct object changes, hidden global state, or customised posting routines often need to be redesigned around subscribers, extension points, and clearer error handling.
How MB-820 maps to real developer work
MB-820 is aimed at developers who build and maintain Business Central solutions rather than consultants who primarily configure the application. The exam expects familiarity with the AL language, Visual Studio Code tooling, Business Central development environments, application lifecycle tasks, debugging, testing, permissions, performance considerations, and integration patterns.
In practical terms, those topics map closely to common project work. Creating table extensions and page extensions reflects how developers add fields and expose them to users. Writing event subscribers reflects how Business Central extensions react to standard application behaviour without modifying Microsoft-owned code. Building codeunits, APIs, reports, and tests reflects the delivery work expected in customer projects and ISV products.
A simple event-subscriber planning checklist shows the kind of thinking developers need to practise: responding to a business event at the right point, keeping logic isolated, and avoiding fragile changes to standard posting code.
Example — event subscriber for customer validation
- Identify the business event that should trigger the validation.
- Confirm that the logic can be handled through an extension point instead of a base-object change.
- Keep the validation rule isolated so it can be tested, reviewed, and maintained separately.
- Write an error message that is clear enough for users and support teams to understand.
- Review the rule against permissions, localisation requirements, and the customer process it supports.
This checklist is intentionally small, but it illustrates a larger exam and project skill: the developer must know where to attach logic, how to avoid unnecessary base-object changes, and how to produce errors that are clear enough for users and support teams. In a real extension, this logic would usually be supported by tests and reviewed against business rules, permissions, and localisation requirements.
Beta-exam realities and how to prepare without immediate feedback
MB-820 was introduced as a beta exam. A beta exam is used by Microsoft to evaluate question quality and exam coverage before the exam becomes generally scored in the normal way. Candidates should expect preparation to feel less predictable than for a mature exam because learning materials, practice questions, and community write-ups are often limited at the start.
The main preparation risk is relying on immediate score feedback as the primary learning loop. With beta exams, results may be delayed while Microsoft analyses exam data. That means candidates need to validate readiness before sitting the exam by building working extensions, asking peers to review code, creating small project briefs, and using Microsoft documentation to check whether their implementation choices match current Business Central development practices.
A useful approach is to practise against realistic delivery tasks rather than memorising feature names. For example, a candidate could build a small per-tenant extension that adds a field to a customer process, exposes the field on a page, enforces a rule through an event subscriber, adds a permission set, writes a test codeunit, and reviews telemetry or debugger output when something fails. That kind of project reveals gaps far better than passive reading.
Setting up a practice environment that teaches the right skills
Preparation is strongest when the lab environment resembles the way Business Central development is actually done. A practical setup usually includes a Business Central SaaS sandbox or a container-based environment, Visual Studio Code, the AL Language extension, a source-control repository, and a small sample app that can be repeatedly changed, published, tested, and debugged.
Telemetry is worth enabling early rather than treating it as an advanced topic. In real projects, Business Central performance and reliability issues rarely announce themselves as clean syntax errors. Developers often need to isolate slow page interactions, review long-running queries, inspect errors from background sessions, and use Application Insights data to understand what happened in a customer environment.
Several pitfalls appear repeatedly in exam-style tasks and in project reviews. Missing permission sets can make a technically correct feature unusable. Skipping testability codeunits makes refactoring risky. Misusing single-instance codeunits can create state-related defects that are hard to reproduce. Weak error handling can leave users with messages that do not explain what action to take next.
Example — a minimal test codeunit pattern
- Define the business rule that the extension must enforce.
- Create a representative test record or scenario that exercises that rule.
- Trigger the validation through the same user-facing behaviour the extension supports.
- Verify that the expected error appears when the rule is violated.
- Use the result to decide whether the extension is safe to refactor or extend further.
The checklist demonstrates why Business Central development is more than creating objects that compile. It asks whether the extension behaves predictably when a business rule is violated. Candidates preparing for MB-820 should be comfortable interpreting this style of validation because testing, debugging, and maintainability are central to professional Business Central development.
Choosing between MB-820, MB-800, and PL-400
Not every Business Central professional needs the same certification path. MB-820 is the clearest fit when the role involves AL development, extension architecture, debugging, testing, integrations, and maintaining code across Business Central updates. It suits NAV and Business Central developers, solution architects who still work close to code, and .NET or C# developers moving into Business Central product development.
By contrast, MB-800 is aligned with the Business Central functional consultant role. It fits professionals who gather requirements, configure finance and operational processes, support implementation decisions, and translate business needs into system setup. PL-400 is a better match when most of the work is Power Platform development, Dataverse, custom connectors, canvas or model-driven apps, and low-code extensibility rather than AL-based Business Central extensions.
The decision is often clearer when framed around the work product. If the deliverable is an AL extension, MB-820 is the relevant path. If the deliverable is configured Business Central processes and user adoption, MB-800 is usually more appropriate. If the deliverable is a Power Platform solution that integrates with Business Central, PL-400 may be the stronger fit.
When instructor-led preparation makes sense
Self-study can work well for developers who already have a stable lab environment, current AL experience, and enough time to build practice projects. It is less efficient when a learner is moving from C/AL to AL, coming from .NET without Business Central product knowledge, or trying to prepare while also supporting customer delivery work.
An instructor-led course is useful when it adds structure, sequencing, and guided practice rather than simply repeating documentation. A strong MB-820 preparation path should help learners connect exam topics to practical tasks: extension design, eventing, debugging, testing, permissions, performance, integrations, and deployment decisions. Readynez offers an instructor-led Dynamics 365 Business Central Developer MB-820 course for developers who want a guided route through those skills.
A practical study plan for MB-820
A balanced preparation plan should start with the official exam page, then move quickly into hands-on development. Reading documentation is necessary, but MB-820 preparation becomes meaningful when the candidate can create, publish, debug, test, and improve a working extension without relying on step-by-step instructions.
- Review the official MB-820 exam page and note the current skills measured.
- Set up a Business Central sandbox or container with Visual Studio Code and the AL Language extension.
- Build a small extension that includes a table extension, page extension, codeunit, event subscriber, and permission set.
- Add automated tests for the main business rule and verify that failures are understandable.
- Debug the extension, inspect runtime behaviour, and review telemetry where available.
- Refactor the extension for upgradeability, clearer errors, and cleaner separation of responsibilities.
This kind of plan gives training managers a more reliable view of readiness than attendance alone. It also helps developers identify whether their gaps are in Business Central concepts, AL syntax, test design, integration patterns, or operational troubleshooting.
Building Business Central developer capability beyond the exam
MB-820 matters because it gives Business Central developers a dedicated credential, but the larger value is the discipline it encourages. Sustainable Business Central development depends on extensions that survive upgrades, permissions that match user roles, tests that protect critical logic, and telemetry that helps teams diagnose issues after deployment.
The most effective next step is to compare the exam objectives with current project work and build a small extension that exercises the weak areas. Teams planning several Microsoft training paths can also evaluate Readynez Microsoft Unlimited as part of a broader training plan, while keeping the immediate focus on hands-on AL practice and current Microsoft guidance.
