What Is Microsoft Power Platform? What’s Included in 2026 and How Teams Start

Microsoft Power Platform is Microsoft’s family of low-code tools for building business apps, automating work, creating AI agents, analyzing data and publishing websites, all on shared data, connectors and security. If your company runs Microsoft 365, you already have a piece of it, whether anyone has opened it yet or not.

In this tutorial, we’ll explain what is Power Platform as it stands in November 2026: the five products, the shared layer underneath them, how licensing works at a high level, and how our team actually rolls it out. We’ll use two real apps from the SPGuides tenant as the running example.

Quick answer: Microsoft Power Platform = Power Apps (apps), Power Automate (flows), Power BI (reports), Copilot Studio (AI agents, formerly Power Virtual Agents) and Power Pages (websites), sitting on Dataverse, connectors, AI Builder and Copilot. Admins govern it from the Power Platform admin center with environments, data policies and Managed Environments.

What You Need Before You Start

Everything runs in the browser, and most Microsoft 365 work accounts can sign in to the maker portals right away.

• A Microsoft 365 work or school account (personal Outlook.com accounts don’t work).
• Power Apps: make.powerapps.com. Power Automate: make.powerautomate.com.
• Copilot Studio: copilotstudio.microsoft.com. Power BI: app.powerbi.com plus the free Power BI Desktop app.
• Power Pages: make.powerpages.microsoft.com.
• For admins: the Power Platform admin center at admin.powerplatform.microsoft.com and the Power Platform Administrator role.

If you want a guided path for one product, start with our Power Apps tutorials hub. It walks from your first canvas app to formulas, galleries and delegation.

The Five Power Platform Products in 2026

Microsoft now groups the platform around what you build: agents, apps, automations, analytics and websites.

Power Apps builds business apps. Canvas apps give you a blank screen and a formula language (Power Fx) that feels like Excel, and they connect to SharePoint, Excel, SQL or Dataverse. Model-driven apps in Power Apps start from your Dataverse tables and generate forms, views and navigation for you.

Power Automate runs workflows. Cloud flows react to triggers such as a new SharePoint item, an email or a schedule, while desktop flows record and replay clicks in older Windows apps (robotic process automation). Our Power Automate tutorials cover both, with real flows we built.

Power BI turns data into interactive reports and dashboards. You model and design in Power BI Desktop, then publish to the Power BI service to share. If you’ve never built one, follow our steps to create a report in Power BI Desktop.

Copilot Studio is the low-code studio for AI agents and agent flows. It replaced Power Virtual Agents, and agents you build there can answer questions from your knowledge sources and take actions in Teams, Microsoft 365 Copilot or a website. Our guide to create an agent using Microsoft Copilot Studio shows the full setup.

Power Pages builds secure, data-driven websites for people outside your organization, such as customers, partners or applicants. It grew out of Power Apps portals and stores its data in Dataverse. You can see a typical build in our post on how to create a form in Power Pages.

What Sits Underneath: Dataverse, Connectors, AI Builder and Copilot

The products feel like one platform because they share the same plumbing.

• Microsoft Dataverse is the built-in database: tables, relationships, business rules and row-level security. Read what Microsoft Dataverse is if you’re deciding where your data should live.
• Connectors are prebuilt wrappers around APIs (SharePoint, Outlook, Salesforce, SQL Server and many more). Some are standard and some are premium, which matters for licensing; we explain standard vs premium connectors separately.
• AI Builder adds prebuilt or custom AI models, such as document processing, to apps and flows. One real use is to extract invoice details with AI Builder from files in SharePoint.
• Copilot in Power Platform lets you describe an app, flow, page or report in plain English and get a working draft you then refine.

Power Fx, the formula language, also runs across Power Apps, Copilot Studio and Dataverse formula columns.

Our Service Desk Example: Two Apps, Two Data Sources

Our SPGuides tenant has one service desk scenario built twice, which shows the main choice every team faces: SharePoint list or Dataverse.

The first is Service Desk Demo, a canvas app on a SharePoint list called Service Requests (about 620 items) on our /sites/SPGuides site. It needed no extra license because SharePoint is a standard connector.

It also taught us a real lesson: a Search() over that list showed a delegation warning and missed items past row 500, which we explain in our Power Apps delegation guide.

The second is the SPGuides Service Request App, a model-driven app on a Dataverse table named Service Request in our “Power Platform” developer environment. Status (Open, In Progress, Closed), views, forms and security come from the table, so we wrote almost no formulas.

If you’re stuck on that decision, our comparison of Dataverse vs SharePoint list for Power Apps lays out the tradeoffs we hit.

Step 1: Plan Your Environments

An environment is a container for apps, flows, agents, connections and at most one Dataverse database. Every tenant gets a Default environment where all licensed users can build, which is fine for personal productivity but has no backup guarantees and isn’t meant for production.

What we set up for most teams:

• Default renamed to something like “Personal Productivity” so nobody mistakes it for production.
• Developer or Sandbox environments for building and testing. Sandboxes support copy and reset.
• Production environments for apps the business depends on.

Important: Microsoft is retiring unmanaged developer environments (no new ones from November 15, 2026; existing ones suspended from December 15, 2026) and Dataverse for Teams environments (no new ones from November 15, 2026). Settings that differ per environment, such as URLs, belong in environment variables in Power Platform.

Step 2: Set Data Policies Before Makers Build

Data policies, which you’ll still hear called DLP policies, decide which connectors can be used together. You create them in the Power Platform admin center under Security > Data and privacy > Data policy.

• Business: connectors for company data, such as SharePoint, Outlook and Dataverse.
• Non-business: everything else; new connectors land here by default.
• Blocked: connectors nobody can use where the policy applies (some, like SharePoint, can’t be blocked).

An app or flow can’t mix Business and Non-business connectors. Policies usually take effect within an hour, but Microsoft says enforcement can take up to 24 hours in big tenants, so set them before people start building.

Step 3: Turn On Managed Environments for Important Work

Managed Environments is a set of premium governance features you switch on per environment. We use sharing limits, weekly usage insights, the solution checker and environment groups most.

It’s included with standalone Power Apps, Power Automate, Copilot Studio, Power Pages and Dynamics 365 licenses, so users running apps in a managed environment need one of those. Pipelines also deploy only to managed target environments.

Step 4: Package Work in Solutions and Deploy with Pipelines

A solution is the box that carries apps, flows, tables, agents and environment variables from development to test to production. Build inside a solution from day one; our post on the preferred solution in Power Platform shows how to make that the default.

Pipelines in Power Platform then move the solution for you. A maker opens the unmanaged solution in the development environment, selects Deploy, and the pipeline exports it once and imports it as a managed solution into each stage. Dataverse rows don’t travel with it; see our Dataverse solution walkthrough for what does.

Developers can script the same work with the Power Platform CLI (pac), which installs as a Visual Studio Code extension, a .NET tool or a Windows MSI:

pac auth create --environment "Power Platform"
pac solution list
pac solution export --name ServiceRequestApp --path .\ServiceRequestApp.zip --managed

The first command signs in to our “Power Platform” environment, the second lists its solutions, and the third exports a managed copy ready for import or source control.

Step 5: Watch Usage in the Power Platform Admin Center

For years the Center of Excellence (CoE) Starter Kit was the standard governance add-on. Microsoft no longer maintains it; its core features now live in the admin center as Inventory (every app, flow and agent), Usage, Monitor and Actions.

We check Inventory weekly for apps with no owner and Actions for recommendations such as apps shared with everyone.

How Power Platform Licensing Works (Without the Price List)

Licensing changes often, so check the Microsoft Power Platform Licensing Guide before you buy. There are four ways to get rights:

• Microsoft 365 use rights: many Microsoft 365 plans include limited Power Apps and Power Automate for Microsoft 365 data and standard connectors, like our SharePoint-based Service Desk Demo.
• Standalone licenses: Power Apps Premium and Power Automate Premium unlock premium connectors, Dataverse and Managed Environments. Copilot Studio and Power Pages have their own licensing, and so does Power BI (see Power BI Free vs Pro vs Premium).
• Pay-as-you-go: link an environment to an Azure subscription and pay per use through Azure meters.
• Capacity add-ons: extra Dataverse storage, AI Builder credits, Power Pages capacity and Copilot Credits.

Note: the Power Apps per app license stopped being sold to new customers in some purchasing channels on January 2, 2026, so don’t build a plan around it without checking with your licensing partner.

Power Platform Cheat Sheet

Piece	What it builds or does	Where you open it	Our example
Power Apps	Canvas and model-driven apps	make.powerapps.com	Service Desk Demo, SPGuides Service Request App
Power Automate	Cloud and desktop flows	make.powerautomate.com	Approval and notification flows on Service Requests
Power BI	Reports and dashboards	Power BI Desktop, app.powerbi.com	Open vs closed requests by priority
Copilot Studio	AI agents and agent flows	copilotstudio.microsoft.com	A help desk agent in Teams
Power Pages	External websites	make.powerpages.microsoft.com	A public request form
Dataverse	Shared database and security	Tables in make.powerapps.com	Service Request table
Admin center	Environments, data policies, Inventory	admin.powerplatform.microsoft.com	“Power Platform” developer environment
pac CLI	Scripted ALM and solutions	VS Code terminal, PowerShell	pac solution export

Common Mistakes to Avoid

• Building production apps in the Default environment. Everyone is a maker there and there’s no backup guarantee. Move important work to its own environment early.
• Skipping data policies. Without one, a flow can copy SharePoint data to any consumer service.
• Building outside a solution. Apps made in the default solution are painful to move later. Start inside a solution.
• Ignoring delegation on SharePoint. Our Service Desk Demo proved that non-delegable functions quietly stop at 500 rows by default.
• Treating the old CoE Starter Kit as current. It gets no fixes; use the admin center Inventory and Usage pages.

Is Power Platform Only for Citizen Developers?

No. Business users build most first apps, but Power Platform development scales to professional work: pro developers write PCF code components, custom connectors, plug-ins and Azure Functions, and they run ALM through the pac CLI, GitHub or Azure DevOps.

Whether low-code fits a project depends on its scale and complexity. We compare it honestly in Power Apps vs traditional development.

Next Steps

Pick one real problem, like a request list or an approval, and build it end to end. Our step-by-step guide to create a canvas app from a SharePoint list is the fastest way to see Power Apps, SharePoint and Power Automate work together in an afternoon.

When you’re ready to go deeper, we’d read these next:

• How to Create a Solution in Copilot Studio (Step-by-Step)
• Create an Agent Flow Using Designer in Copilot Studio
• How to Get Power Apps Environment ID
• Dataverse Dataflow: Copy a SharePoint List into Dataverse with Power Query

Frequently Asked Questions