Microsoft put the sharing possibility of Power Apps with Guest users in preview. Okay, time to share created canvas apps with guest users. This give us the possibility to create PowerApps that are build with the intention to share data with external persons.
Let’s start by adding a guest user into the Azure Active Directory.
Default the usage location of a guest user is empty. When not filled in and the guest user has been added to the Power App. The guest user cannot open the Power App via the receive link in the e-mail. So don’t forget this to change to the correct usage location!
As administrator go to the canvas app that you would like to share with your guest user. Click on Share.
Search for the guest user and click share. The guest user will be notified by e-mail that access is given to a specific canvas app.
E-mail that will be sent to the guest user.
Guest user can click “Open the app >” and use the canvas app.
Which License you use for a guest user?
During the test the guest user had a Office 365 E3 license, including the Office 365 PowerApps/Flow apps. But I did also the test with a Microsoft enabled account without Office 365 license and had no license assigned in Azure Active Directory. Even this guest user cloud access the canvas app, after he was added to the shared user list.
It’s a great opportunity to have the possibility to create canvas apps in your organisation that can be used by people outside your organisation. I have already my first canvas app, shared with our first customer. How cool is that!
- Share apps with users outside your tenant using ADD B2B or B2C
- Share an app with guest as easily as you do with co-worker
- Guest can run cnavas apps that are embedded in SharePoint lists
- Guest can access apps in both browser and mobile clients
License – update 01/10/2019:
PowerApps and Flow service can only be accessed if you have a PowerApps or Flow license. Similarly, PowerApps and Flow licenses are required for users that input data into, query, or view data from the PowerApps and Flow apps through a pooling device. Pooled connections use a non-interactive user account in PowerApps and Flow that can access the system but only via the web service layer. Internal users accessing PowerApps and Flow service indirectly through a portal or via an API to a separate service such Microsoft Outlook must also be properly licensed, regardless of if they are set up as a PowerApps and Flow user in the app, for example:
- Internal users that access the PowerApps and Flow service must still be properly licensed for PowerApps and Flow.
- Any user that accesses PowerApps and Flow service that is made available through an automated process requires a PowerApps and Flow license.
- The number of tiers of hardware or software between the PowerApps and Flow apps and the user or devices that ultimately use PowerApps and Flow service indirectly does not affect the number of SLs required.