Exam prep guide PL-400: Microsoft Power Platform Developer

TL;DR: PL-400 is the pro-developer exam in the Power Platform family. There are six skill areas, and the weight sits squarely on Extend the platform (30–35%): plug-ins, custom APIs, the Dataverse Web API and Azure Functions. It runs 100 minutes, you need 700 to pass, and it expects real code (C#, JavaScript, TypeScript). Learn the six areas below and remember the golden rule: hands-on beats reading. Skills measured as of 19 March 2026.

So the Power Platform certification train keeps rolling, and it is time to either grab the chance to learn, or to prove that you already know, the developer side of the platform. The skills measured got refreshed on 19 March 2026, old knowledge is retired and new bits take its place… so… ready, set, go.

This is my prep guide for PL-400: Microsoft Power Platform Developer, the associate exam behind the Microsoft Certified: Power Platform Developer Associate badge.

One honest warning if you are coming straight from PL-900 Fundamentals: PL-400 is a different animal. It is written for people who build. C# plug-ins, JavaScript client scripting, PCF components, custom connectors, Azure. Microsoft expects you to have real hands-on time with Power Platform, JavaScript, JSON, TypeScript, C#, HTML, RESTful Web APIs, Visual Studio, VS Code and Azure. If that is your day job, you will be fine.

Exam at a glance

• Level: Intermediate / Associate
• Length: 100 minutes, proctored (can include interactive lab components)
• Passing score: 700 out of 1000
• Price: 165 USD, varies by country
• Renewal: every 12 months, free, through an online assessment on Microsoft Learn
• Skills measured version: as of 19 March 2026
• Certification: Microsoft Certified: Power Platform Developer Associate
• Official study guide: Exam PL-400 study guide

New to Microsoft certification?

For a gentler introduction before PL-400, start with my PL-900 Microsoft Power Platform Fundamentals exam prep guide.

If exams like this are new to you, start with the official Microsoft learning content. It gives you a foundation and a fair shot at passing. On exam day, read every question slowly. A lot of PL-400 items are scenario questions of the “which extension point, which pipeline stage, which registration is correct” kind, so take your time and pick the answer the platform actually supports, not the one that merely sounds right.

The certification page gathers the self-paced learning paths under Prepare for the exam. They line up almost one to one with the skills measured:

• Introduction to developing with Microsoft Power Platform
• Use advanced techniques in canvas apps to perform custom updates and optimization
• Extend the user experience with client scripting and command bar customization
• Build basic code components with the Power Apps Component Framework
• Extending Power Platform Dataverse
• Automate a business process with expressions and Dataverse actions using Power Automate
• Integrate with Dataverse and Azure

Watch the prep videos. Microsoft’s Exam Readiness Zone has a six-part PL-400 series with Julian Sharp, one episode per skill area, packed with tips, tricks and strategies. I’ve linked each episode under its matching section below, so you can watch the one that goes with whatever you’re studying. Heads-up though: the series is a couple of years old (recorded before the March 2026 refresh), so the on-screen weightings are out of date, even if the six topic names still match. Honestly, I treat the videos as a nice overview rather than the final word. They may not be fully current, so for the real detail I rely on the documentation links under each skill area below.

Take the exam for a test drive first. Before you book it, spend a few minutes in the exam sandbox. You get the exact look, feel and question types you’ll meet on the day, so the interface holds no surprises. Especially worth it if this is your first Microsoft exam.

Reading alone won’t cut it

You do not pass this one by reading theory. You have to get into the system, write the code, register the plug-in and watch it fire. A good share of PL-400 questions are really “which method, which stage, in which order” questions, and you only get those right once you have done it with your own hands.

So set yourself up properly first:

• Grab a free Power Platform Developer Plan. It gives you a personal Dataverse environment to build in and break.
• Install the tooling: Visual Studio / VS Code, the Power Platform CLI (pac), and the Plug-in Registration Tool.
• Then work the labs in the learning paths above. Write a plug-in, build a PCF control, wire up a custom connector, call the Web API.

The short version, for those of us with some mileage

I have been doing Dynamics and Power Platform certifications for more than ten years, and the most effective move is always the same: open the official Skills measured and read up only on what you actually need. I go deep on the added and changed skills and just skim the ones that have not moved since last time. Lean, clean and quick.

Below you find the skills measured for PL-400 and the docs I found most useful. I have done the digging so you can prep in a lean, clean and quick fashion.

Tip: When you read the docs on learn.microsoft.com, pay real attention to the purple Note and the baby-blue Important boxes. What lives in those callouts has a high habit of turning up in the exam questions.

Skills measured & the docs I’d actually read

1. Create a technical design (10–15%)

Design the technical architecture: break the architecture down into solution components, set the authentication and authorization strategy, decide out-of-the-box versus custom, and decide where business logic belongs (cloud, client-side, business rules, plug-ins, Power Automate). Pick standard, virtual, or elastic tables versus connectors. Weigh the impact of DLP policies, security roles, teams, business units and row sharing.

Design the solution components: reusable canvas components, code components (PCF) and client scripting; custom connectors; Dataverse code components (Power Fx functions, plug-ins, custom APIs); Power Automate cloud flows; inbound and outbound integrations with Dataverse and Azure.

Read up on:

• Types of tables: standard, activity, virtual, elastic
• Elastic tables for developers
• Create and edit virtual tables
• Create virtual tables using connectors, the tables-versus-connectors call
• Common Data Model, the standard schema behind Dataverse
• Security roles and privileges for Dataverse
• Column-level security, the column-versus-row half of the access story
• Data policies (DLP)

Watch: Exam Readiness Zone — Create a technical design (Part 1 of 6)

2. Build Power Platform solutions (10–15%)

Configure and troubleshoot: operational security issues, Dataverse security roles for code components with least privilege, and managing your dev environments.

Implement ALM: solution dependencies, environment variables, solution layers, Power Platform Pipelines, and CI/CD automations with Power Platform Build Tools.

Read up on:

• ALM for developers in Power Platform
• Create patches to simplify solution updates
• Microsoft Power Platform CLI

Watch: Exam Readiness Zone — Build Power Platform Solutions (Part 2 of 6)

3. Implement Power Apps improvements (10–15%)

Advanced canvas apps: complex Power Fx formulas, reusable component libraries, and calling Power Automate cloud flows from a canvas app.

Optimize and troubleshoot: debug canvas and model-driven apps with Monitor and the browser tools, and optimize performance (pre-loading data, query delegation, forms and views).

Read up on:

• Microsoft Power Fx overview
• Develop offline-capable canvas apps
• Live monitor, the debugging tool for both canvas and model-driven apps

Watch: Exam Readiness Zone — Implement Power Apps improvements (Part 3 of 6)

4. Extend the user experience (10–15%)

Client scripting in model-driven apps: write JavaScript against the Client API object model, choose the event-handler registration approach, call the Dataverse Web API from client script, configure commands and buttons with Power Fx and JavaScript, and navigate to custom pages through the Client API.

Power Apps component framework (PCF): the lifecycle events, the component manifest, component interfaces, packaging and deploying, and using the Device, Utility and Web API features in component logic.

Read up on:

• Create and build a code component (PCF)
• Power Apps component framework for canvas apps
• Implement components using TypeScript
• Use the Microsoft Dataverse Web API for the client-side calls
• Add custom JavaScript to Power Pages
• Work with lists in Power Pages

Watch: Exam Readiness Zone — Extend the user experience (Part 4 of 6)

5. Extend the platform (30–35%) — the big one

This is where the exam is won or lost. Give it the most time.

Create a Dataverse plug-in: the event-execution pipeline stages, the execution context, business logic, Pre and Post Images, operations through the Organization service, plug-in performance, registering with the Plug-in Registration Tool, custom API messages, and Dataverse business events.

Create custom connectors: an OpenAPI definition for an existing REST API, authentication, policy templates to change runtime behavior, importing from OpenAPI / Azure / GitHub, a connector for an Azure service, an Azure Function behind a connector, and transforming data in connector code.

Use the platform APIs: the Dataverse Web API and the Organization service, API-limit retry policies, tuning for performance, concurrency, transactions and bulk operations, OAuth, and running workloads or long-running, scheduled and event-driven work in Azure Functions, including managed identities.

Configure Power Automate cloud flows: Dataverse actions and triggers, complex expressions, sensitive input and output parameters, Azure Key Vault, error handling and flow control, trigger filters and retry policies, reusable child flows, and Microsoft Entra ID service principals.

Read up on:

• Write a plug-in (Microsoft Dataverse)
• Event framework, the execution pipeline
• Handle exceptions in a plug-in
• Debug plug-ins, tracing and the plug-in profiler
• Integrate with Dataverse and Azure, the learning path that covers building and deploying Azure Functions
• Custom connectors overview
• Create a custom connector from scratch
• Policy templates for custom connectors, the runtime-behaviour bit the skills measured calls out by name
• Use the Microsoft Dataverse Web API
• Execute multiple requests for bulk operations and performance
• MSAL overview for the OAuth and token side
• Use expressions in conditions in Power Automate

Watch: Exam Readiness Zone — Extend the platform (Part 5 of 6)

6. Develop integrations (10–15%)

Publish and consume Dataverse events: publish with IServiceEndpointNotificationService, publish through the Plug-in Registration Tool, register service endpoints (webhooks, Azure Service Bus, Azure Event Hub), and weigh the options for listening to Dataverse events.

Data synchronization with Dataverse: change tracking, alternate keys, and the UpsertRequest message.

Read up on:

• Event framework, the execution pipeline
• Use webhooks to create external handlers for server events
• Azure Service Bus integration, the queue, topic and Event Hubs contracts
• Enable change tracking to control data synchronization
• Work with alternate keys
• Use the Microsoft Dataverse Web API for alternate keys and upsert
• Export Customer Insights data to Power Apps as a worked example of an inbound integration

Watch: Exam Readiness Zone — Develop integrations (Part 6 of 6)

My exam-day shortlist

• Know the plug-in pipeline cold: the stages (pre-validation, pre-operation, post-operation), sync versus async, Pre and Post Images, and when to reach for the Organization service. This is the highest-value study you can do.
• Know the failure path too: throw InvalidPluginExecutionException when you want to cancel and show the user a real message, cancel in pre-validation so you avoid a rollback, write to ITracingService for the trace log, and remember that an async plug-in cannot cancel anything, its errors land in System Jobs.
• Be ready for “where should this logic live?” Plug-in, Power Automate, or business rule, and why you picked it. The security twin of that question is just as common: column-level security controls who sees the field, security roles and row sharing control who sees the row.
• The PCF lifecycle: init, updateView, getOutputs, destroy, and what the manifest declares.
• Web API versus Organization service: REST/OData versus the SDK for .NET, and when each one fits.
• Custom connectors: the OpenAPI definition, the auth types, and policy templates.
• ALM: solutions, layers, environment variables, patches, and Build Tools / Pipelines for CI/CD.
• Getting events out of Dataverse: webhook versus Azure Service Bus versus Event Hub. Webhooks run synchronous or asynchronous and scale only as far as your own endpoint does, Service Bus is asynchronous only but queues properly when the consumer is down or the volume is high. Know which one survives an outage.
• Where does the code run, plug-in or Azure Function? Plug-in for transactional logic inside the pipeline, Function for long-running, scheduled or event-driven work. Know the two-minute plug-in timeout as the signal to move out, and reach for a managed identity rather than a stored secret.
• Syncing without duplicates: alternate keys to match the external system’s ID, UpsertRequest to create-or-update in one call, and change tracking to pull only the delta. Expect a “sync 200,000 rows nightly” scenario.
• When it breaks, which tool? Live monitor for canvas and model-driven apps, the plug-in trace log and the profiler for server-side, browser dev tools for client script, and run history for a cloud flow. Easy marks if you have the names straight.

Good luck taking the certification

That is my lean, clean and quick prep guide for PL-400. Drop a comment if you spot something missing that would help others pass, and I will keep it updated as the skills measured change.

Official resources: PL-400 study guide · Power Platform Developer Associate certification