Skip to content

PL-900 cheat sheet ​

The distinctions that come up again and again on PL-900, plus a quick reference card.


Admin Centers ​

The Triangle Rule: ​

  • Microsoft 365 Admin Center = Add users to the TENANT (creating users in Entra ID/Azure AD)
  • Power Platform Admin Center = Add users to ENVIRONMENTS + Create environments

Mental Model: ​

  • M365 = People (tenant-level users)
  • Power Platform = Places (environment-level access)

Exam Trick to Watch For: ​

When they say "add a user to Power Platform," ask yourself:

  • Tenant level? → Microsoft 365 Admin Center
  • Environment level? → Power Platform Admin Center

Remember: If it's about the tenant, the answer is NEVER Power Platform Admin Center.


Canvas vs Model-Driven Apps ​

The Simple Rule: ​

FeatureCanvasModel-Driven
When to use"I want specific layout/design""I need forms/views driven by Dataverse data"
Control levelFull control, pixel-perfectAuto-generated UI
Data sourceAny (SharePoint, SQL, Excel, etc.)Dataverse only
CustomizationCustom UI, flexibleData-first, structured layout

Key Triggers: ​

  • "Customized layout" → Canvas App
  • "Custom screen design" → Canvas App
  • "Complex data relationships in Dataverse" → Model-Driven App

"Highly customized layout" means canvas, not model-driven.


Model-Driven App Components ​

What You CAN Add Directly: ​

  • Forms
  • Business Process Flows
  • Views
  • Dashboards
  • Charts

What You CANNOT Add: ​

  • Business Rules (they come automatically with tables/forms - don't add separately)
  • Cloud Flows

Memorize: ​

  • Forms? Yes
  • BPF? Yes
  • Business Rules? No (auto-included, not manually added)
  • Cloud Flows? No

Canvas Controls for Lists ​

The Perfect Rule: ​

ControlSearchable?Best ForScreen Space
Combo BoxYes200+ items, large listsCompact
DropdownNoSmall listsCompact
List BoxNoEverything visibleHUGE (kills scroll space)
RadioNoTiny lists onlyMedium

Exam Triggers: ​

If you see:

  • "search" OR
  • "more than 200 items" OR
  • "conserve screen space"

→ Combo Box every time.


Flow Troubleshooting Tools ​

The Cheat Code: ​

ToolPurposeWhen to Use
Flow CheckerDesign-time issuesFind errors/performance issues BEFORE running
TestRun manually while editingSee what happens during development
View OutputsRuntime detailsFind expression errors, see JSON details

Mental Model: ​

  • Flow Checker = Static analysis (like a linter)
  • Test = Dynamic execution (run it and see)
  • View Outputs = Debugging expressions and JSON

For the Exam: ​

  • Identify error in expression → View Outputs
  • Check performance issues before running → Flow Checker
  • Test while building → Test

Creating Flows with Copilot ​

The Sequence (Always): ​

  1. Open Power Automate maker portal (NOT Copilot Studio)
  2. Describe automation
  3. Add connections

Mnemonic: ​

"Automation lives in Power Automate"

Remember: ​

  • Power Automate = where you create flows with Copilot
  • Copilot Studio = where you create chatbots

Don't overthink it - flows live in Power Automate!


Power Pages Industry Templates ​

The Only 3 Real Templates: ​

  1. Government
  2. Education
  3. Financial Services

Easy Mnemonic: ​

"GEF: Government, Education, Financial"

NOT Power Pages Templates (These are Microsoft Cloud verticals): ​

  • Healthcare
  • Retail

Just memorize GEF and you're done.


Quick reference card ​

The Speed Round: ​

  • Highly customized layout → Canvas
  • Complex data relationships in Dataverse → Model-Driven
  • Add tenant users → Microsoft 365 Admin Center
  • Add environment users / Create environments → Power Platform Admin Center
  • Search a big list → Combo Box
  • Power Pages templates → GEF (Government, Education, Financial)
  • Flow design-time errors → Flow Checker
  • Flow expression errors → View Outputs
  • Create flows with Copilot → Power Automate maker portal
  • Add to model-driven app → Forms and BPF (not Business Rules)

Personal study notes written from official documentation. Not affiliated with Microsoft or GitHub. Contains no exam questions.