Microsoft PL-200 Is Retired: Move to AB-410
PL-200, Microsoft Power Platform Functional Consultant, retired on August 31, 2026 together with the Power Platform Functional Consultant Associate certification. Microsoft replaced that path with the Intelligent Applications Builder Associate certification and AB-410, Building Intelligent Applications.
This is not a cosmetic exam-code change. PL-200 focused on requirements discovery, Dataverse, Power Apps, Power Automate, Power Pages, integrations, and delivering business solutions as a functional consultant. AB-410 keeps many of those implementation skills but explicitly adds AI-enabled solution design, Copilot features, prompts, AI models, agents, and natural-language development.
Professionals who already studied PL-200 therefore have a strong foundation. The practical transition is to keep the business-analysis, Dataverse, app, automation, and ALM skills that remain relevant while adding the AI-first Power Platform capabilities Microsoft now expects.
PL-200 was built around the functional consultant who could translate business requirements into Power Platform solutions. Candidates needed to understand how to gather requirements, work with stakeholders, configure Dataverse, build apps and flows, create Power Pages experiences, and support adoption.
Those responsibilities remain central to real Power Platform work. A business solution still needs a clear process, a sensible data model, usable interfaces, controlled automation, security, and a deployment lifecycle.
The shift is that Microsoft now expects those solutions to make practical use of AI when it adds value. That means the old functional-consultant foundation remains useful, but it is no longer the complete role.
Microsoft positioned Intelligent Applications Builder Associate as the replacement for Power Platform Functional Consultant Associate. AB-410 is the exam used to earn that credential.
The current blueprint is organized around three broad areas: creating a foundation for intelligent applications, creating intelligent applications, and building business application logic and automation. The largest share of the exam is business logic and automation, which shows that traditional Power Platform implementation skill is still important.
What changed is the expected context. Apps and automations now increasingly include prompts, AI models, agents, Copilot features, and AI-assisted solution design.
One of the strongest PL-200 skills was learning to understand the business process before building anything. That remains essential in AB-410.
A stakeholder may ask for an “AI app” when the actual problem is a slow approval process, poor data quality, or a missing user interface. The consultant or app builder should identify the real requirement before deciding whether the solution needs a canvas app, model-driven app, flow, agent, prompt, or ordinary business rule.
AI should be used because it solves uncertainty, language, summarization, extraction, or reasoning problems—not because every solution needs an agent.
AB-410 still expects candidates to build and configure Dataverse tables, columns, relationships, forms, views, security, and calculated or formula-driven behavior.
Good Dataverse design starts with business entities and ownership. Customers, cases, requests, assets, approvals, inspections, or other records should have clear relationships and lifecycle states.
Poor data design creates downstream problems in apps, flows, reports, and agents. If the data model is inconsistent, adding AI usually makes the inconsistency easier to access rather than fixing it.
Model-driven apps are still a strong fit for structured business processes built on Dataverse. Forms, views, dashboards, business rules, security roles, and process logic can be assembled around the data model without recreating every interface from scratch.
AB-410 adds AI-enabled creation and Copilot experiences to this workflow. Natural language can help generate pages or solution elements, but the resulting app still needs review for usability, access, data quality, and maintainability.
The key professional skill is knowing when a model-driven experience is appropriate and when another interface would serve users better.
Canvas apps provide greater control over layout and interaction. They are useful for mobile workflows, inspections, field processes, guided tasks, and other scenarios where the interface needs to be shaped closely around user behavior.
AB-410 expects app builders to consider accessibility, responsiveness, performance, components, formulas, variables, collections, error handling, and testing.
AI can accelerate some app creation, but it does not remove these design responsibilities. A generated screen still has to work on the target device, load efficiently, handle failure, and make sense to the people using it.
Cloud flows are still one of the most important Power Platform skills. Candidates should know how to choose triggers, use connectors, manage approvals, implement conditions and loops, handle errors, and troubleshoot runs.
The modern difference is that flows can now consume prompts and AI models or provide actions to agents. This creates richer automation, but it also raises the need for input validation, monitoring, and clear permission boundaries.
The current Power Platform architecture is easiest to understand when apps, data, automation, and agents are treated as one solution rather than separate products.
AB-410 explicitly expects candidates to build and consume prompts, add knowledge, configure model settings, pass inputs, and use AI models inside apps and cloud flows.
That means prompt design becomes part of business-solution implementation. A prompt should have a defined task, known inputs, expected output structure, and a way to handle cases where the model produces incomplete or unsafe results.
For deterministic calculations or regulatory rules, ordinary logic may still be better. AI belongs where language understanding, extraction, summarization, classification, or generative assistance produces real value.
AB-410 expects awareness of Copilot Studio agents and how they fit into apps, portals, and broader solutions. An agent can answer questions, use knowledge, call flows, and participate in multi-step processes.
The important question is what the agent is allowed to do. A read-only support agent carries different risk from one that can create a case, change a customer record, approve a request, or call an external system.
Tool permissions, authentication, confirmation, human review, audit logging, and failure handling should be designed before an agent is given consequential actions.
PL-200 candidates often worked with Power Pages because organizations need secure external access for customers, partners, suppliers, applicants, or other outside users.
That skill remains useful in AB-410. Power Pages solutions still need authentication, table permissions, web roles, forms, lists, and careful control of what Dataverse data becomes visible externally.
AI can enrich the experience through agents or assisted content, but external exposure makes security more important rather than less.
Development, test, and production should be separated for important business solutions. Solutions, pipelines, environment variables, connection references, and controlled deployment reduce the risk of ad hoc changes.
AB-410 explicitly includes ALM awareness because intelligent applications have more moving parts: apps, flows, Dataverse schema, prompts, models, agents, and connections.
Generated assets should move through the same review and testing process as manually built assets. AI-assisted development can speed up creation, but it does not justify bypassing lifecycle control.
Also keep the habit of validating a solution with real users before expanding it. Intelligent features can accelerate building, but they can also hide weak requirements behind impressive demos. A small pilot with representative data and realistic exceptions often reveals more about solution quality than adding another feature.
Keep requirements gathering, stakeholder communication, Dataverse modeling, canvas apps, model-driven apps, Power Automate, Power Pages, business rules, business process flows, security, solutions, and ALM where the material still matches the current platform.
Discard advice that presents PL-200 as schedulable or Power Platform Functional Consultant Associate as a current certification. Update older terminology and add AI-first capabilities that did not exist in the retired blueprint.
If your broader Power Platform foundation is still weak, Power Platform Fundamentals and PL-900 remain useful for understanding the product family before deeper AB-410 work.
Take one business process such as employee onboarding, service requests, inspections, or customer follow-up. Model the data in Dataverse, build a model-driven or canvas app, and automate at least one process through Power Automate.
Then add one AI capability that solves a real problem: summarize a case, classify a request, extract structured data, generate a draft, or provide an agent that can answer questions from approved knowledge.
Finally, package the solution properly, move it through a test environment, validate permissions, and monitor failures. That project exercises the durable PL-200 foundation while adding the intelligent-app skills AB-410 now measures.
PL-200 retired because Microsoft changed the certification path around how business applications are now built. The core need to understand business processes did not disappear. It expanded to include AI-assisted design, prompts, models, agents, and intelligent automation.
For professionals who already earned PL-200, the credential remains part of their certification history while the underlying skills continue to be useful. For new candidates, AB-410 is the current Microsoft exam that reflects the updated role.
The strongest transition strategy is therefore to preserve the business-solution discipline of PL-200 and add AI where it creates measurable value rather than rebuilding your Power Platform knowledge from zero.
