PL-900 — frequently asked questions

The Excel connector enables access, but the step that writes the row is an Action. Microsoft Learn states to use the Write to Excel worksheet action.

It requires an Action, such as a Condition, because the flow must evaluate the email's priority as a logical step. A Connector is not the component performing the check.

AppSource lists Power BI add-ins, custom visuals, and template apps for feature gaps, and its Consulting Services directory lets you evaluate partner companies for a proof-of-concept.

No. Azure Marketplace is for discovering and deploying cloud software solutions; partner consulting discovery is an AppSource function.

The app canvas only exposes runtime functionality to users; Microsoft support requests are tenant-level admin tasks, so they are created from the Power Platform admin center's Help + support area.

It handles Microsoft 365 service requests, but Power Platform app and environment issues are routed through the Power Platform admin center, where the affected environment is visible.

Flow Checker only validates Power Automate cloud flows, so it cannot inspect canvas app screens, control labels, or screen reader properties.

No. It lists each issue with an explanation of who it affects and a suggested fix, but you must apply the changes yourself in Power Apps Studio.

No. Cloud flows rely on API or connector data; reading a rendered website UI requires a desktop flow’s RPA browser actions.

A scheduled cloud flow can run every Friday and trigger the desktop flow, which opens the site, reads vendors, and passes data for the email.

A dashboard is a single-page canvas whose tiles can be pinned from several different reports and datasets, which is what the KPI requirement describes. A report page shows multiple visuals but only from its own single dataset.

No. Line charts are authored in a report (or generated with Q&A) and then pinned to the dashboard as a tile. PL-900 therefore expects Report for the line-chart requirement.

Business process flows only guide users through predefined stages in a model-driven app; they cannot send SMS messages or run unattended on a schedule.

An automated cloud flow starts from an event trigger like a record being created, while a scheduled cloud flow starts at a specific date and time you define.

No. Prebuilt models are trained by Microsoft and are read-only, so your own samples cannot improve them. To use company-specific content, build and train a custom model instead.

A custom model trained on your own labeled data, such as custom document processing or custom prediction, then consumed in Power Apps or Power Automate.

It requires an existing data source to generate the app; the scenario states the company has no existing data, so it cannot demonstrate natural-language app and data-model creation.

No, AI Builder builds AI models such as form processing or prediction; it does not generate an app or Dataverse table structure from natural language.

Power BI reports are read-only analytics over data; they can display order status but cannot edit SharePoint items, so they fail the mobile update requirement.

Yes. Canvas apps connect natively to SharePoint lists, letting makers design phone screens that browse, create, and update order records in the same list.

Out of the box, Power Pages lists and forms are Dataverse-backed, so SharePoint data would need a cloud flow or custom integration. That is why Dataverse is the expected PL-900 answer here.

Power Pages cannot bind its native forms and lists to an Excel workbook, and Excel has no row-level security model for external customers. Dataverse is the platform's built-in site data source.

Yes. Canvas apps and Power Automate flows read and write list items through the standard SharePoint connector, and this list-backed pattern remains a supported, common build approach.

No. Microsoft Dataverse is the native, enterprise-grade data service with role-based security; SharePoint lists are a supported external data source, not the default store.

Co-owner can edit, delete, and share the flow, while Run-only can only execute the flow but cannot modify its logic or settings.

You can share the flow by adding the user as a co-owner for full access or granting run-only access if they only need to trigger it.

Setting Importance to High on the 'When a new email arrives' trigger pre-filters mail, but a Condition makes the 'priority equals High' decision explicit before the Excel write.

Yes. The Outlook and Excel Online (Business) connectors are standard, so the seeded Power Automate license included with Microsoft 365 covers this flow.

A workspace is a collaborative area where creators build and manage reports, datasets, and dashboards. An app is a bundled, curated collection of content published from a workspace, designed for consumers to view without accessing the underlying data or editing tools.

Yes. When publishing an app, you can assign it to specific security groups or users within your organization. This ensures that only authorized individuals can access the distributed content.

No. Power BI is for analytics and visualization. Dataverse is the underlying data platform for storing and managing application data. While Power BI can read from SQL, it doesn't serve as the persistent storage layer for the app's logic.

Yes, Power Automate has built-in 'Approval' actions that can route requests to specific users, such as sales managers, and pause the flow until a decision is made.

Yes. When you create a new environment, you can choose whether to enable Dataverse. This is useful for hosting simple canvas apps that connect only to external data sources like SharePoint or Excel.

No. Connections and data sources are scoped to the environment where the app resides. You must configure separate connections within each environment to access external data.

Power Apps is used to build internal or external apps for users to interact with data via forms and dashboards. Power Pages is specifically for building external-facing, professional websites that allow public or partner access to data.

Yes, but only basic business rules like field validation and formatting. Complex logic that spans multiple systems or requires triggering actions based on events is handled by Power Automate.

Dataverse stores data in Microsoft's cloud. The requirement explicitly states that all data must remain within the ERP application due to privacy concerns, so using Dataverse would violate data residency rules.

You typically need the SQL Server connector, potentially configured with an On-premises Data Gateway if the ERP is behind a firewall, allowing Power Apps to securely access the local database.

Yes, Power BI embeds into Teams allowing users to view reports. Depending on the workspace sharing settings, viewers may not require a full Pro license if shared via Teams tabs, though specific governance applies.

Dataverse is the native, secure data platform for Power Apps. While SharePoint works, Dataverse is preferred when the requirement specifies 'hosting' apps with their own dedicated, relational data store managed by the platform.

Power Apps creates the user interface (UI) for humans to interact with SharePoint data. Power Automate handles the backend logic and automation triggers. The question asks for an 'interface,' pointing to Power Apps.

No. Business Rules apply logic and automation within a single table or form. To associate records across different tables, you must use a Relationship.

You can use Table Permissions, Security Roles, or Client-Side scripts. The question focuses on the data model structure, which is handled by Relationships.