Almanac

Power Platform Developer Associate

PL-400intermediate16 uncoveredMicrosoft DataversePower Apps
115–20%Build Microsoft Power Platform solutions — 15–20% · 10 covered, 4 doc only, 8 uncovered225–30%Extend the user experience — 25–30% · 12 covered, 6 doc only, 4 uncovered335–40%Extend Microsoft Power Platform — 35–40% · 10 covered, 13 doc only, 7 uncovered410–15%Develop integrations — 10–15% · 4 covered, 3 doc only, 7 uncovered
module + docdoc onlynothingcircle size = share of the exam
About the non-Microsoft material below. Listed because it is useful, not because anyone paid for the placement — there are no affiliate links on this site and no one has been charged to appear. Anything marked Used it is a first-hand opinion; everything else is a listing, not a recommendation. Exam dumps and “real exam questions” sites are deliberately absent: using them breaches Microsoft's exam policy and can cost you the certification you already hold.

Where the marks are

Skills measured as of 16 October 2026 · re-read nightly
Build Microsoft Power Platform solutions22 objectives · 12h 33m
Extend the user experience22 objectives · 13h 35m
Extend Microsoft Power Platform30 objectives · 14h 53m
Develop integrations14 objectives · 4h 3m

Beyond Microsoft Learn — the whole certification

Free practice assessment for PL-400Free from MicrosoftPractice

Microsoft's own practice questions, written to the same objective list as the stages above. Unlimited attempts, and it tells you which domain you dropped marks in — the fastest way to find out which stage on this page you should actually be reading.

Microsoft · Free, needs a Microsoft Learn account

Microsoft's official classroom course for this exam, delivered by training partners. Worth it if your employer is paying and you want the labs and someone to ask; the content is the same material the modules above cover.

Microsoft (delivered by partners) · Priced by the delivery partner, not Microsoft
Stage 1

Build Microsoft Power Platform solutions

15–20% · 12h 33m

Design the technical architecture

Analyze the technical architecture to identify solution components and their implementation approach
No module
Design authentication and authorization for solution components
No module
Determine whether requirements can be met with out-of-the-box functionality
No module
Determine where to implement business logic including cloud services, client-side processing, business rules, plug-ins, and automation
Doc only
Determine when to use standard tables, virtual tables, elastic tables, or connectors
Doc only
Assess the impact of Microsoft Power Platform security features on solution components, including managed environments, data policies, security roles, teams, business units, and row sharing
Weak matchCovered
Determine when to use deterministic or non-deterministic methods to implement business logic
Weak matchDoc only
Determine when to use code apps, generative pages, Power Apps component frameworks (PCFs), web resources, interactive agents, and Model Context Protocol (MCP) app widgets to implement the user experience
Weak matchCovered
Determine when to use Microsoft Foundry or Microsoft Copilot Studio to build agents
No module

Design solution components

Design Power Apps reusable components including generative pages, code components (PCF), and client scripting
Weak matchCovered
Design custom connectors and MCP servers for use with Microsoft Power Platform solutions
Covered
Design Dataverse code components, including plug-ins and custom APIs
Weak matchCovered
Design automations, including Power Automate cloud flows and Copilot Studio workflows
Covered
Design inbound and outbound integrations using Dataverse and Microsoft Azure
Weak matchNo module
Design custom interfaces by using Power Apps code apps
Covered
Design custom agents that integrate with Microsoft Power Platform
No module
Design monitoring and alerting, including Azure Monitor Application Insights and Microsoft Power Platform monitor alerts
Weak matchCovered

Implement application lifecycle management (ALM)

Manage solution dependencies
Doc only
Create and use environment variables
Weak matchCovered
Manage solution layers
No module
Implement and extend Microsoft Power Platform Pipelines
Covered
Create Continuous Integration/Continuous Deployment (CI/CD) automations using Microsoft Power Platform Build Tools
No module
Stage 2

Extend the user experience

25–30% · 13h 35m

Apply business logic in model-driven apps by using client scripting

Build code that targets the Client API object model
No module
Determine an event handler registration approach
No module
Create client scripting that targets the Dataverse Web API
Covered
Configure commands and buttons by using Power Fx and JavaScript
Doc only
Implement navigation, dialogs, and notifications by using the Client API
Weak matchDoc only

Create PCF code components

Demonstrate the use of the different lifecycle events
No module
Configure a code component manifest
Weak matchCovered
Implement component interfaces
Doc only
Package, deploy, and consume a component
Weak matchCovered
Configure and use Device, Utility, and Web API features in component logic
No module

Build Power Apps code apps

Configure code apps to use Microsoft Power Platform connections
Covered
Configure code apps to use Dataverse tables
Weak matchCovered
Perform table and metadata operations on Dataverse data
Weak matchCovered
Configure code apps to use Power Automate cloud flows
Covered
Configure code apps to use agents built in Copilot Studio
Covered
Configure code apps to use environment variables
Weak matchCovered

Deploy and manage Power Apps code apps

Configure Content Security Policy (CSP) settings
Weak matchDoc only
Implement monitoring by using Azure Application Insights
Doc only
Package, deploy, and share code apps
Covered
Troubleshoot code apps by using Monitor and other browser-based debugging tools
Doc only
Optimize code app performance and resource usage
Weak matchCovered
Stage 3

Extend Microsoft Power Platform

35–40% · 14h 53m

Create a Dataverse plug-in

Demonstrate the use of the different event execution pipeline stages
No module
Develop a plug-in that uses the execution context
Doc only
Develop a plug-in that implements business logic
Doc only
Implement images to support plug-in logic
Doc only
Perform operations in plug-ins by using the Organization service
Doc only
Optimize plug-in performance
Doc only
Register plug-in components by using the Plug-in Registration Tool
Doc only
Develop a plug-in that implements a custom API
Doc only
Configure Microsoft Power Platform managed identity for plug-ins
Covered

Perform operations by using platform APIs

Perform operations by using the Dataverse Web API
Covered
Perform operations by using the Organization service
Doc only
Implement API limit retry policies
Weak matchDoc only
Optimize solution components for performance, concurrency, transactions, and bulk operations
No module
Implement and troubleshoot authentication by using OAuth
No module
Perform asynchronous logic by using background operations
Weak matchDoc only
Perform operations by using Dataverse SDKs for .NET and Python
Doc only

Process workloads by using Microsoft Azure Functions

Process long-running operations by using Azure Functions for Microsoft Power Platform solutions
No module
Implement scheduled and event-driven triggers in Azure Functions for Microsoft Power Platform solutions
Weak matchNo module
Authenticate to Microsoft Power Platform by using managed identities
Covered

Configure Power Automate cloud flows and Copilot Studio workflows

Implement flow control actions including error handling
Covered
Configure trigger filter and retry policies
Weak matchDoc only
Develop reuseable logic by using child flows
Weak matchNo module
Implement authentication for the Dataverse connector by using service principals
No module

Build Microsoft Foundry agents by using code that integrates with the Microsoft Power Platform

Integrate custom agents by using Microsoft Power Platform MCP servers
Covered
Connect custom agents to Copilot Studio agents
Weak matchCovered
Integrate custom agents with Dataverse data by using Work IQ
Covered
Consume Copilot Studio agents by using the Copilot Studio client library
Weak matchDoc only
Stage 4

Develop integrations

10–15% · 4h 3m

Publish and consume Dataverse events

Publish a Dataverse event by using the IServiceEndpointNotificationService
No module
Publish a Dataverse event by using the Plug-in Registration Tool
Weak matchDoc only
Register service endpoints including webhooks, Azure Service Bus, and Azure Event Hub
Doc only
Recommend options for listening to Dataverse events
No module

Implement synchronization for Dataverse data

Perform data synchronization by using change tracking
Doc only
Develop code that uses alternate keys
No module
Synchronize data by using the UpsertRequest message
No module

Create custom connectors

Implement authentication for custom connectors
Covered
Configure policy templates to modify connector behavior at runtime
No module
Import definitions from existing APIs including Open API definitions, Azure services, and GitHub
No module
Create a custom connector for an Azure service
No module
Develop an Azure Function to be used in a custom connector
Weak matchCovered
Extend the Open API definition for a custom connector
Weak matchCovered
Develop code for a custom connector to transform data
Weak matchCovered