Power Platform Components for SharePoint and External Access

PL-600 By islever Editorial Last updated

Short answer

BD Use a Canvas app for internal employees to interact with the SharePoint list and Power Pages to provide view access for external customers.

Question

You are designing a Microsoft Power Platform solution for a customer. The customer is developing an application that needs to use an existing Microsoft SharePoint list. The application must be able to: • allow view access for external customers. • use out-of-the-box processes for access for employees. You need to recommend components for the application. Which two components should you recommend? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.
  1. Custom pages
  2. Canvas app Correct Answer
  3. Model-driven app
  4. Power Pages Correct Answer

Key Takeaways

The core trap is confusing Model-driven apps (which require Dataverse) with Canvas apps (which can connect directly to SharePoint). Additionally, recognizing Power Pages as the dedicated portal solution for external users is critical.

This question evaluates the selection of appropriate Power Platform components to integrate with SharePoint lists while supporting both internal employees and external customers. The solution requires a canvas app for internal data manipulation and Power Pages for secure external viewing.

Common mistake: Many candidates choose Option C (Model-driven app) because it handles business processes well, but they fail to realize that Model-driven apps are built on Dataverse and do not natively support direct SharePoint list integration without complex workarounds.

Expert Analysis

Why the Answer Is Correct

The correct components are Canvas App (B) and Power Pages (D). A Canvas app is ideal for connecting directly to existing data sources like SharePoint lists, allowing custom UI design for employee workflows. Power Pages is Microsoft's dedicated low-code portal solution designed specifically for providing secure web access to external users (customers) who do not have Microsoft Entra ID licenses.

Why the Other Options Are Wrong

Option A (Custom pages) are sub-components within Model-driven apps, not standalone solutions for this scenario. Option C (Model-driven app) is incorrect because it relies on the Dataverse platform; it cannot directly consume a SharePoint list as its primary data source in the way required here, making it unsuitable for an existing SharePoint-based architecture.

Community Comment Notes

Community consensus heavily favored BD, with several users noting that "If your data source is a SP List, then you need a canvas app" due to the lack of native Dataverse support in SharePoint lists. Others highlighted that Power Pages is the obvious choice for external access, reinforcing the split between internal (Canvas) and external (Power Pages) needs.

Exam Strategy

Always check the underlying data model first. If the requirement mentions 'existing SharePoint' or 'Excel', think Canvas Apps. If it mentions 'Dataverse' or 'built-in security models', think Model-driven Apps. For external portals, Power Pages is the standard answer.

Frequently Asked Questions

Why can't I use a Model-driven app with SharePoint?

Model-driven apps are built on Dataverse. While connectors exist, they are not native to the same degree as Canvas apps, and SharePoint is not a supported primary data source for Model-driven app creation.

Is Power Pages free for external users?

No, Power Pages requires specific licensing for external visitors. It is distinct from standard Power Apps which rely on user-specific licenses.

More PL-600 FAQ →

Community Votes

BD
67%
CD
33%

67% of anonymous learners picked answer BD. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 7 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 7

  1. OscarAdriani 👍 2
    Here's why the other options are not as suitable: A. Custom pages: Custom pages are components within model-driven apps. While they offer some customization, they are primarily intended for use within the context of a model-driven app and are not ideal for providing external access to a SharePoint list. C. Model-driven app: Model-driven apps are built on top of Dataverse and are primarily designed for internal users within an organization. While you could technically expose a model-driven app externally, it's not the recommended approach, especially for simply providing view access to a SharePoint list. Managing external user access and licensing for a model-driven app would be more complex than using Power Pages.
  2. d6ff68f 👍 2
    Even if you put an Iframe in the model driven app it's not the best approach to include SharePoint data, so Canvas App it's my choice. BD
  3. uberlord 👍 2
    external customer acces:portal using existing processes: model driven (BPF)
  4. No_Doubt 👍 2
    1- External users: D. Power Pages 2- Employees: C. Model-driven app
  5. ziggy1117 👍 1
    If your data source is a SP List, then you need a canvas app. We cannot use a model-driven app because there is no dataverse. Power Pages is obv the answer for external view access
Show 2 more comments
  1. iraelena 👍 1
    external: Power Pages employees - internal, oob processes: model driven
  2. loftuscheek 👍 1
    B. Canvas app D. Power Pages

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Selecting Power Apps vs Dynamics 365 for Custom Home Building

S-grade

Power Platform ALM Tool for Multiple Assets

S-grade

Dataverse Security Strategy for Departmental Apps

S-grade

Identifying Functional Requirements for Microsoft Power Pages

S-grade

← Back to PL-600 Study Guide