Study guide
0.2 Audience Profile & Required Developer Skills
Microsoft Power Platform Developer Associate PL-400
Track your progress as you read
Finished sections get a check mark.
1 Introduction, Exam Overview & Developer Toolchain
0.1 PL-400 Exam Facts 0.2 Audience Profile & Required Developer Skills 0.3 The Power Platform Developer Toolchain 0.4 Extension-Point Map & AI in the Developer Workflow
2 Create a Technical Design
1.1 Analyzing Technical Architecture and Choosing Out-of-the-Box vs. Custom Solutions 1.2 Designing Authentication, Authorization, and Security Architecture 1.3 Deciding Where Business Logic Runs and Choosing the Right Table Type 1.4 Designing Reusable Power Apps Components and Custom Connectors 1.5 Designing Dataverse Code Components, Automations, and Integrations
3 Build Power Platform Solutions
2.1 Managing Power Platform Environments for Development 2.2 Dataverse Security Roles for Code Components, Least Privilege & Troubleshooting Operational Security 2.3 Solutions, Managing Dependencies & Solution Layers 2.4 Environment Variables & Connection References 2.5 Power Platform Pipelines & CI/CD with Power Platform Build Tools
4 Implement Power Apps Improvements
3.1 Complex Power Fx Formulas and Functions 3.2 Building Reusable Canvas Component Libraries 3.3 Invoking Power Automate Cloud Flows from a Canvas App 3.4 Troubleshooting Canvas and Model-Driven Apps with Monitor and Browser Debugging Tools 3.5 Optimizing Canvas and Model-Driven App Performance
5 Extend the User Experience
4.1 The Client API Object Model & JavaScript Form Scripting 4.2 Event Handler Registration & Navigation to Custom Pages via the Client API 4.3 Client Scripting Against the Dataverse Web API; Command Bar & Buttons with Power Fx and JavaScript 4.4 PCF Fundamentals: The Component Manifest & Lifecycle Events 4.5 Implementing PCF Component Interfaces; Device, Utility & Web API Features 4.6 Packaging, Deploying & Consuming a PCF Component
6 Extend the Platform: Dataverse Plug-ins & Custom APIs
5.1 Plug-in Fundamentals & the Event Execution Pipeline Stages 5.2 Execution Context & Implementing Business Logic in Plug-ins 5.3 Pre/Post Images & Organization Service Operations in Plug-ins 5.4 Registering Plug-ins with the Plug-in Registration Tool & Optimizing Plug-in Performance 5.5 Custom API Messages & Plug-ins That Implement a Custom API 5.6 Configuring Dataverse Business Events
7 Extend the Platform: Custom Connectors
6.1 Open API Definitions: Building and Extending a Custom Connector 6.2 Authentication and Policy Templates for Custom Connectors 6.3 Importing Definitions and Creating Connectors for Azure Services 6.4 Azure Functions in Custom Connectors and Data Transformation
8 Extend the Platform: Platform APIs & Azure Functions
7.1 Dataverse Web API Operations & OAuth Authentication 7.2 Organization Service Operations, Concurrency, Transactions & Bulk Operations 7.3 Service Protection API Limits & Retry Policies 7.4 Azure Functions for Long-Running, Scheduled & Event-Driven Workloads 7.5 Authenticating to Power Platform with Managed Identities
9 Extend the Platform: Power Automate Cloud Flows
8.1 Dataverse connector triggers/actions, trigger filters & retry policies 8.2 Complex expressions & flow control with error handling 8.3 Sensitive input/output parameters & Azure Key Vault 8.4 Reusable child flows & Microsoft Entra ID service principals
10 Develop Integrations
9.1 Publishing Dataverse Events: IServiceEndpointNotificationService & the Plug-in Registration Tool 9.2 Registering Service Endpoints: Webhooks, Azure Service Bus & Event Hub 9.3 Data Synchronization with Change Tracking & Alternate Keys 9.4 Upsert-Based Synchronization with the UpsertRequest Message
11 Exam Readiness & Practice
10.1 Cross-Domain "Where Do I Implement This?" Decision Framework 10.2 Exam-Day Strategy, PL-400 Item Styles & Study Plan
0.2 Audience Profile & Required Developer Skills
Key Takeaways Explain This Topic AI
PL-400 certifies pro-code developers, distinct from the low-code PL-200 Functional Consultant track
Candidates need at least one of JavaScript, TypeScript, or C#, plus JSON, HTML, RESTful API concepts, and Visual Studio/VS Code fluency
Azure familiarity is expected because Functions, Key Vault, Service Bus, and Entra ID appear in later domains
PL-900 is not a technical prerequisite but is strongly recommended foundational knowledge
AI shows up as two audience-profile expectations - AI in solution logic, and AI tools/agents in the developer's own workflow - not as a separate domain
Last updated: July 2026
Audience Profile & Required Developer Skills
Quick Answer: PL-400 targets professional developers , not app makers or business analysts. Microsoft expects candidates to already be comfortable writing code in at least one language such as JavaScript, TypeScript, C#, or HTML/JSON , understand RESTful web service concepts, and be able to work in Visual Studio or VS Code . Familiarity with Azure and with foundational Power Platform concepts (ideally at the PL-900 level) rounds out the expected background.
Who Microsoft Built This Exam For
The Microsoft Certified: Power Platform Developer Associate credential is explicitly a pro-code certification, sitting apart from the low-code/no-code track represented by PL-900 (Fundamentals) and PL-200 (Functional Consultant). According to the official audience profile, a Power Platform Developer:
Designs, develops, secures, and troubleshoots Power Platform solutions.
Acts as a subject matter expert who implements components including Power Apps custom pages and components, Dataverse plug-ins and custom APIs, custom connectors, cloud flow logic, and Azure-based integrations.
Collaborates with functional consultants, architects, and administrators, but is personally responsible for the code-level implementation those roles hand off.
Uses AI as part of the solution itself (for example, AI Builder models or Copilot-driven experiences embedded in an app) and uses AI tools, including AI agents, to accelerate their own development and troubleshooting workflow.
If your background is entirely in configuring Power Apps through the maker portal with formulas and no custom code, PL-400 will feel like a different exam from PL-200 - because it is. Roughly a third of the blueprint (Extend the Platform) assumes you can read and reason about C# plug-in code, Web API JSON payloads, and Azure Function signatures without translation.
Required Programming & Web Skills
Microsoft's official prerequisites list is intentionally broad about which language you know, but firm about the fact that you need at least one of these, plus general web literacy:
Skill Area What You Need
Object-oriented language JavaScript, TypeScript, or C# - used for plug-ins, PCF components, and client scripting
- Data formats JSON, and comfort reading/writing structured payloads
- Markup HTML, for custom pages and canvas component styling
Web services Understanding of RESTful APIs - how the Dataverse Web API and custom connectors communicate over HTTP
Tooling Visual Studio and/or Visual Studio Code, including debugging workflows
Cloud platform Working familiarity with Microsoft Azure - Functions, Key Vault, Service Bus, and Entra ID all appear later in the "Extend the Platform" and "Develop Integrations" domains
You do not need expert-level mastery of all of these simultaneously - most working developers will have deep strength in one or two areas (say, C# and Azure) and working proficiency in the others (JavaScript for client scripting, TypeScript for PCF). The exam blueprint reflects that mixed-language reality: plug-ins are typically C#, client scripting and PCF components are typically JavaScript/TypeScript, and Power Fx sits alongside both inside canvas apps and formula-driven components.
Is PL-900 a Real Prerequisite?
Microsoft does not enforce PL-900 as a technical gate - there's no system that blocks you from registering for PL-400 without it. But it is strongly recommended as a knowledge foundation, and for good reason: PL-400's "Create a Technical Design" and "Build Power Platform Solutions" domains assume you already know what a Dataverse table, environment, solution, and security role are at a conceptual level. PL-900 covers that vocabulary; PL-400 builds pro-code skills on top of it. If you're coming from a pure software-engineering background with no prior Power Platform exposure, spending a few hours with PL-900-level material before diving into plug-in registration and ALM pipelines will save you far more time than it costs.
Where AI Fits the Skill Profile
Two AI-related expectations appear explicitly in the current audience profile, and neither is a standalone exam domain - they're described as characteristics of how a modern Power Platform developer works:
AI as part of solution logic - knowing when and how to embed AI Builder models, Copilot experiences, or agent-driven behavior into the apps and flows you build.
AI tools, including agents, used to improve development and troubleshooting - using AI-assisted coding tools (such as GitHub Copilot inside Visual Studio Code) and AI-driven diagnostic assistance as part of your own developer workflow, not just as a feature you ship to end users.
Don't expect a dedicated "Copilot" chapter or domain on the exam - these AI skills are woven into how questions across all six domains are framed, not tested as an isolated topic.
Where PL-400 Sits in the Certification Path
Microsoft's Power Platform role-based certifications form a loose ladder rather than a strict prerequisite chain: PL-900 (Fundamentals) validates conceptual, no-code understanding for any business user; PL-200 (Functional Consultant) validates configuration-level skill - building apps, flows, and Dataverse schema through low-code tools without writing custom code; PL-400 (Developer) validates pro-code extensibility on top of that same platform; and PL-600 (Solution Architect) validates cross-workload design leadership that typically assumes developer- or consultant-level depth already exists. A common, realistic path into PL-400 is PL-900 for vocabulary, hands-on Power Platform project experience for context, and then direct PL-400 study focused on the pro-code gaps - you do not need to collect PL-200 first unless your job also requires configuration-consultant skills.