Share a canvas app in Power Apps

After you build a canvas app that addresses a business need, specify which users in your organization can run the app and which can modify and even reshare it. Specify each user by name, or specify a security group in Azure Active Directory. If everyone would benefit from your app, specify that your entire organization can run it.


For a shared app to function as you expect, you must also manage permissions for the data source or sources on which the app is based, such as Microsoft Dataverse or Excel. You might also need to share other resources on which the app depends, such as flows, gateways, or connections.


Before you share an app, you must save it to the cloud (not locally) and then publish the app.

  • Give your app a meaningful name and a clear description, so that people know what your app does and they can easily find it in a list. On the File menu in Power Apps Studio, select App settings, specify a name, and then type or paste a description.

  • Whenever you make changes, you must save and publish the app again if you want others to see those changes.

Share an app

  1. Sign in to Power Apps.

  2. Select Apps from the left pane.

    Show list of apps

  3. Select the app that you want to share by selecting its icon.

    Select an app

  4. Select Share from the top menu. You can also select More Commands (...) and then select Share from the drop-down menu:

    Share an app

  5. Specify by name or alias the users or security groups in Azure Active Directory with which you want to share the app.

    • To allow your entire organization to run the app (but not modify or share it), type Everyone in the sharing panel.

      Search Everyone

    • You can share an app with a list of aliases, friendly names, or a combination of those (for example, Meghan Holmes <>) if the items are separated by semi-colons. If more than one person has the same name but different aliases, the first person found will be added to the list. A tooltip appears if a name or alias already has permission or can't be resolved.

      Individual user


    You can't share an app with a distribution group in your organization or with a group outside your organization.

  6. If you want to allow the users to edit and share the app, select the Co-owner check box.

    Select a co-owner

    You can't grant Co-owner permission to a security group if you created the app from within a solution.


    Regardless of permissions, no two people can edit an app at the same time. If one person opens the app for editing, other people can run it but not edit it.

  7. If your app connects to data for which users need access permissions, specify them.

    For example, your app might connect to an entity in a Dataverse database. When you share such an app, the sharing panel prompts you to manage security for that entity.

    Assign a security role

    For more information about managing security for an entity, go to Manage entity permissions.

    If your app uses connection to other data sources such as an Excel file hosted on OneDrive for Business, ensure you share such data source with users that you share app with.

    Share Excel on OneDrive for Business

    For more information about sharing canvas app resources and connections, go to share canvas app resources.

  8. If you want to help people find your app, select the Send an email invitation to new users check box.

    Send email invitation

  9. At the bottom of the share panel, select Share.

    Users can now run the app using Power Apps Mobile on a mobile device. Or, from AppSource on Dynamics 365 in a browser. Co-owners can edit and share the app in Power Apps.

    If you sent an email invitation, users can also run the app by selecting the link in the invitation email.

    • If a user selects the link on a mobile device, the app opens in Power Apps Mobile.
    • If a user selects the link on a desktop computer, the app opens in a browser.

    Co-owners who receive an invitation get another link that opens the app for editing in Power Apps Studio.

To change permissions for a user or a security group:

  • To allow co-owners to run the app but no longer edit or share it, clear the Co-owner check box.
  • To stop sharing the app with that user or group, select the Remove (x) icon.

Security-group considerations

  • All existing members of the security group inherit the app permissions. New users joining the security group will inherit the security group permissions on the app. Users leaving the group will no longer have access through that group. Users may continue to have permissions either directly, or through membership of another security group.

  • Every member of a security group has the same permission for an app as the overall group does. However, you can specify greater permissions for one or more members of that group to allow them greater access. For example, you can give Security Group A permission to run an app. And then, you can also give User B, who belongs to that group, Co-owner permission. Every member of the security group can run the app, but only User B can edit it. If you give Security Group A Co-owner permission and User B permission to run the app, that user can still edit the app.

Share an app with Microsoft 365 Groups

You can share an app with Microsoft 365 groups. However, the group must be security enabled. Enabling security ensures the Microsoft 365 group can receive security tokens for authentication to access apps or resources.

Follow these steps to check if an Microsoft 365 group has security enabled:

  1. Ensure you have access to the Azure AD cmdlets.

  2. Go to Azure portal > Azure Active Directory > Groups > Select the appropriate group > Copy the Object Id.

  3. Connect to Azure AD using PowerShell:


  4. Get the group details using Get-AzureADGroup -ObjectId <ObjectID\> | select *.
    In the output, ensure the property SecurityEnabled is set to True:

    Check SecurityEnabled property

If the group isn't security enabled, you can enable it using PowerShell cmdlet Set-AzureADGroup by setting the SecurityEnabled property to True:

Set-AzureADGroup -ObjectId <ObjectID> -SecurityEnabled $True

Set SecurityEnabled to True


You must be the owner of the Microsoft 365 group to enable security. Setting SecurityEnabled property to true does not affect how Power Apps and Microsoft 365 features work. This command is required as SecurityEnabled property is set to false by default when creating Microsoft 365 Groups outside of Azure AD.

After a while, you can discover this group in the Power Apps sharing panel and share apps with this group.

Manage entity permissions


If you create an app based on Dataverse, you must also ensure that the users that you share the app with have the appropriate permissions for the entity or entities used by the app. Particularly, those users must belong to a security role that can do tasks such as creating, reading, writing, and deleting relevant records. In many cases, you'll want to create one or more custom security roles with the exact permissions that users need to run the app. You can then assign a role to each user as appropriate.


  • You can assign security roles to individual users and security groups in Azure AD but not to Office groups.
  • The user must also be in the Dataverse root business unit. If the user is not in the root business unit, you can share the app without providing a security role, and then set the security role directly.


To assign a role, you must have System administrator permissions for a Dataverse database.

Assign a security group in Azure AD to a role

  1. In the sharing panel, select Assign a security role under Data permissions.

  2. Select the Dataverse role(s) that you want to apply to the selected Azure AD user(s) or group(s):

    Security role list

Dataverse (previous version)

When you share an app that's based on an older version of Dataverse, you must share the runtime permission to the service separately. If you don’t have permission to do this, see your environment administrator.

Share with guests

Power Apps canvas apps can be shared with guest users of an Azure Active Directory tenant. This enables inviting external business partners, contractors, and third parties to run your company’s canvas apps.



  • In Azure Active Directory (Azure AD), enable B2B external collaboration for the tenant. More information: Enable B2B external collaboration and manage who can invite guests

  • Access to an account that can add guest users to an Azure AD tenant. Admins and users with the Guest Inviter role can add guests to a tenant.

  • The guest user must have a license with Power Apps use rights that matches the capability of the app assigned through one of the following tenants:

    • The tenant hosting the app being shared.
    • The home tenant of the guest user.


Power Apps Per App Plans are scoped to apps in a specific environment, so they cannot be recognized across tenants. Power Apps included with Office and Power Apps Per User Plans are not bound to a specific environment so they are recognized across tenants in guest scenarios.

Steps to grant guest access

  1. Select New guest user to add guest users in Azure AD. More information: Quickstart: Add a new guest user in Azure AD.

    Add guest in Azure AD

  2. If the guest user doesn't already have a license in their home tenant, assign a license to the guest user.


    You may need to disable the Microsoft 365 admin center preview to assign a license to a guest.

  3. Share the canvas app.

    1. Sign in to Power Apps.

    2. Select Apps from the left pane.

    3. Select a canvas app.

    4. Select Share from the command bar.

    5. Enter an email address for a guest user from an Azure AD tenant. More information: What is guest user access in Azure AD B2B?

      Share with guest

After you share an app for guest access, guests can discover and access apps shared with them from the email sent to them as part of sharing. You can also share the app URL directly with the guest instead. To find the URL, go to Power Apps, select Apps from left pane, select an app, and then select the Details tab. The app URL is displayed under Web link.

Guests receive app share email

Frequently Asked Questions

What’s the difference between canvas app guest access and Power Apps portals?

Canvas apps enable building an app, tailored to digitizing business processes, without writing code in a traditional programming language such as C#. Guest access for canvas apps enables teams of individuals made up of different organizations participating in a common business process to access the same app resources that may be integrated with a wide variety of Microsoft and third-party sources. More information: Overview of canvas-app connectors for Power Apps.

Power Apps portals provide the ability to build low-code, responsive websites that allow external users to interact with the data stored in Dataverse. It allows organizations to create websites that can be shared with users external to their organization either anonymously or through the login provider of their choice, such as LinkedIn, Microsoft Account, or other commercial login providers.

The following table outlines a few core capability differences between Power Apps portals and canvas apps.

Portals or canvas apps Interface Authentication Accessible data sources
Power Apps portals Browser only experience Allows anonymous and authenticated access Dataverse
Canvas apps Browser and mobile apps Requires authentication via Azure AD Any ~150 out-of-box connectors and any custom connector

Can guests access customized forms in SharePoint?

Yes. Any user that can access a SharePoint list with a customized form can create and edit items in the list, using the form. As long as the custom form only uses standard connectors, the guest isn't required to have any Power Apps license.

Why is a guest accessing a customized form in SharePoint prompted for a trial?

If the custom form uses a premium connector, a guest must have a Power Apps license to access the custom form. If the custom form only uses standard connectors, your tenant must allow Power Platform internal consent plans to be assigned to users. For more details about Power Platform internal consent plans, read block trial license commands.

Can guests access apps embedded in SharePoint?

Yes. Though, access to canvas standalone apps require a license with Power Apps user rights that matches the capability of the app; including embedded apps. When embedding a canvas app in SharePoint using the Microsoft Power Apps embed control, enter the app id. To do this, enter the app ID in the App web link or ID box.

Embed canvas app in SharePoint for guests

When embedding a canvas app in SharePoint via the iFrame HTML tag, reference the app using the full web URL. To find the URL, sign in to Power Apps, select an app, select the Details tab, and the URL is displayed under Web link.

Canvas app details

How come guests can launch the app shared with them but connections fail to be created?

As with non-guests, the underlying data source(s) accessed by the app must also be made accessible to the guest.

What license must be assigned to my guest so they can run an app shared with them?

The same license that’s required for non-guests to run an app. For instance, if the app uses premium connectors, then a Power Apps Per App Plan or a Power Apps Per User Plan must be assigned to the guest.

Plan SharePoint customized form Standalone canvas app using non-premium connectors Standalone canvas app using premium connectors Model driven app
SharePoint user (no PA license) x
Power Apps Included w/ Office x x
Power Apps Per App Plan x x x x
Power Apps Per User Plan x x x x

More details around pricing and capabilities of various plans can be found in Microsoft Power Apps and Power Automate Licensing Guide.

In Power Apps Mobile, how does a guest see apps for their home tenant?

Any user that has accessed a canvas app, on their mobile device, that’s published in an Azure AD tenant that isn’t their home tenant must sign out of Power Apps and sign back in to Power Apps Mobile.

In Power Apps Mobile, how does a guest see apps in the guest tenant?

As the guest user, open the email received when an app in the guest tenant was shared, and select the Open the app button. This applies to both Azure Active Directory and Microsoft Account users.

Must a guest accept the Azure AD guest invitation before sharing an app with the guest?

No. If a guest launches an app shared with them before accepting a guest invitation, the guest will be prompted to accept the invitation as part of the sign-in experience while launching the app.

What Azure AD tenant are connections for a guest user created in?

Connections for an app are always made in the context of the Azure AD tenant the app is associated. For example, if an app is created in the Contoso tenant, the connections made for Contoso internal and guest users are in the context of the Contoso tenant.

Can guests use Microsoft Graph via Microsoft Security Graph connector or a custom connector using Microsoft Graph APIs?

No, Azure AD guests can't query Microsoft Graph to retrieve information for a tenant in which they’re a guest.

What Intune policies apply to guests using my Power Apps?

Intune only applies policies of a user’s home tenant. For instance, if shares an app with, Intune continues to apply policies on Wanda’s device regardless of the apps Wanda runs.

What connectors support guest access?

All connectors that don't use Azure AD authentication of any type supports guest access. The following table enumerates all connectors that use Azure AD authentication and which connectors currently support guest access. More information: List of all Power Apps connectors

Connector Supports guest access
10to8 Appointment Scheduling No
Adobe Creative Cloud No
Adobe Sign No
Asana No
AtBot Admin No
AtBot Logic No
Azure AD Yes
Azure Automation Yes
Azure Container Instance Yes
Azure Data Factory Yes
Azure Data Lake Yes
Azure DevOps No
Azure Event Grid No
Azure IoT Central Yes
Azure Key Vault No
Azure Kusto Yes
Azure Log Analytics Yes
Azure Resource Manager Yes
Basecamp 2 No
Bitbucket No
Bitly No
bttn No
Buffer No
Business Central No
CandidateZip No
Capsule CRM No
Cloud PKI Management No
Cognito Forms No
Commmon Data Service Yes*
Common Data Service (Legacy) No
D&B Optimizer No
Derdack SIGNL4 No
Disqus No
Document Merge No
Dynamics 365 No
Dynamics 365 AI for Sales Yes
Dynamics 365 for Fin & Ops No
Enadoc No
Eventbrite No
Excel Online (Business) No
Excel Online (OneDrive) No
Expiration Reminder No
FreshBooks No
GoToMeeting No
GoToTraining No
GoToWebinar No
Harvest No
HTTP with Azure AD No
Infusionsoft No
Inoreader No
Intercom No
JotForm No
kintone No
LinkedIn No
Marketing Content Hub No
Medium No
Metatask No
Microsoft Forms No
Microsoft Forms Pro No
Microsoft Graph Security No
Microsoft Kaizala No
Microsoft School Data Sync No
Microsoft StaffHub No
Microsoft Teams Yes
Microsoft To-Do (Business) No
Muhimbi PDF No
NetDocuments No
Office 365 Groups Yes
Office 365 Outlook No
Office 365 Users Yes
Office 365 Video No
OneDrive No
OneDrive for Business No
OneNote (Business) No
Outlook Customer Manager No
Outlook Tasks Yes No
Paylocity No
Planner No
Plumsail Forms No
Power Apps for Admins No
Power Apps for Makers No
Power Automate Management No
Power BI Yes
Power Platform for Admins No
Project Online No
ProjectWise Design Integration No
Projectwise Share No
SharePoint Yes
SignNow No
Skype for Business Online No
Soft1 No
Stormboard No
Survey123 No
SurveyMonkey No
Toodledo No
Typeform No
Vimeo No
Webex Teams No
Windows Defender Advanced Threat Protection (ATP) No
Word Online (Business) No

* When using the Common Data Service connector, ensure the guest user is licensed from the same tenant where you have Dataverse located.

See also