Home / crm-business-applications / Microsoft Certified: Power Platform Fundamentals (PL-900) / Cheat Sheet
Microsoft Certified: Power Platform Fundamentals (PL-900)

PL-900 Cheat Sheet

PL-900 Tests Which Power Platform Tool Fits the Need — Not Building Apps

PL-900 is a 45-minute fundamentals exam for business users and newcomers. The 2026 outline adds Copilot Studio agents as a full domain, so read each stem for who uses the solution and whether it shows, moves, stores or converses.

Check Your Readiness →
Among the harder certs
Avg: Not published by Microsoft
Pass: 750 / 1000
Most candidates understand Microsoft Certified: Power Platform Fundamentals (PL-900) concepts — and still fail. This exam tests how you apply knowledge under pressure.

PL-900 Domain Map (skills measured July 24, 2026)

Four domains share 20–25% each, so no area can be skipped. Stems describe a team, a pain point and a goal; distractors swap near-identical terms such as form and view, Copilot and Copilot Studio, or knowledge and tool. 700/1000 to pass; question count not published.

  1. 01
    Business value (5–10%) — low-code, Power Apps, Power Automate, Power Pages, Dataverse, connectors, Copilot vs. Copilot Studio
  2. 02
    Environment management (20–25%) — environments, tables, columns, relationships, forms vs. views, business rules, security roles, data policies, pipelines
  3. 03
    Power Apps (20–25%) — canvas vs. model-driven vs. code apps, Plan designer, vibe experience, Copilot creation, sharing
  4. 04
    Power Automate (20–25%) — automated, instant and scheduled cloud flows, desktop flows, triggers vs. actions, approvals, AI Builder
  5. 05
    Copilot Studio agents (20–25%) — topics, knowledge, tools, MCP servers, channels, analytics, evaluations, Agent 365

Wrong instinct vs correct approach

Makers keep building flows that copy Dataverse data into personal Gmail accounts; Outlook and SharePoint must still work
✕ Wrong instinct

Remove the makers' Dataverse security roles

✓ Correct approach

Create a data policy in the Power Platform admin center that puts Dataverse, Outlook and SharePoint in the business group and Gmail in non-business or blocked. Connectors from different groups cannot be combined, so the copy flow cannot be saved or run.

Technicians need a branded tablet app matching a paper checklist, saving photos and readings to a SharePoint list
✕ Wrong instinct

Build a model-driven app for consistent screens

✓ Correct approach

A canvas app gives screen-by-screen layout control and connects to SharePoint through a connector. Model-driven apps require Dataverse and generate layout from tables, forms and views, so they cannot match a branded design.

A Forms submission must go to the requester's manager and approved items must land in a SharePoint list
✕ Wrong instinct

A scheduled flow checking for new responses every hour

✓ Correct approach

Use an automated cloud flow triggered by When a new response is submitted, then the Approvals action, then a SharePoint create item action. A cloud flow has exactly one trigger; everything after it is an action.

A maker changed an agent's instructions and wants to rerun 50 prepared questions with expected answers before publishing
✕ Wrong instinct

Check the Copilot Studio analytics page

✓ Correct approach

Run agent evaluations against a test set; cases are graded against expected answers or criteria. Analytics only reports sessions, resolution, escalation and satisfaction from real published use, and Agent 365 governs agents organisation-wide rather than testing one.

Know these cold

  • ▸ Each environment holds at most one Dataverse database; production never belongs in the default environment
  • ▸ Form = one row; view = list of rows; dashboard = overview across sources
  • ▸ One-to-many uses a lookup column on the many side; students-to-courses needs many-to-many
  • ▸ Business rules handle simple validation; calling external services needs a flow or plug-in
  • ▸ Premium and custom connectors need premium licensing; standard connectors come with Microsoft 365 rights
  • ▸ Model-driven apps require Dataverse; canvas apps connect to SharePoint, SQL and other sources
  • ▸ Sharing an app is not enough — sers also need a security role and a licence
  • ▸ Automated = event trigger; instant = button or selected item; scheduled = recurrence
  • ▸ Copilot in maker tools helps build; Copilot Studio builds agents that serve end users
  • ▸ Pipelines deploy solutions between environments; hand-exported unmanaged solutions are not governed ALM

Can you answer these without checking your notes?

In this scenario: "Makers keep building flows that copy Dataverse data into personal Gmail accounts; Outlook and SharePoint must still work" — what should you do first?
Create a data policy in the Power Platform admin center that puts Dataverse, Outlook and SharePoint in the business group and Gmail in non-business or blocked. Connectors from different groups cannot be combined, so the copy flow cannot be saved or run.
In this scenario: "Technicians need a branded tablet app matching a paper checklist, saving photos and readings to a SharePoint list" — what should you do first?
A canvas app gives screen-by-screen layout control and connects to SharePoint through a connector. Model-driven apps require Dataverse and generate layout from tables, forms and views, so they cannot match a branded design.
In this scenario: "A Forms submission must go to the requester's manager and approved items must land in a SharePoint list" — what should you do first?
Use an automated cloud flow triggered by When a new response is submitted, then the Approvals action, then a SharePoint create item action. A cloud flow has exactly one trigger; everything after it is an action.

Common Exam Mistakes — What candidates get wrong

Choosing a shared canvas app when customers or partners need a website

External audiences who browse anonymously or sign in with their own identities are served by Power Pages sites with data in Dataverse. Power Apps targets users inside the tenant. Words like residents, customers, portal or registration point to Power Pages.

Treating a data policy as record-level security

Data (DLP) policies group connectors as business, non-business or blocked so they cannot be combined in one app or flow. Which rows a user sees comes from Dataverse security roles, business units and teams; environment security groups control who enters the environment.

Picking a desktop flow for services that already have connectors

SharePoint, Outlook, Forms and Teams have standard connectors, so a cloud flow is simpler and needs no machine. Desktop flows are RPA for legacy Windows or web screens with no API, running attended alongside staff or unattended for batch work.

Adding a knowledge source when the agent must take an action

Knowledge sources such as SharePoint, websites, files and Dataverse ground answers only. Creating a ticket or booking a room needs a tool: a connector for one operation, an agent flow for multi-step logic, or an MCP server supplying external tools.

Studying Power Virtual Agents material written before the 2026 outline

The July 2026 outline covers generative orchestration, tools, MCP servers, agent evaluations, analytics and Microsoft Agent 365. It also adds Plan designer, the vibe experience and code apps in Power Apps, plus Copilot in desktop flows. Older courses miss all of these.

Resources to help you pass Power Platform Fundamentals PL-900 on your first attempt

PL-900 hinges on matching each need to apps, flows, pages, Dataverse or agents. Check your mapping.