Power Platform access by guest users: unexpected behavior

[Korni1]

In our organization we wanted to try the guest sharing functionality in PowerApps and Flow, as described in the following article:

https://powerapps.microsoft.com/en-us/blog/share-canvas-apps-with-guests-in-your-organization/

But what we encountered a different behavior as expected, while sharing Apps to guest in our tenant.

Here is a description of our test:

1. We added the account to our Active Directory QA Enviroment.
2. Then we searched for the user in the sharing functionality of the specific PowerApps (QA tenant) as the original creator of the App.
3. We launched the hyperlink as the guest user.  
4. After authentication, we waited for few seconds for the login.

• The background color of the app was displayed for few seconds. Afterwards we received the folowing error message.

So since opening the very same App was possible with multiple other accounts on the same tenant. The App seems not to be broken, rather it seems to be there is an issue with the guest access or licensing.

Our first request here would be:

If the user did not have rights to open the app, an according error message shall be displayed.

We tested all this with different Accounts on different tenants with and without a license.

We are guessing here, but it seems like each guest needs to have a Microsoft tenant with a PowerApps and Flow license to access any other PowerApps and Flow in any other tenant, where he might be a guest.
In our opinion this limits any kind of collaboration planned with our customer, since we can’t expect guest to have a Microsoft tenant or even Licenses for PowerApps and Flow.  

So, is this guess correct? That means a guest needs to have a valid license on their own tenant?
Is this the expected behavior, in your point of view?

[MikSCaT]

You can try this workaround to access an app with external user on Power Apps mobile app. 

https://mvidal365.com/index.php/2020/11/21/acceder-a-power-apps-con-cuentas-personales/

[abeldjilali]

Thank you for the tip 🙂