PL-900: Microsoft Power Platform Fundamentals Study Guide
PL-900 (Microsoft Power Platform Fundamentals) validates foundational knowledge of the Power Platform: its business value plus the core products Power BI, Power Apps, Power Automate, Power Pages, Copilot Studio, and AI Builder, all built on Microsoft Dataverse. It is aimed at business users, citizen developers, and IT decision-makers who want to demonstrate they understand how low-code/no-code tools deliver business solutions. The exam is conceptual rather than hands-on, so focus on knowing what each product does, when to use it, and how the pieces fit together.
Domain 1: Describe the Business Value of Power Platform
- Power Platform is a low-code/no-code suite (Power BI, Power Apps, Power Automate, Power Pages, Microsoft Copilot Studio) underpinned by Microsoft Dataverse; 'Power Server' is not a real product.
- The core business value is empowering 'citizen developers' (non-professional makers) to build apps, automations, and reports with visual designers and Excel-like formulas instead of traditional code.
- Connectors are pre-built integration points to hundreds of Microsoft and third-party data sources and services; Power Platform is not limited to Microsoft data.
- Standard connectors are included with most Microsoft 365/Dynamics 365 licenses; premium connectors (e.g. SQL Server, Azure, custom connectors, Dataverse in some plans) require additional per-user or per-app/per-flow licensing.
- Custom connectors let organizations integrate with any service exposing a REST API, including proprietary, legacy, or internal systems, without waiting for Microsoft to build a native connector.
- Data Loss Prevention (DLP) policies classify connectors into Business, Non-business, and Blocked groups; data cannot flow between connectors in different groups within the same app or flow.
- Environments are logical containers that isolate apps, flows, and data; organizations use separate Development, Test, and Production environments with their own security, governance, and DLP settings.
- The Power Platform admin center is where administrators manage environments, DLP policies, data integration, capacity, and analytics.
- The Microsoft 365 admin center (not the Power Platform admin center) is used to manage user accounts, groups, and licenses.
- Governance features include environment-level DLP, tenant-wide DLP, sharing limits, and solution checker enforcement to give admins control as adoption scales.
- Power Platform integrates natively with Microsoft 365 (Teams, SharePoint, Outlook, Excel) and Azure, and offers embedded experiences so apps and flows run inside those products.
- The Center of Excellence (CoE) Starter Kit is a free Microsoft toolkit of apps, flows, and dashboards that helps organizations monitor, govern, and nurture Power Platform adoption.
- Microsoft Dataverse is the secure, cloud-based relational data platform that stores business data and provides logic, security, and compliance for Power Platform solutions.
- Low-code development reduces cost and time-to-value by letting business teams solve departmental problems quickly, easing the backlog on professional development teams.
Domain 2: Identify Foundational Components of Power Platform
- In Dataverse a table (formerly 'entity') stores data as rows (records) and columns (fields/attributes); each column has a defined data type.
- Each Dataverse environment contains a single database that holds all of that environment's tables and records.
- Relationships associate rows across tables: one-to-many (a customer with many orders), many-to-one, and many-to-many (students and courses, managed via an implicit junction table).
- A lookup column stores a reference to a row in another table, implementing the 'many' side of a one-to-many relationship.
- An Autonumber column auto-generates unique, sequential, human-readable identifiers (with optional prefix/format) on row creation, ideal for ticket or order numbers.
- Dataverse provides role-based access control through security roles, plus auditing/audit logging of data changes for compliance.
- Business rules are no-code logic that set field values, set defaults, show error messages, make fields required, or show/hide fields based on conditions without writing code.
- Solutions are containers that package customizations (apps, flows, tables, columns, plugins) so they can be transported between environments for ALM.
- Unmanaged solutions can be directly edited in the target environment and are used for development; managed solutions cannot be directly customized and are used for test/production deployment.
- Connectors are the integration layer that abstracts API communication, authentication, and data transformation between apps/flows/dashboards and external services.
- Connector types: standard (included with base licenses), premium (require extra licensing), and custom (built by the organization for REST APIs lacking a connector).
- An on-premises data gateway securely relays data between cloud Power Platform services and on-premises sources behind a firewall, using an encrypted outbound connection without opening inbound ports.
- Dataverse is relational and supports referential integrity, business logic, and security, making it more than a simple flat data store.
- Standard tables (e.g. Account, Contact) ship with Dataverse; custom tables are created to store organization-specific data.
Domain 3: Demonstrate Capabilities of Power BI
- Power BI Desktop is a free Windows application used to connect to data, transform it with Power Query, build data models, and author reports and visualizations.
- The Power BI service (app.powerbi.com) is the cloud platform where reports are published, dashboards are created, and content is shared and consumed.
- A dataset (now called a semantic model) is the imported or connected data plus its model that reports are built on; one dataset can be shared and reused across multiple reports in a workspace.
- A report is a multi-page artifact built on a single dataset, where each page can contain many interactive visuals (goes 'deep').
- A dashboard exists only in the Power BI service and is a single-page canvas of tiles pinned from one or more reports, even across different datasets (goes 'broad').
- A workspace is a collaborative space in the service where teams create, publish, and manage datasets, reports, and dashboards with role-based access (Admin, Member, Contributor, Viewer).
- DAX (Data Analysis Expressions) is the formula language used to create calculated columns, measures, and calculated tables; measures aggregate at query time.
- Power Query (M language) is the data preparation/transformation layer used to clean, shape, remove duplicates, merge, and filter data before loading.
- Sharing options include publishing to a workspace and granting access, packaging a workspace as a Power BI app, and 'Publish to web' which creates a public embed code (no security - avoid for sensitive data).
- Data alerts can be set on dashboard tiles to notify a user (via email or the mobile app) when a numeric value crosses a defined threshold.
- Drill-down lets users navigate from summary-level data to more detailed data within a hierarchy in a visual.
- Power BI Desktop is free for authoring, but publishing, sharing, and collaborating in the service generally require Power BI Pro or Premium Per User licensing.
- Power BI connects to many data sources, including SQL Server (enterprise relational) and Excel workbooks (file-based), with scheduled refresh for imported data.
- Power BI Mobile apps (iOS/Android/Windows) let users view reports and dashboards and receive alerts on the go.
Domain 4: Demonstrate Capabilities of Power Apps
- Canvas apps give the maker full pixel-level control over screen layout, starting from a blank canvas or template, and can connect to many data sources (Dataverse, SharePoint, Excel/OneDrive, SQL, and more).
- Model-driven apps derive their UI, forms, views, and navigation automatically from the underlying Dataverse data model and require Dataverse as the data source.
- Power Apps formulas use Power Fx, a low-code expression language similar in syntax to Excel formulas, making it accessible to spreadsheet users.
- Common Power Fx functions include Filter(), LookUp(), Patch() (create/update records), Navigate() (move between screens), and Collect() (build collections).
- Navigate() moves between canvas-app screens, e.g. Navigate(Screen2, ScreenTransition.Fade), with transitions like Fade, Cover, UnCover, and None.
- A Gallery control displays a scrollable list of multiple records using a repeating template layout.
- A Form control (display/edit) shows, edits, or creates a single record from a data source and supports validation.
- The OnStart property runs when an app loads and is used to set global variables or preload initial data; OnVisible runs each time a screen is shown.
- Power Pages (formerly Power Apps portals) builds external-facing websites that let users outside the organization interact with Dataverse data.
- Canvas apps support offline capabilities and device features like the camera, making them ideal for mobile scenarios such as photographing receipts.
- Model-driven apps are built from components including tables, forms, views, charts, dashboards, and business process flows defined in Dataverse.
- Canvas apps can be auto-generated from a data source (e.g. a SharePoint list or Dataverse table) to quickly create a three-screen browse/detail/edit app.
- Power Apps provides responsive design and a cross-platform runtime so apps run in a browser and in the Power Apps mobile app on phones and tablets.
- Component libraries let makers create reusable UI components that can be shared across multiple apps for consistency.
Domain 5: Demonstrate Capabilities of Power Automate
- A cloud flow runs in the cloud and connects services and data sources; the three trigger types are automated (event), instant (manual/button), and scheduled (recurrence).
- Automated cloud flows start when a specific event occurs, such as an email arriving in Outlook, a record created in Dataverse, a file added to OneDrive, or an item created in SharePoint.
- Instant (button) flows are triggered manually on demand, including being called from a Power Apps canvas app button or a mobile/Teams button.
- Scheduled flows run on a recurring time-based schedule (e.g. daily at 8:00 AM, hourly, or weekly) using a recurrence trigger.
- Every flow is built from a trigger (the event that starts it) plus one or more actions (the operations it performs).
- Desktop flows provide Robotic Process Automation (RPA) to automate legacy desktop applications by recording mouse clicks, keyboard input, and screen interactions when no API exists.
- Desktop flows can run attended (with the user signed in and watching) or unattended (on a machine without interactive sign-in), and can be triggered from a cloud flow.
- The Approvals action creates structured approval workflows that send requests to designated users via email and Teams; users approve or reject, and the flow branches on the outcome.
- Approval flows support sequential multi-level (hierarchical) approvals, such as team lead, then manager, then finance director.
- The Condition (if/else) action and Switch action add conditional branching so flows take different paths based on data values.
- Loop controls 'Apply to each' iterate over every item in an array or collection, and 'Do until' loops until a condition is met.
- Power Automate provides a library of pre-built templates that serve as ready-made starting points for common automation scenarios.
- Power Automate integrates deeply with Microsoft Teams to post messages, send notifications/adaptive cards, and trigger flows directly from Teams.
- Business process flows guide users through a consistent set of defined stages and steps to follow a standard business procedure (distinct from cloud and desktop flows).
Domain 6: Describe AI Builder
- AI Builder is a low-code AI capability that adds intelligence to Power Apps and Power Automate without requiring data science expertise or writing code.
- AI Builder offers two model categories: prebuilt models (ready to use immediately, no training) and custom models (you train them on your own data).
- Prebuilt models include text recognition/OCR, sentiment analysis, key phrase extraction, language detection, text translation, business card reader, category classification, and invoice/receipt/ID processing.
- The document processing model (formerly 'form processing') extracts structured key-value pairs and tabular data from documents like invoices, receipts, purchase orders, and forms.
- Training a custom document processing model requires a minimum of five sample documents of the same type/layout.
- Object detection identifies, locates, and counts specific objects within images, useful for inventory, retail shelf, or warehouse scenarios.
- The category classification (text classification) model learns from labeled examples to automatically sort text into custom categories you define, e.g. routing feedback to Billing, Technical Support, or Sales.
- The prediction model forecasts a binary (yes/no) outcome or numerical value from historical data patterns, such as predicting customer churn.
- AI Builder models are exposed as actions you add to a Power Automate cloud flow to process documents, analyze/classify text, or score predictions.
- In canvas apps you can add AI Builder controls such as the business card reader or text recognition to capture and extract data directly in the app.
- AI prompts (powered by GPT/Azure OpenAI) let makers add generative-AI text generation, summarization, and extraction using natural-language instructions.
- AI Builder uses a credit-based consumption model; processing data consumes AI Builder credits, and custom or high-volume models typically consume more than prebuilt ones.
- The custom model lifecycle is: choose model type, connect/prepare data, train, evaluate performance, then publish before it can be used.
- AI Builder is built on Dataverse and inherits its security, and AI capabilities require an appropriate license or credit allocation.
PL-900 exam tips
- Master the four pillars plus their split: Power BI = analyze/visualize, Power Apps = build apps, Power Automate = automate workflows, AI Builder = add AI; Dataverse is the common data store underneath. Many questions test which tool fits a described scenario.
- Know the canvas vs model-driven distinction cold: canvas = full layout control and many data sources; model-driven = data-first, Dataverse-required. Likewise know report (multi-page, one dataset) vs dashboard (single page, pinned tiles from many reports).
- Memorize the three cloud-flow trigger types (automated/event, instant/manual, scheduled/recurrence) and that desktop flows = RPA for apps without APIs.
- Distinguish the admin centers: Power Platform admin center manages environments and DLP; Microsoft 365 admin center manages users, groups, and licenses. DLP classifies connectors into Business/Non-business/Blocked.
- Watch for true/false and 'select all that apply' wording. Read carefully for distractors like fake products ('Power Server') and licensing nuances (standard connectors free, premium connectors require extra licensing).
- The exam is 45 minutes with a passing score of 700/1000; pace yourself, flag uncertain items for review, and answer every question since there is no penalty for guessing.
Study guide FAQ
How is PL-900 scored and what do I need to pass?
PL-900 is scored on a scale of 100 to 1000, and you need a score of 700 or higher to pass. The exam runs about 45 minutes and contains a mix of multiple-choice, multiple-response, and true/false questions. There is no penalty for wrong answers, so answer everything.
Do I need hands-on or coding experience to pass PL-900?
No. PL-900 is a fundamentals exam that tests conceptual understanding of what each Power Platform product does and when to use it, not the ability to build solutions or write code. Some hands-on exploration of Power Apps, Power Automate, and Power BI Desktop helps reinforce the concepts, but deep technical or coding skills are not required.
What is the difference between Power Platform and Microsoft Dataverse?
Power Platform is the overall suite of low-code products (Power BI, Power Apps, Power Automate, Power Pages, and Copilot Studio) plus AI Builder. Microsoft Dataverse is the secure, cloud-based relational data platform that sits underneath and stores the business data, tables, relationships, security roles, and business logic that those products use.
Which licenses do I need to use connectors, and what makes a connector 'premium'?
Standard connectors (such as SharePoint, Outlook, OneDrive, and Teams) are included with most Microsoft 365 and Dynamics 365 licenses at no extra cost. Premium connectors (such as SQL Server, Azure services, Dataverse in some plans, and custom connectors) require an additional Power Apps or Power Automate per-user or per-app/per-flow license. The exam expects you to recognize this distinction.