PL-400 status as of July 16, 2026
Microsoft Certified: Power Platform Developer Associate is an active role-based certification earned through PL-400. The current Power Platform Developer Associate page offers scheduling, a Practice Assessment, exam prep resources, and renewal. It does not display a retirement warning or retirement date as of this review.
That status should be stated carefully. “No retirement notice currently shown” is not a promise that PL-400 will never retire. Microsoft can update or retire credentials, so candidates should check the live certification page before paying or scheduling. Do not copy PL-200's August 2026 retirement into PL-400 metadata; they are separate credentials with different current statuses.
PL-400 targets developers who design, develop, test, and troubleshoot Power Platform solution components. Microsoft's candidate profile expects experience with Power Platform services, JavaScript, JSON, TypeScript, C#, HTML, RESTful web APIs, Visual Studio, Visual Studio Code, and Microsoft Azure. It also names complex Power Fx, Power Automate workflow expressions, AI in solution logic, authentication, security, ALM, Power Platform CLI, and AI tools including agents.
Official exam metadata
| Item | Current official information |
|---|---|
| Credential | Microsoft Certified: Power Platform Developer Associate |
| Required exam | PL-400 |
| Current status | Active; no retirement warning or date shown on the current certification page |
| Assessment time | 100 minutes |
| Passing score | 700 |
| Fixed question count | Not published for PL-400 |
| Price | Based on the country or region where the exam is proctored |
| Delivery | Proctored and scheduled through Pearson VUE |
| Languages | English, German, Spanish, French, Japanese, Portuguese (Brazil), and Chinese (Simplified) |
| Current skills version | March 19, 2026 |
| Renewal frequency | 12 months |
| Formal prerequisite exam | None listed on the current certification page |
The certification page gives candidates 100 minutes to complete the assessment. Microsoft's exam duration guidance distinguishes assessment time from seat time for instructions, the candidate agreement, questions, and optional comments. It generally lists 120 minutes of seat time for associate role-based exams without labs, but candidates should use the appointment duration shown at registration because lab availability can change the allocation.
Microsoft does not publish a fixed PL-400 question count. Its general exam guidance says most Microsoft certification exams typically contain 40–60 questions, but the number can vary. That general range is not a guaranteed PL-400 form length. Microsoft also says it does not identify exam-specific formats or question types in advance; use the official sandbox to learn the interface without assuming that a particular form will contain a set number of case studies, code-completion items, or labs.
Price depends on the proctoring country or region
The certification page does not present one durable worldwide fee. It says pricing is based on the country or region where the exam is proctored. A US-dollar figure should not be treated as a global PL-400 price or converted into unofficial regional amounts.
For an accurate total:
- Sign in with the personal Microsoft account that will hold the exam record.
- Select Schedule exam on the certification page.
- Choose the actual proctoring country or region and delivery method.
- Confirm the current price, taxes, and any verified offer before paying.
- Recheck the live amount for a retake because another fee may apply.
Microsoft strongly recommends using a personal Microsoft account rather than only a work or school account. It warns that exam records associated with an organizational account can become unrecoverable if the candidate leaves that organization.
Skills measured as of March 19, 2026
The official PL-400 study guide publishes six domains:
| Domain | Weight |
|---|---|
| Create a technical design | 10–15% |
| Build Power Platform solutions | 10–15% |
| Implement Power Apps improvements | 10–15% |
| Extend the user experience | 10–15% |
| Extend the platform | 30–35% |
| Develop integrations | 10–15% |
Extend the platform is the largest published domain, but percentages do not prove an exact question count. Multiplying each weight by a guessed 50-question form creates false precision.
Create a technical design — 10–15%
Be able to analyze architecture, choose authentication and authorization strategies, determine whether requirements fit out-of-the-box features, and decide where business logic belongs: cloud computing, client-side processing, business rules, plug-ins, or Power Automate.
The outline also covers standard, virtual, and elastic tables; connectors; DLP policies; security roles; teams; business units; and row sharing. Component design includes reusable Power Apps components, PCF code components, client scripting, custom connectors, Power Fx functions, plug-ins, custom APIs, cloud flows, and Dataverse/Azure integrations.
Build Power Platform solutions — 10–15%
Review troubleshooting operational security, least-privilege roles for code components, and development environments. For ALM, study solution dependencies, environment variables, solution layers, Power Platform Pipelines, and CI/CD with Power Platform Build Tools.
Avoid reducing Pipelines to “for citizen developers” and Build Tools to “for professionals.” Compare their actual capabilities and choose from the requirement: in-product deployment experience, source control, automation, dependency handling, environment strategy, governance, and extension needs.
Implement Power Apps improvements — 10–15%
Practice complex Power Fx formulas, reusable component libraries, and calling cloud flows from canvas apps. For troubleshooting and performance, use Monitor and browser debugging tools, understand data preloading and delegation, and optimize model-driven forms and views.
This domain rewards hands-on diagnosis. Build a deliberately slow or delegation-limited app, observe it, explain the bottleneck, and make a measurable correction.
Extend the user experience — 10–15%
For model-driven apps, build JavaScript against the Client API object model, choose an event-registration approach, call the Dataverse Web API, configure commands with Power Fx or JavaScript, and navigate to custom pages through the Client API.
For PCF, know lifecycle events, the component manifest, interfaces, packaging, deployment, consumption, and use of Device, Utility, and Web API features. Implementing one small code component from initialization through cleanup is more valuable than memorizing method names without context.
Extend the platform — 30–35%
This is the heaviest domain. Dataverse plug-in objectives include pipeline stages, execution context, business logic, pre and post images, Organization service operations, performance, custom API messages, registration with the Plug-in Registration Tool, and business events.
Custom-connector objectives include OpenAPI definitions, authentication, policy templates, importing existing definitions, Azure services, Azure Functions, and code that transforms data. Platform API coverage includes the Dataverse Web API, Organization service, retry policies, performance, concurrency, transactions, bulk operations, and OAuth.
Also review long-running, scheduled, and event-driven Azure Functions plus managed-identity authentication. The Power Automate portion covers Dataverse triggers and actions, complex expressions, sensitive inputs and outputs, Azure Key Vault, error handling, trigger filters, retry policies, child flows, and Microsoft Entra ID service principals.
Develop integrations — 10–15%
Study publishing and consuming Dataverse events, including IServiceEndpointNotificationService and service endpoints for webhooks, Azure Service Bus, and Azure Event Hub. For data synchronization, cover change tracking, alternate keys, and UpsertRequest.
Practice designing for retries and idempotency. An integration answer is not complete merely because it moves data once; it must also handle duplication, updates, failures, and replay safely.
What the March 2026 update actually says
The current study guide labels the objectives Skills measured as of March 19, 2026. Its published change log marks the audience profile as a minor change. It does not identify multiple top-level weight changes or say that Pipelines, elastic tables, Copilot Studio, AI Builder, or custom prompts were all newly added on that date.
The audience profile does explicitly include AI as part of solution logic and AI tools, including agents, in development and troubleshooting. That supports studying AI-assisted Power Platform development at a role level. It does not justify promising specific Copilot Studio, AI Builder, or custom-prompt questions when those product names do not appear in the skills bullets. Use the exact current bullets as the exam-content boundary.
Microsoft notes that localized versions generally update after the English exam. Candidates using another language should read the update notice on the live certification page and confirm the version relevant to their appointment.
A six-week developer study plan
This schedule is editorial guidance, not a Microsoft prerequisite or pass guarantee. Adjust it to your starting skill and available lab environment.
Week 1: architecture and ALM
Map every study-guide bullet into a checklist. Design a small solution, identify where each business rule should run, and document authentication, authorization, DLP, table, and integration choices. Package the solution with environment variables and review dependencies and layers.
Week 2: Power Apps improvements
Build a canvas app with complex but readable Power Fx and reusable components. Call a cloud flow, test delegation behavior, and use Monitor to diagnose performance. Review optimization of model-driven forms and views.
Week 3: client scripting and PCF
Write model-driven app event handlers, call the Web API, configure a command, and navigate to a custom page. Build, package, deploy, and clean up a small PCF component while explaining each lifecycle event and manifest choice.
Weeks 4 and 5: extend the platform
Develop and register a Dataverse plug-in using execution context, images, tracing, and Organization service operations. Implement a custom API and a small custom connector with authentication. Exercise retry behavior, bulk operations, an Azure Function, a Dataverse-triggered flow, child-flow reuse, and secret handling.
Week 6: integrations and repair
Publish a Dataverse event to an appropriate endpoint and design a synchronization path using change tracking, alternate keys, and UpsertRequest. Take Microsoft's free Practice Assessment, then map every miss to an official objective and reproduce weak scenarios in a development environment.
Keep local practice inventory separate
Use local practice as a diagnostic loop:
- Attempt a short mixed set without notes.
- Map each miss to a current study-guide bullet.
- Verify the feature in Microsoft Learn and, where practical, in a developer environment.
- Explain why the rejected options fail the stated requirement.
- Revisit the same skill in a different scenario.
Microsoft's Practice Assessment is also a preparation resource, not a copy of the exam and not proof of exam length. Avoid providers that claim to offer recalled or live exam questions.
Exam experience and retakes
Microsoft permits access to learn.microsoft.com during associate exams, with exclusions such as Q&A, Practice Assessments, and the candidate profile. The exam timer continues while Learn is open, so use it for targeted verification rather than searching every question.
The current retake policy states:
- Wait 24 hours after the first failed attempt.
- Wait 14 days between subsequent attempts, up to five attempts.
- Do not take the same exam more than five times within 12 months from the first attempt.
- A retake fee may apply.
- A passed exam cannot be retaken unless the certification has expired.
Microsoft provides a narrow waiting-period waiver process for documented connectivity or equipment failures associated with a Pearson VUE case. Check the policy page rather than relying on informal discount or waiver claims.
Certification validity and renewal
Microsoft's credential expiration policy says role-based associate, expert, and specialty certifications are valid for one year after all requirements are completed. PL-400's certification page lists a 12-month renewal frequency and currently offers renewal.
The normal Microsoft renewal process is free, online, unproctored, and open book. The six-month eligibility window is before the certification expires. Candidates may retry the renewal assessment as needed within that window; passing extends the certification one year from its existing expiration date.
There is no six-month grace period after expiration. Once the certification expires, Microsoft's expiration policy says it cannot be renewed; the candidate must re-earn it by meeting the current exam requirements. Check the Learn profile for the exact eligibility date and renewal button.
Official-source checklist
Use these pages as the final authority:
- Power Platform Developer Associate — active status, candidate profile, assessment time, languages, price notice, scheduling, and renewal.
- PL-400 study guide — six domains, weights, objectives, and change log.
- Exam duration and experience — changing question counts, seat time, sandbox, breaks, and in-exam Learn access.
- Retake policy — waiting periods, attempt limit, fees, and waivers.
- Credential expiration policy and renewal process — one-year validity and the six-month pre-expiration renewal window.
Bottom line
As of July 16, 2026, PL-400 remains active and has no retirement warning on its current Microsoft certification page. The verified public facts are 100 minutes to complete the assessment, a passing score of 700, six weighted domains, regional pricing, and a 12-month renewable certification.
Do not turn Microsoft's general 40–60-question guidance into a fixed PL-400 total, invent exam-specific formats, or blend local practice inventory into formal metadata. Build against the March 19, 2026 study guide, verify live scheduling details, and renew during the six months before expiration.

