Historical PL-500 Scope
PL-500 was Microsoft's Microsoft Power Automate RPA Developer exam until its retirement on 2026-06-30. Its final published scope covered Design automations, Develop automations, Deploy and manage automations. This page preserves that dated outline for historical comparison and curriculum cleanup. It is not a schedulable exam, and its prices, delivery details, registration links, and practice calls to action must not be used for a new certification plan.
Who PL-500 Was For
Nobody should start a new certification plan around PL-500. This page serves former candidates, credential holders, training teams removing stale material, and practitioners deciding whether prior preparation is reusable for AB-100. New candidates should verify the active Microsoft page and current dated study guide before booking.
Skills You Should Be Ready to Demonstrate
- Preserve practical experience from Design automations only where the current guide shows meaningful overlap
- Preserve practical experience from Develop automations only where the current guide shows meaningful overlap
- Preserve practical experience from Deploy and manage automations only where the current guide shows meaningful overlap
How to Reuse Your Preparation
Do not rename an old PL-500 checklist or question bank as AB-100. Compare the two official guides objective by objective and classify each historical skill as transferable, changed, or absent. Use transferable experience as a diagnostic baseline, then rebuild labs and review around AB-100's current domain weights, products, role expectations, security controls, and operational tasks. Because Microsoft identifies AB-100 as the broader replacement path, review the skill map below before assuming equivalence.
What changed from PL-500 to AB-100
| Historical PL-500 | Current AB-100 | Practical impact |
|---|
Design automations
25-30% | Plan AI-powered business solutions
25-30% | Process analysis transfers, while AB-100 broadens planning to AI readiness, value, responsible use, data, and organizational adoption. |
Develop automations
45-50% | Design AI-powered business solutions
25-30% | Hands-on desktop and cloud flow building gives way to architecture across agents, copilots, models, integrations, and human oversight. |
Deploy and manage automations
20-25% | Deploy AI-powered business solutions
40-45% | Operational discipline remains useful, but AB-100 adds evaluation, governance, security, monitoring, cost, and multi-agent lifecycle concerns. |
Migration checklist
- Stop scheduling, selling, or presenting PL-500 as a current exam.
- Compare completed PL-500 preparation with the current AB-100 guide; do not carry over obsolete weighting or mechanics.
- Create a fresh AB-100 plan around its current domains and hands-on role expectations.
- Remove or quarantine practice content that cannot be mapped to a current objective with source evidence.
- Recheck Microsoft's dated AB-100 study guide before booking because role-based exams change over time.
Open the official AB-100 study guide
Historical Domain Guide
Design automations: Historical Scope
Historically, Design automations required candidates to connect configuration choices with operational outcomes. The official outline included Design automations using Power Automate features and capabilities. Preserve hands-on understanding of those tasks where the successor comparison shows overlap, but do not treat this retired weighting or terminology as a current exam blueprint.
- Use the official historical objectives to document what design automations required
- Mark each prior skill as transferable, changed, or absent in the current replacement guide
- Rebuild practical exercises around current services, interfaces, governance, and role expectations
Develop automations: Historical Scope
Historically, Develop automations required candidates to connect configuration choices with operational outcomes. The official outline included Develop cloud flows; Develop desktop flows. Preserve hands-on understanding of those tasks where the successor comparison shows overlap, but do not treat this retired weighting or terminology as a current exam blueprint.
- Use the official historical objectives to document what develop automations required
- Mark each prior skill as transferable, changed, or absent in the current replacement guide
- Rebuild practical exercises around current services, interfaces, governance, and role expectations
Deploy and manage automations: Historical Scope
Historically, Deploy and manage automations required candidates to connect configuration choices with operational outcomes. The official outline included Perform target environment preparation; Implement access to RPA components. Preserve hands-on understanding of those tasks where the successor comparison shows overlap, but do not treat this retired weighting or terminology as a current exam blueprint.
- Use the official historical objectives to document what deploy and manage automations required
- Mark each prior skill as transferable, changed, or absent in the current replacement guide
- Rebuild practical exercises around current services, interfaces, governance, and role expectations
Sources and Verification
Verified 2026-08-26
How this page was made
Cert Atlas compared Microsoft's final PL-500 study guide with the current AB-100 guide at the domain and objective level, then checked Microsoft's retirement list and transition announcement. OpenAI Codex assisted with extraction, normalization, comparison, and drafting. Claims were reviewed against the linked official sources; no exam stems, answers, choices, or explanations were used.
Historical PL-500 Domains
1.0 Design automations
25-30%
- 1.1Design automations using Power Automate features and capabilities
Leverage the Power Automate ecosystem; Differentiate between cloud flows and desktop flows; Design automations using desktop flows and cloud flows; Differentiate trigger types for cloud flows; Differentiate options for interacting with target applications and browsers; Differentiate the different methods for running a desktop flow; Assess the ability to run cloud and desktop flows concurrently; Recommend running desktop flows attended versus unattended; Differentiate HTTP actions in cloud and desktop flows; Assess if work queues are applicable for the automation; Design custom actions; Design automations using other Microsoft Power Platform features and capabilities; Design automations that include canvas and model-driven apps; Design automations using connectors, custom connectors, connection references, and connections for cloud flows; Design automations that include Microsoft Dataverse; Design automations that analyze and enhance data and documents; Differentiate Microsoft AI options for processing documents in desktop and cloud flows; Differentiate Microsoft AI options for processing data in desktop and cloud flows; Recommend optical character recognition (OCR) capabilities in desktop flows; Recommend Document Automation Toolkit for use in automation design; Design automations using scripting languages in desktop flows; Design automations using scripting languages including PowerShell and Visual Basic Script (VBScript); Recommend automation use cases that use JavaScript; Design an automation that uses the document object model (DOM)
2.0 Develop automations
45-50%
- 2.1Develop cloud flows
Develop a cloud flow that calls a desktop flow; Develop and use child cloud flows including passing and returning data; Perform actions in cloud flows by calling external APIs; Implement trigger conditions and concurrency in cloud flows; Implement timeout and retry policies in cloud flows; Implement data objects and data operations in cloud flows; Perform text parsing including JSON, XML, and CSV in cloud flows
- 2.2Develop desktop flows
Implement UI options; Implement datatables, lists, and custom objects in desktop flows; Implement subflows in desktop flows; Perform actions in desktop flows by calling external APIs; Implement timeout and retry in desktop flows; Implement data objects and data operations in desktop flows; Perform text parsing including JSON, XML, and CSV in desktop flows; Implement custom actions in desktop flows
- 2.3Implement logic in cloud and desktop flows
Implement flow control in cloud and desktop flows including loops; Implement expressions in cloud flows; Implement variable actions for cloud and desktop flows; Implement secure input and output data in actions in cloud flows; Implement secure variables in desktop flows; Implement priority for desktop flows in a queue; Implement exception handling blocks in cloud and desktop flows to handle system exceptions; Implement error handling routines in cloud and desktop flows to handle business exceptions; Implement work queues in cloud and desktop flows
- 2.4Build custom connectors and implement connector configurations
Build a custom connector; Implement authentication for custom connectors; Implement custom connector policy templates; Develop code in a custom connector
- 2.5Perform automation infrastructure management
Recommend credential management practices; Utilize on-premises data gateway to connect resources from cloud flows; Build components in Microsoft Dataverse solutions
- 2.6Test automations and finalize development efforts
Test a cloud flow; Test a desktop flow; Utilize environment variables and configuration files to manage configurations; Utilize debugging features in cloud and desktop flows
3.0 Deploy and manage automations
20-25%
- 3.1Perform target environment preparation
Implement Microsoft Power Platform application lifecycle management (ALM); Differentiate credentials used for different environments; Recommend how to deploy solution components to other environments; Build virtual desktop environments for unattended desktop flow execution; Assess data loss prevention (DLP) policies for RPA execution; Assess Microsoft Power Platform DLP policies; Assess how DLP policies impact actions in cloud and desktop flows; Assess how DLP policies apply to custom connectors
- 3.2Implement access to RPA components
Perform sharing of cloud and desktop flows; Perform sharing of machines and machine groups; Recommend security roles required to run and monitor cloud and desktop flows; Implement service accounts and service principals; Implement machine groups and queues required for desktop flow automations; Assess machine and machine group requirements; Perform machine registration management; Perform machine group management; Implement load balancing of desktop flows by using machine groups and queues; Perform operations on the run queue to manage desktop flows; Analyze cloud and desktop flow run history from the Power Automate portal