Valid Ways to Share a Canvas App Power Apps
Which TWO are valid ways to share a canvas app with other users in your organization?
Quick Answer
Sharing a canvas app in Power Apps really only has two supported paths, and both are covered here: sharing directly from the Power Apps maker portal, which is the standard mechanism where an owner grants other users or security groups access and the app then appears in their Power Apps list, and embedding the app as a tab within Microsoft Teams, which surfaces that same shared app inside a channel or chat for easier day-to-day access. Both routes ultimately rely on the same underlying sharing and permission model, since Teams embedding doesn't bypass it, it just changes where users encounter the app. That's why options like publishing to a SharePoint list, sending a direct link to the .msapp file, or emailing the app as an attachment don't work: a canvas app isn't a standalone file that travels outside the platform, and none of those approaches touches the actual permission system that determines who can open the app. The .msapp file in particular is a build artifact used for import and export, not something a user can click to launch a live app. When a question offers you ways to share an app, favor answers that go through the platform's own sharing and permission mechanism and be suspicious of any option that treats the app like a portable file sent outside the system.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Share directly from the Power Apps maker portal
Option B is correct because the Power Apps maker portal provides a built-in Share feature that lets you grant specific users or groups in your organization access to a canvas app, assigning them either User or Co-owner permissions. Option C is correct because embedding a canvas app in Microsoft Teams is a supported sharing method that distributes the app to team members through a Teams tab or as a personal app, respecting the organization's security and licensing. Option A is not valid because a SharePoint list is a data source, not a distribution channel for a canvas app. Option D is not valid because a .msapp file is a source package for editing or importing in the maker portal, not a runnable link for end users. Option E is not valid because emailing the .msapp file does not publish or share the app and recipients cannot run it directly.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Publish the app to a SharePoint list
Why it's wrong here
SharePoint lists store data that canvas apps connect to; they are not an app distribution channel. Publishing to a list is tempting because Power Apps integrates with SharePoint, but sharing happens through the Power Apps sharing panel, which assigns users or groups access.
- ✓
Share directly from the Power Apps maker portal
Why this is correct
The maker portal's Share command grants named users or security groups permission to run the app, with optional co-owner rights. This is the standard in-tenant distribution mechanism, satisfying the requirement for a valid way to share a canvas app within the organisation.
- ✓
Embed the app in Microsoft Teams
Why this is correct
Publishing the app as a Teams tab or personal app distributes it through a channel members already use, and Entra ID authentication governs access. This satisfies the requirement for a valid in-organisation sharing method, since recipients need no separate portal navigation.
- ✗
Provide a direct link to the .msapp file
Why it's wrong here
A .msapp file is the source package opened in Power Apps Studio; recipients cannot run it as a shared app. It is tempting because the file does contain the app, but sharing requires granting access through Power Apps, not distributing the package.
- ✗
Send the app file as an email attachment
Why it's wrong here
Emailing the .msapp attachment delivers a source package, not a runnable app with permissions. It is tempting because the file represents the app, yet recipients still need Power Apps access granted via the sharing dialog, so the attachment alone grants nothing.
Go deeper
Related to this question
About these practice questions
This PL-900 question is part of Courseiva's 701-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on PL-900
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which TWO of the following are valid ways to share a canvas app with other users? (Choose TWO.)
medium- A.Share the app with a distribution group.
- B.Share the app with everyone in the organization by selecting 'Everyone' in the share settings.
- ✓ C.Share the app with a security group.
- D.Share the app with a Microsoft 365 group.
- ✓ E.Share the app with individual users by entering their email addresses.
Why C: Option C is correct because Power Apps allows you to share a canvas app with a security group, which is an Azure AD security group used to grant access to multiple users at once. Option E is correct because you can share a canvas app directly with individual users by entering their email addresses in the share pane. Option A is incorrect because distribution groups are mail-enabled groups that cannot be used for app sharing permissions in Power Apps. Option B is incorrect because there is no 'Everyone' option in the share settings; you cannot share an app with the entire organization in one action. Option D is incorrect because Microsoft 365 groups are not supported for sharing canvas apps; only security groups and individual users are valid.
Variation 2. Which TWO are valid ways to share a canvas app with other users in your organization? (Select two.)
medium- A.Send a direct link to the app via email before publishing
- ✓ B.Add users to a security group that has been granted access to the app
- ✓ C.Share the app directly with individual users or Microsoft Entra ID groups
- D.Generate a public URL that anyone in the organization can use
- E.Export the app as a .msapp file and email it to users
Why B: Option B is correct because in Power Apps you can grant access to a canvas app by sharing it with a Microsoft Entra ID security group, and then simply add or remove users from that group to manage access at scale. Option C is correct because the standard Share action in Power Apps lets you share a canvas app directly with individual users or with Microsoft Entra ID groups, assigning them either User or Co-owner permissions. Option A is not valid because a direct link only works after the app has been published and shared with the recipient; sending a link before publishing does not grant access. Option D is not valid because canvas apps do not support anonymous public URLs for anyone in the organization; access always requires explicit sharing with named users or groups. Option E is not valid because a .msapp file is a source package for import into another environment, not a distribution mechanism, and emailing it does not grant runtime access to the app.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PL-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-900 exam.