This chapter covers the Microsoft Power Platform, a suite of low-code/no-code tools for building apps, automating workflows, analyzing data, and creating chatbots. For the MS-900 exam, Power Platform appears in Domain 2: M365 Productivity, Objective 2.4 — about 10-15% of exam questions touch this topic. You need to understand the core components, their licensing, and how they integrate with Microsoft 365. We will break down each service, explain Dataverse, and highlight common exam traps.
Jump to a section
Imagine a factory that builds custom digital tools. The factory has four specialized assembly lines. The first assembly line, Power Apps, is like a prefabricated parts station: workers snap together pre-made components (connectors, screens, controls) to build custom applications without welding or machining from scratch. The second line, Power Automate, is like a conveyor belt system with programmable switches: when a package arrives (a trigger, like an email or a new database row), sensors detect it and automatically route the package through a series of actions (approvals, data entry, notifications) based on rules you set. The third line, Power BI, is like a quality control dashboard: it continuously collects data from every station, runs statistical analyses, and displays real-time charts and graphs so managers can spot bottlenecks and trends. The fourth line, Power Virtual Agents, is like an automated customer service kiosk: users type questions, and the kiosk uses a decision tree (built by you) to provide answers or escalate to a human. All four lines are connected by a common power supply — Microsoft Dataverse — which stores all the raw materials (data) and finished goods (configurations) in a centralized, secure warehouse. The factory floor manager (Power Platform admin center) controls who can access each line, monitors usage, and sets policies. This entire factory runs inside your Microsoft tenant, so it inherits security and compliance from your existing Microsoft 365 setup.
What is Microsoft Power Platform?
Microsoft Power Platform is a collection of four key products — Power Apps, Power Automate, Power BI, and Power Virtual Agents — plus a common data platform called Microsoft Dataverse. It enables users with little or no coding experience to build custom business solutions. The platform is designed to extend Microsoft 365, Dynamics 365, Azure, and third-party services.
Power Apps
Power Apps is a low-code application development environment. It allows you to create custom apps that run on web, mobile, and tablet. There are two main types: canvas apps and model-driven apps. Canvas apps start with a blank canvas where you drag and drop controls (buttons, forms, galleries) and connect to data sources. Model-driven apps start from your data model in Dataverse and automatically generate a responsive app with forms, views, and dashboards. Power Apps has connectors to hundreds of data sources, including SharePoint, Excel, SQL Server, and Salesforce. Licensing: Power Apps per app plan (per user/app), Power Apps per user plan (unlimited apps for one user), or included with some Microsoft 365 and Dynamics 365 licenses.
Power Automate
Power Automate (formerly Microsoft Flow) is a workflow automation service. It lets you create automated processes between apps and services. Flows can be triggered by events (e.g., new email, new SharePoint item) and perform actions (e.g., send approval, update record). There are three main flow types: automated flows (triggered by an event), button flows (triggered manually), and scheduled flows (run on a schedule). Power Automate also includes robotic process automation (RPA) capabilities with desktop flows. Licensing: Power Automate per user plan (unlimited runs), per flow plan (high-volume), or included with some Microsoft 365 licenses (limited runs).
Power BI
Power BI is a business analytics service. It provides interactive visualizations and business intelligence capabilities. You can create reports and dashboards from multiple data sources. Power BI Desktop is a free authoring tool; Power BI Service is the cloud-based sharing and collaboration platform. Power BI Premium offers dedicated capacity for larger deployments. Licensing: Power BI Pro (per user, share and collaborate), Power BI Premium Per User (more capacity), Power BI Premium (dedicated capacity).
Power Virtual Agents
Power Virtual Agents is a chatbot service. It allows you to create intelligent chatbots without coding, using a graphical interface. You define topics (conversation paths) and trigger phrases. The chatbot can be published to websites, Microsoft Teams, and other channels. It uses natural language understanding (NLU) to interpret user queries. Licensing: Power Virtual Agents standalone (per user/month with limited sessions) or included with some Microsoft 365 licenses (e.g., Office 365 E3/E5 have limited capacity).
Microsoft Dataverse
Dataverse is the underlying data platform for Power Apps, Power Automate, and Power Virtual Agents. It stores data in tables (similar to database tables) with relationships, business rules, and security. Dataverse replaces the earlier Common Data Service (CDS). It provides a standardized schema and supports rich data types (text, numbers, images, files). Dataverse also includes built-in security with role-based access control (RBAC) and field-level security. Data can be accessed via APIs and connectors. Licensing: Dataverse storage is included with Power Apps and Power Automate licenses, with additional storage available for purchase.
Integration with Microsoft 365
Power Platform deeply integrates with Microsoft 365. For example, you can build a Power App that uses SharePoint lists as a data source, or create a Power Automate flow that sends an email via Outlook when a Teams message is posted. Power BI can pull data from Excel Online or SharePoint. Power Virtual Agents can be embedded in Teams. The Power Platform admin center allows centralized management of environments, data loss prevention (DLP) policies, and licensing.
Environments
Environments are containers that separate apps, flows, and data. Each environment has its own Dataverse database. You can have multiple environments for development, testing, and production. Environments are created and managed in the Power Platform admin center. Default environments include a Microsoft Dataverse environment for each tenant.
Connectors
Connectors are wrappers around APIs that allow Power Apps and Power Automate to interact with services. There are hundreds of connectors: standard (included with licenses), premium (require additional licenses), and custom (built by developers). Examples: Office 365 Outlook, SharePoint, SQL Server, Salesforce, Twitter.
AI Builder
AI Builder is a capability within Power Platform that lets you add AI models (e.g., form processing, object detection, text classification) to your apps and flows without coding. It uses prebuilt or custom models.
Licensing Summary
Power Apps per app: $5/user/app/month (or $10 for premium connectors)
Power Apps per user: $20/user/month (premium connectors included)
Power Automate per user: $15/user/month (unlimited flows)
Power Automate per flow: $500/flow/month (high volume)
Power BI Pro: $10/user/month
Power BI Premium Per User: $20/user/month
Power Virtual Agents: $1,000/month for 2,000 sessions (or included with some M365 plans)
Dataverse storage: 10 GB base included with Power Apps/Power Automate licenses; additional storage $5/GB/month
Verification Commands (PowerShell)
To manage Power Platform, you can use the Microsoft.PowerApps.Administration.PowerShell module:
# Install module
Install-Module -Name Microsoft.PowerApps.Administration.PowerShell
# Connect
Add-PowerAppsAccount
# List environments
Get-AdminPowerAppEnvironment
# Get licenses
Get-AdminPowerAppLicensesCommon Exam Traps
Confusing Power Apps canvas vs. model-driven apps (canvas: pixel-perfect control; model-driven: data-centric).
Thinking Power Automate is only for simple tasks (it can handle complex logic including conditions, loops, and parallel branches).
Assuming Dataverse is the same as SQL Server (Dataverse is a low-code platform with built-in security and business rules).
Forgetting that Power BI reports can be embedded in Power Apps (they can).
Misunderstanding licensing: some Microsoft 365 plans include limited Power Automate runs (e.g., 2,000/month) but not unlimited.
Create a Power App
1. Sign in to make.powerapps.com. 2. Select 'Create' from the left navigation. 3. Choose 'Canvas app' or 'Model-driven app'. 4. For canvas: select a template or start blank, then choose a data source (e.g., SharePoint list). 5. Drag controls (labels, text inputs, galleries) onto the canvas. 6. Bind controls to data fields using formulas (e.g., `Gallery1.Selected.Title`). 7. Set properties like OnSelect to navigate or submit data. 8. Save and publish. The app is now available in the Power Apps mobile app or web browser.
Build a Power Automate Flow
1. Go to flow.microsoft.com. 2. Select 'Create' and choose 'Automated cloud flow'. 3. Pick a trigger (e.g., 'When a new email arrives' from Outlook). 4. Add actions: e.g., 'Get item' from SharePoint, 'Send an approval' to a manager. 5. Configure each action: map fields from previous steps using dynamic content. 6. Add conditions (e.g., if priority is high, send email; else, skip). 7. Save and turn on the flow. The flow runs in real-time when the trigger occurs.
Create a Power BI Report
1. Open Power BI Desktop. 2. Get data from a source (e.g., Excel, SQL Server, SharePoint). 3. In the Query Editor, clean and transform data (remove columns, merge tables). 4. Close & Apply to load data. 5. Drag fields onto the report canvas to create visuals (bar chart, table, map). 6. Add slicers and filters for interactivity. 7. Publish to Power BI Service. 8. In the service, create dashboards by pinning visuals from reports. 9. Share dashboards with others by granting access.
Set up a Power Virtual Agent
1. Go to powervirtualagents.microsoft.com. 2. Create a new bot and give it a name. 3. The bot is automatically connected to a Dataverse environment. 4. Create topics: define trigger phrases (e.g., 'How do I reset my password?') and conversation flow (questions, responses). 5. Use entities to capture user input (e.g., email address). 6. Test the bot in the test pane. 7. Publish the bot to a channel (e.g., Teams, website). 8. Monitor analytics in the bot's dashboard.
Manage Environments in Admin Center
1. Go to admin.powerplatform.microsoft.com. 2. Select 'Environments' from the left menu. 3. Click 'New' to create an environment. 4. Choose a name, type (Production, Sandbox, Trial), and region. 5. Decide whether to create a Dataverse database (required for model-driven apps). 6. Set security group access. 7. Once created, you can assign permissions (Environment Admin, Environment Maker) to users. 8. Monitor storage usage and capacity in the 'Capacity' section. 9. Set data loss prevention (DLP) policies to control which connectors can be used together.
Enterprise Scenario 1: Travel Expense Reporting
A large enterprise with 5,000 employees uses an outdated paper-based expense reporting system. The IT department builds a Power Apps canvas app that connects to a SharePoint list for expense data. Employees submit expenses via the app on their phones. A Power Automate flow triggers when a new expense is submitted: it sends an approval request to the manager. If approved, the flow updates the SharePoint list and sends a confirmation email. Power BI pulls data from SharePoint to create a dashboard showing expense trends by department, helping finance identify overspending. The solution reduced processing time from 3 days to 2 hours. Common issues: users forgetting to grant connector permissions; flows failing due to throttling (Power Automate has limits of 100 calls per 5 minutes per user). To avoid throttling, the company uses a premium license with higher limits.
Enterprise Scenario 2: Customer Support Chatbot
A retail company with 200 support agents uses Power Virtual Agents to handle common queries like order status and returns. The bot is published on the company website and in Teams. The bot uses Dataverse to look up order details. If the bot cannot resolve the query, it escalates to a human agent via a Power Automate flow that creates a ticket in Dynamics 365. Power BI dashboards show bot performance metrics (resolution rate, average session duration). After deployment, 40% of queries were handled without human intervention, saving $500k annually. Challenges: training the bot with enough trigger phrases; handling ambiguous language; ensuring escalation works reliably. The admin regularly reviews analytics to improve topics.
Scenario 3: Sales Pipeline Management
A B2B software company uses a model-driven Power App built on Dataverse to manage leads and opportunities. The app includes business rules (e.g., automatically calculate expected revenue) and workflows (e.g., send email to sales rep when lead is assigned). Power Automate flows synchronize data between Dataverse and Salesforce using a premium connector. Power BI reports give executives real-time pipeline visibility. The solution replaced a custom .NET application, reducing maintenance costs by 60%. Performance considerations: Dataverse storage limits (10 GB base) required careful data archiving. Misconfiguration: if DLP policies block the Salesforce connector, the sync fails silently.
MS-900 Objective 2.4: Describe Microsoft Power Platform
This objective covers identifying the components (Power Apps, Power Automate, Power BI, Power Virtual Agents, Dataverse) and understanding their use cases. The exam expects you to know:
The difference between canvas and model-driven apps.
The three flow types: automated, button, scheduled.
That Power BI is for analytics, not app building.
That Power Virtual Agents creates chatbots.
That Dataverse is the common data service (not SharePoint).
Common Wrong Answers
'Power Automate is used to build mobile apps.' Wrong: Power Automate automates workflows, not builds apps. That's Power Apps.
'Power BI can create custom apps.' Wrong: Power BI is for reporting and dashboards. Custom apps come from Power Apps.
'Dataverse is the same as SharePoint.' Wrong: Dataverse is a structured database with relationships and business logic; SharePoint is document management.
'Power Virtual Agents requires coding.' Wrong: It is a low-code/no-code chatbot builder.
'All Microsoft 365 licenses include full Power Platform capabilities.' Wrong: Only some plans include limited usage; most require additional licenses.
Specific Numbers and Terms
Power Apps per app: $5/user/app/month (standard), $10 (premium connectors)
Power Automate per user: $15/user/month
Power BI Pro: $10/user/month
Power Virtual Agents: $1,000/month for 2,000 sessions
Dataverse storage: 10 GB included per tenant
Flow types: automated, button, scheduled
Environments: Production, Sandbox, Trial
Edge Cases
Power Automate flows can be triggered by Dataverse business events (not just external triggers).
Power Apps model-driven apps are automatically responsive; canvas apps require manual layout.
Power BI dashboards can be pinned from multiple reports.
Power Virtual Agents can use Power Automate flows to perform actions (e.g., update a record).
How to Eliminate Wrong Answers
If the question asks about building an app, eliminate Power Automate and Power BI.
If the question mentions workflow automation, choose Power Automate.
If the question mentions data analysis and visualization, choose Power BI.
If the question mentions chatbots, choose Power Virtual Agents.
If the question mentions a common data platform, choose Dataverse.
Look for keywords: 'trigger', 'action', 'approval' -> Power Automate; 'canvas', 'model-driven' -> Power Apps; 'dashboard', 'report' -> Power BI; 'topic', 'chatbot' -> Power Virtual Agents.
Power Platform consists of Power Apps, Power Automate, Power BI, Power Virtual Agents, and Dataverse.
Power Apps has two types: canvas apps (pixel-perfect) and model-driven apps (data-centric).
Power Automate flows are triggered by events (automated), manually (button), or on a schedule.
Power BI is for analytics and visualization, not app building.
Power Virtual Agents creates chatbots using a graphical interface without coding.
Dataverse is the underlying data platform with built-in security and business logic.
Licensing: Power Apps per app $5/user/app, Power Automate per user $15/user, Power BI Pro $10/user, Power Virtual Agents $1,000/month.
Environments separate development, test, and production; each has its own Dataverse database.
Connectors link Power Apps and Power Automate to external services; premium connectors require additional licenses.
AI Builder adds AI capabilities (form processing, object detection) to apps and flows.
These come up on the exam all the time. Here's how to tell them apart.
Canvas Apps
Start with a blank canvas; drag and drop controls.
Full control over layout and pixel-perfect design.
Can connect to many data sources (SharePoint, Excel, SQL).
Best for custom user interfaces and mobile apps.
Requires more manual effort for responsive design.
Model-Driven Apps
Start from data model (Dataverse); UI is generated automatically.
Responsive design by default; adapts to screen size.
Only works with Dataverse as the data source.
Best for data-centric apps with complex business logic.
Less control over layout; follows predefined forms and views.
Mistake
Power Automate is only for simple email notifications.
Correct
Power Automate can handle complex logic: conditions, loops, parallel branches, approvals, and even RPA via desktop flows. It can integrate with hundreds of services and perform data transformations.
Mistake
Power Apps requires coding in C# or JavaScript.
Correct
Power Apps uses a low-code formula language (Power Fx) similar to Excel. No traditional programming is required, though custom code can be added via connectors or custom controls.
Mistake
Power BI is just a charting tool like Excel charts.
Correct
Power BI is a full business intelligence platform with data modeling, DAX calculations, row-level security, and real-time streaming. It can combine multiple data sources into a single data model.
Mistake
Power Virtual Agents is the same as Microsoft Bot Framework.
Correct
Power Virtual Agents is a low-code chatbot builder with a graphical interface, while Bot Framework is a code-based SDK for developers. Power Virtual Agents abstracts away the code.
Mistake
Dataverse is just a database like SQL Server.
Correct
Dataverse includes built-in business logic (business rules, workflows), security (role-based access, field-level security), and a standardized schema. It is optimized for low-code apps and integrates deeply with Power Platform.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Canvas apps give you complete control over the user interface by dragging and dropping controls onto a blank canvas. They can connect to many data sources (SharePoint, Excel, SQL). Model-driven apps start from your data model in Dataverse and automatically generate a responsive UI with forms, views, and dashboards. They are best for data-centric applications with complex business logic. For the exam, remember: canvas = custom layout, model-driven = data-driven layout.
Microsoft 365 E5 includes Power Automate capabilities, but with limitations. E5 users get up to 2,000 Power Automate runs per month and can only use standard connectors. If you need unlimited runs or premium connectors (e.g., SQL Server, Salesforce), you need a standalone Power Automate per user license ($15/user/month). For the exam, know that some Microsoft 365 plans include limited Power Automate usage.
Yes. Power BI tiles and reports can be embedded inside Power Apps using the Power BI tile control (canvas apps) or by adding a Power BI dashboard to a model-driven app. This allows users to view analytics without leaving the app. For the exam, this is a common integration point.
Dataverse is the centralized data storage for Power Apps, Power Automate, and Power Virtual Agents. It provides a secure, structured database with relationships, business rules, and role-based security. It replaces the earlier Common Data Service (CDS). Data stored in Dataverse can be accessed by all Power Platform components and external systems via APIs.
Use Power Automate when you need to automate a workflow or process (e.g., send approval when a new item is added). Use Power Apps when you need a custom user interface for data entry or viewing (e.g., a mobile expense report form). Often, they are used together: a Power App triggers a Power Automate flow to process data. For the exam, match the scenario: workflow automation = Power Automate, custom app = Power Apps.
A free Microsoft account gives you 750 Power Automate runs per month. Microsoft 365 licenses (E1, E3, E5) include 2,000 runs per month. Standalone Power Automate per user plan has unlimited runs. For the exam, know that run limits vary by license.
Yes. Power Virtual Agents is a low-code/no-code chatbot builder. You create topics using a graphical interface: define trigger phrases, add questions and responses, and design the conversation flow. No coding is required, though you can extend functionality with Power Automate flows or Bot Framework code if needed.
You've just covered Microsoft Power Platform Overview — now see how well it sticks with free MS-900 practice questions. Full explanations included, no account needed.
Done with this chapter?