Exam Prep
Microsoft Power Platform · AB-400

Extending Microsoft Power Platform Solutions with Code and AI

Validates the skills to design, develop, test, and troubleshoot Microsoft Power Platform solutions using code and AI — covers technical architecture, application lifecycle management, user experience extensions, Dataverse plug-ins and code components, and integrations.

Start Preparing

Free study references: Pages from Microsoft Power Platform for every objective

Should I Take the AB-400?

You should work towards AB-400 if you’re aiming for one of these careers:

  • Power Platform developer — the role the exam is built around: writing plug-ins, code components and custom APIs that extend Power Apps and Dataverse beyond their low-code tools.
  • Dynamics 365 developer — customizing and extending Dynamics 365 apps, which run on the same Dataverse and Power Platform extensibility model the exam covers.
  • Power Platform solution architect (early-career path) — designing the technical architecture of Power Platform solutions, a skill area the exam tests directly before most architects move into that title.
  • Integration developer for Power Platform — building custom connectors, Dataverse event publishing and API integrations that connect Power Platform solutions to Azure and other systems.

AB-400 is the current exam for Microsoft Certified: Power Platform Developer Associate, the same credential formerly earned through PL-400. Microsoft is retiring the PL-400 course and exam as part of this transition, so a developer's only route to a new Power Platform Developer Associate certification is now through AB-400.

Is the AB-400 Worthwhile?

Here’s what we’d tell a friend:

  • It replaced an existing, well-recognized credential rather than creating a new one. AB-400 earns the same title PL-400 did, Microsoft Certified: Power Platform Developer Associate, so the certification already has a track record in hiring rather than being an unproven new line.
  • Pay figures for Power Platform developers vary widely by source, location and seniority — be wary of any single number. In October 2026, ZipRecruiter's national figure for Microsoft Power Platform Developer was $129,348 a year, while its separate Power Platform Developer listing showed a median of $123,611; Glassdoor's New York and Chicago averages ran well above that, at $186,794 and $177,816 respectively. These differences come from location, employer and years of experience, not from the certification itself; it alone won't set your salary, your role and experience will. Source: Salary: Microsoft Power Platform Developer (Oct, 2026) US, Power Platform Developer Salary: Hourly Rate October 2026, Salary: Power Platform Developer in New York, NY 2026, Salary: Power Platform Developer in Chicago, IL 2026
  • It covers a broader, more current exam objective set than its predecessor. AB-400 reorganizes the old developer exam into four domains and adds generative AI, agentic solutions, code apps, MCP and Python to the skills measured, so studying for it means learning tools that are newer to the role than those PL-400 tested.
  • The underlying Power Platform and Dynamics 365 market remains active. Industry recruiters describe demand for Dynamics 365 and Power Platform professionals as continuing to outpace supply heading into 2026, particularly for people who combine delivery skills with governance and technical depth. Source: Dynamics 365 and Power Platform Compensation Is Holding Firm Into 2026. Here's Why... - Nigel Frank
  • This is not an entry-level credential, so it carries more weight with employers who need working developers. It is an associate-level developer exam that assumes you have already registered a plug-in and debugged a code component, not just studied the concepts, which is a higher bar than many associate-level exams set. Source: Free AB-400 Study Guide and Learning Resources (2026)

How Long Will I Have to Spend Studying for the AB-400?

The honest answer is that it depends on how much you already know. Microsoft's own description of the candidate says you design, develop, test, and troubleshoot solution components using the extension points of Power Platform and generative AI, and that you have development experience with Power Platform services, JavaScript, JSON, TypeScript, Power Fx, C#, Python, HTML, YAML, RESTful web APIs, Microsoft Azure, Microsoft Foundry, and Microsoft Copilot Studio. If that’s your background, you’ve got a good start.

In our plan, you pick the areas of AB-400 that matter to you — for the exam and for your job — and build a study plan from our domain reviews. Then you take an initial exam, backed by Microsoft Power Platform’s own documentation, to see where you need to focus to meet your study plan’s goals (our exam review will show you that).

In our store, you can buy a single exam or, if you intend to stick with us, our standard package — which includes, for example, custom drills for the areas our review showed that you need to strengthen (both domain knowledge and exam-taking skills). Repeat with fresh exams, step up to a challenge exam, take advantage of Mentor, and walk into the real exam with your own two-page cheat sheet. See how it works.

How Hard Is the AB-400 Exam?

Another honest answer: since Microsoft Power Platform doesn’t publish pass rates, no one knows (including us). What Microsoft Power Platform does publish: a score of 700 or greater is required to pass. The skills it measures, and how much each area weighs, are listed below.

We can tell you that we update our exams monthly, so they always reflect the current state of both the certification and the documentation that supports it. That means our exams follow the certification’s current topic weights, and our domain reviews and explanations are always up to date.

Start Preparing

We can’t tell you how well you know the content — you need to take one of our real exams for that. But our full exams also tell you how you miss: what question answering habits are tripping you up (and we do it across six kinds of ‘bad habits’). We have over 100 answers written that not only test your knowledge but catch those specific bad habits.

These 10 questions, for example, find which kind of ‘almost right’ answers catch you:

Sample exam coming soon.

Skills at a glance

Build Microsoft Power Platform solutions18%
  • Analyze the technical architecture to identify solution components and their implementation approach
  • Design authentication and authorization for solution components
  • Determine whether requirements can be met with out-of-the-box functionality
  • Determine where to implement business logic including cloud services, client-side processing, business rules, plug-ins, and automation
  • Determine when to use standard tables, virtual tables, elastic tables, or connectors
  • 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
  • Determine when to use deterministic or non-deterministic methods to implement business logic
  • 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
  • Determine when to use Microsoft Foundry or Microsoft Copilot Studio to build agents
  • Design Power Apps reusable components including generative pages, code components (PCF), and client scripting
  • Design custom connectors and MCP servers for use with Microsoft Power Platform solutions
  • Design Dataverse code components, including plug-ins and custom APIs
  • Design automations, including Power Automate cloud flows and Copilot Studio workflows
  • Design inbound and outbound integrations using Dataverse and Microsoft Azure
  • Design custom interfaces by using Power Apps code apps
  • Design custom agents that integrate with Microsoft Power Platform
  • Design monitoring and alerting, including Azure Monitor Application Insights and Microsoft Power Platform monitor alerts
  • Manage solution dependencies
  • Create and use environment variables
  • Manage solution layers
  • Implement and extend Microsoft Power Platform Pipelines
  • Create Continuous Integration/Continuous Deployment (CI/CD) automations using Microsoft Power Platform Build Tools
Extend the user experience28%
  • Build code that targets the Client API object model
  • Determine an event handler registration approach
  • Create client scripting that targets the Dataverse Web API
  • Configure commands and buttons by using Power Fx and JavaScript
  • Implement navigation, dialogs, and notifications by using the Client API
  • Demonstrate the use of the different lifecycle events
  • Configure a code component manifest
  • Implement component interfaces
  • Package, deploy, and consume a component
  • Configure and use Device, Utility, and Web API features in component logic
  • Configure code apps to use Microsoft Power Platform connections
  • Configure code apps to use Dataverse tables
  • Perform table and metadata operations on Dataverse data
  • Perform Dataverse actions and functions
  • Configure code apps to use Power Automate cloud flows
  • Configure code apps to use agents built in Copilot Studio
  • Configure code apps to use environment variables
  • Configure Content Security Policy (CSP) settings
  • Implement monitoring by using Azure Application Insights
  • Package, deploy, and share code apps
  • Troubleshoot code apps by using Monitor and other browser-based debugging tools
  • Optimize code app performance and resource usage
Extend Microsoft Power Platform40%
  • Demonstrate the use of the different event execution pipeline stages
  • Develop a plug-in that uses the execution context
  • Develop a plug-in that implements business logic
  • Implement images to support plug-in logic
  • Perform operations in plug-ins by using the Organization service
  • Optimize plug-in performance
  • Configure a Dataverse custom API message
  • Register plug-in components by using the Plug-in Registration Tool
  • Develop a plug-in that implements a custom API
  • Configure Dataverse business events
  • Configure Microsoft Power Platform managed identity for plug-ins
  • Perform operations by using the Dataverse Web API
  • Perform operations by using the Organization service
  • Implement API limit retry policies
  • Optimize solution components for performance, concurrency, transactions, and bulk operations
  • Implement and troubleshoot authentication by using OAuth
  • Perform asynchronous logic by using background operations
  • Perform operations by using Dataverse SDKs for .NET and Python
  • Process long-running operations by using Azure Functions for Microsoft Power Platform solutions
  • Implement scheduled and event-driven triggers in Azure Functions for Microsoft Power Platform solutions
  • Authenticate to Microsoft Power Platform by using managed identities
  • Implement complex expressions in flow steps
  • Implement flow control actions including error handling
  • Configure trigger filter and retry policies
  • Develop reuseable logic by using child flows
  • Implement authentication for the Dataverse connector by using service principals
  • Integrate custom agents by using Microsoft Power Platform MCP servers
  • Connect custom agents to Copilot Studio agents
  • Integrate custom agents with Dataverse data by using Work IQ
  • Consume Copilot Studio agents by using the Copilot Studio client library
Develop integrations14%
  • Publish a Dataverse event by using the IServiceEndpointNotificationService
  • Publish a Dataverse event by using the Plug-in Registration Tool
  • Register service endpoints including webhooks, Azure Service Bus, and Azure Event Hub
  • Recommend options for listening to Dataverse events
  • Perform data synchronization by using change tracking
  • Develop code that uses alternate keys
  • Synchronize data by using the UpsertRequest message
  • Implement authentication for custom connectors
  • Configure policy templates to modify connector behavior at runtime
  • Import definitions from existing APIs including Open API definitions, Azure services, and GitHub
  • Create a custom connector for an Azure service
  • Develop an Azure Function to be used in a custom connector
  • Extend the Open API definition for a custom connector
  • Develop code for a custom connector to transform data

Domains

Build Microsoft Power Platform solutions18%
Design the technical architecture
  • Analyze the technical architecture to identify solution components and their implementation approach
  • Design authentication and authorization for solution components
  • Determine whether requirements can be met with out-of-the-box functionality
  • Determine where to implement business logic including cloud services, client-side processing, business rules, plug-ins, and automation
  • Determine when to use standard tables, virtual tables, elastic tables, or connectors
  • 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
  • Determine when to use deterministic or non-deterministic methods to implement business logic
  • 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
  • Determine when to use Microsoft Foundry or Microsoft Copilot Studio to build agents
Design solution components
  • Design Power Apps reusable components including generative pages, code components (PCF), and client scripting
  • Design custom connectors and MCP servers for use with Microsoft Power Platform solutions
  • Design Dataverse code components, including plug-ins and custom APIs
  • Design automations, including Power Automate cloud flows and Copilot Studio workflows
  • Design inbound and outbound integrations using Dataverse and Microsoft Azure
  • Design custom interfaces by using Power Apps code apps
  • Design custom agents that integrate with Microsoft Power Platform
  • Design monitoring and alerting, including Azure Monitor Application Insights and Microsoft Power Platform monitor alerts
Implement application lifecycle management (ALM)
  • Manage solution dependencies
  • Create and use environment variables
  • Manage solution layers
  • Implement and extend Microsoft Power Platform Pipelines
  • Create Continuous Integration/Continuous Deployment (CI/CD) automations using Microsoft Power Platform Build Tools
Extend the user experience28%
Apply business logic in model-driven apps by using client scripting
  • Build code that targets the Client API object model
  • Determine an event handler registration approach
  • Create client scripting that targets the Dataverse Web API
  • Configure commands and buttons by using Power Fx and JavaScript
  • Implement navigation, dialogs, and notifications by using the Client API
Create PCF code components
  • Demonstrate the use of the different lifecycle events
  • Configure a code component manifest
  • Implement component interfaces
  • Package, deploy, and consume a component
  • Configure and use Device, Utility, and Web API features in component logic
Build Power Apps code apps
  • Configure code apps to use Microsoft Power Platform connections
  • Configure code apps to use Dataverse tables
  • Perform table and metadata operations on Dataverse data
  • Perform Dataverse actions and functions
  • Configure code apps to use Power Automate cloud flows
  • Configure code apps to use agents built in Copilot Studio
  • Configure code apps to use environment variables
Deploy and manage Power Apps code apps
  • Configure Content Security Policy (CSP) settings
  • Implement monitoring by using Azure Application Insights
  • Package, deploy, and share code apps
  • Troubleshoot code apps by using Monitor and other browser-based debugging tools
  • Optimize code app performance and resource usage
Extend Microsoft Power Platform40%
Create a Dataverse plug-in
  • Demonstrate the use of the different event execution pipeline stages
  • Develop a plug-in that uses the execution context
  • Develop a plug-in that implements business logic
  • Implement images to support plug-in logic
  • Perform operations in plug-ins by using the Organization service
  • Optimize plug-in performance
  • Configure a Dataverse custom API message
  • Register plug-in components by using the Plug-in Registration Tool
  • Develop a plug-in that implements a custom API
  • Configure Dataverse business events
  • Configure Microsoft Power Platform managed identity for plug-ins
Perform operations by using platform APIs
  • Perform operations by using the Dataverse Web API
  • Perform operations by using the Organization service
  • Implement API limit retry policies
  • Optimize solution components for performance, concurrency, transactions, and bulk operations
  • Implement and troubleshoot authentication by using OAuth
  • Perform asynchronous logic by using background operations
  • Perform operations by using Dataverse SDKs for .NET and Python
Process workloads by using Microsoft Azure Functions
  • Process long-running operations by using Azure Functions for Microsoft Power Platform solutions
  • Implement scheduled and event-driven triggers in Azure Functions for Microsoft Power Platform solutions
  • Authenticate to Microsoft Power Platform by using managed identities
Configure Power Automate cloud flows and Copilot Studio workflows
  • Implement complex expressions in flow steps
  • Implement flow control actions including error handling
  • Configure trigger filter and retry policies
  • Develop reuseable logic by using child flows
  • Implement authentication for the Dataverse connector by using service principals
Build Microsoft Foundry agents by using code that integrates with the Microsoft Power Platform
  • Integrate custom agents by using Microsoft Power Platform MCP servers
  • Connect custom agents to Copilot Studio agents
  • Integrate custom agents with Dataverse data by using Work IQ
  • Consume Copilot Studio agents by using the Copilot Studio client library
Develop integrations14%
Publish and consume Dataverse events
  • Publish a Dataverse event by using the IServiceEndpointNotificationService
  • Publish a Dataverse event by using the Plug-in Registration Tool
  • Register service endpoints including webhooks, Azure Service Bus, and Azure Event Hub
  • Recommend options for listening to Dataverse events
Implement synchronization for Dataverse data
  • Perform data synchronization by using change tracking
  • Develop code that uses alternate keys
  • Synchronize data by using the UpsertRequest message
Create custom connectors
  • Implement authentication for custom connectors
  • Configure policy templates to modify connector behavior at runtime
  • Import definitions from existing APIs including Open API definitions, Azure services, and GitHub
  • Create a custom connector for an Azure service
  • Develop an Azure Function to be used in a custom connector
  • Extend the Open API definition for a custom connector
  • Develop code for a custom connector to transform data