1.3 The Power Platform Ecosystem

The Power Platform: Four Core Products

Microsoft Power Platform is a family of four low-code tools that let people build solutions without traditional software development:

• Power Apps — build custom business applications (canvas apps with a drag-and-drop design surface, or model-driven apps generated from a data model).
• Power Automate — build automated workflows, from simple cloud flows (e.g., "when a file is added to SharePoint, notify a Teams channel") to desktop flows that automate legacy or manual processes on a PC (robotic process automation, or RPA).
• Power Pages — build secure, low-code external-facing websites and portals so customers, partners, or citizens outside your organization can interact with your data (submit a form, check a case status, view a self-service dashboard).
• Copilot Studio — build conversational AI agents that can answer questions, use tools, and take action, deployable to channels like Teams, a website, or a Power Pages site.

PL-900 tests your ability to describe what each product does and, critically, to recognize which product fits a given business scenario — a recurring question pattern is "a company needs X; which Power Platform product should they use?"

Dataverse: The Common Data Layer

Microsoft Dataverse is the data platform that underpins the whole ecosystem. It stores data in tables (rows and columns, similar conceptually to a database, but with built-in business logic, relationships, and security baked in) and is the layer that Power Apps, Power Automate, Power Pages, and Copilot Studio can all read from and write to. Because Dataverse is shared infrastructure rather than something owned by any single product, think of it as the glue that lets the four Power Platform products work on the same data without custom integration code. A model-driven Power Apps form, a Power Automate flow trigger, a Power Pages portal submission, and a Copilot Studio agent's knowledge source can all point at the exact same Dataverse table.

Connectors: Extending Beyond Microsoft

Connectors are prebuilt bridges that let Power Apps and Power Automate talk to systems outside Dataverse — SharePoint, Outlook, SQL Server, Salesforce, Twitter/X, and well over a thousand other services. Microsoft groups connectors into tiers:

In Power Automate, a connector typically supplies the trigger that starts a flow (e.g., "when a new email arrives") and the actions that flow performs (e.g., "create a Dataverse row," "post a Teams message"). Understanding this trigger/action vocabulary matters for both the environment-management and Power Automate exam domains.

How It All Fits Into the Microsoft Cloud

Power Platform doesn't stand alone — it's designed to sit alongside the rest of Microsoft's cloud portfolio:

• Microsoft 365 supplies everyday connectors (Outlook, Teams, SharePoint, Excel) and is often where Power Apps and Power Automate solutions get embedded and consumed.
• Dynamics 365 apps are themselves built on Dataverse, so Power Platform and Dynamics 365 share the same underlying data model and can extend one another.
• Azure supplies identity (through Microsoft Entra ID, formerly Azure AD, which governs who can access which environment and table) and the underlying AI services — Azure OpenAI and Azure AI services power generative features across Copilot Studio agents, AI Builder, and the "AI-assisted" building experiences inside Power Apps and Power Automate.
• The Power Platform admin center ties governance together: environments, data loss prevention (DLP) policies, and monitoring all apply across every product in the suite from one place.

Putting the Pieces Together

A single business scenario often touches every product at once. Picture a company that wants to modernize how it handles customer service requests: a Power Pages portal lets external customers submit a request, which is stored as a row in a Dataverse table. A Power Automate cloud flow triggers automatically on that new row, routes the request for approval, and posts a notification in Teams. Internal staff manage and update the case through a Power Apps model-driven app built directly on that same Dataverse table. Meanwhile, a Copilot Studio agent embedded on the company website answers common customer questions by drawing on knowledge sources connected to that same underlying data — all four products working from one shared foundation rather than four disconnected systems.

AI Builder and the Generative Layer

AI Builder is a related capability worth knowing at a conceptual level: it lets makers add AI models — such as prediction, form processing, or object detection — directly into a Power Apps app or a Power Automate flow without writing machine-learning code. It draws on the same underlying Azure AI infrastructure that powers Copilot Studio agents, which is why Microsoft increasingly describes the platform's newer features as "AI-infused" rather than purely "low-code." When a PL-900 question describes a maker adding a prebuilt or custom AI model to automate document processing or prediction inside an app or flow, that's describing AI Builder, not Copilot Studio — Copilot Studio is specifically for building conversational, tool-using agents, while AI Builder embeds discrete AI models into existing app and flow logic.

Licensing: A Conceptual View

PL-900 doesn't expect you to memorize exact SKU prices, but it does expect you to know that Power Platform licensing is capacity- and per-user based, and that some capabilities (like premium connectors, larger Dataverse storage, or advanced AI Builder credits) require add-on licensing beyond what's bundled with a Microsoft 365 subscription. Recognizing that a scenario requires a premium license — even without naming the exact plan — is the level of licensing knowledge the exam tests. Keep this distinction between "included" and "premium" capability in mind as you move into the deeper Power Apps, Power Automate, and Copilot Studio chapters ahead.