Can I require AAD authorization to limit who can see a Power App?

[aec2018]

I need to build an internal proof of concept that is going to need AAD authorization since we'll be showing sensitive data. From the documentation that I'm seeing, I keep getting pointed to a Power Apps Portals. Can I build something with Power Apps that will require users to sign in and block the app off to unauthorized users? Can I build a blank canvas app that can only be accessed by going through a Power Apps Portal? Thanks!

[BCLS776 · Accepted solution]

By controlling to whom an app and underlying data sources are shared, you effectively use AAD's authentication to control access. If an app is not shared with a user, they will not be able to access it.

Is that the kind of access control you are after?

[aec2018]

When you say shared, do you mean just having a link the app? My hope is that if any person somehow got a link to the Power App, they would get a not authorized page. So I'm guessing this would be based on Security Groups. Would I then need a log in experience at all or it would just be handled by virtue of being part of an SG or not?

[BCLS776]

By "Shared" I mean users/groups who explicitly have the app shared with them through Power Apps:

Any user who attempts to access an app through a link (in Teams or through a browser, for example) will not be able to run the app unless it has been shared with them or one of their M365 Groups. In addition, if underlying data sources are not shared, the user will encounter an error upon trying to start the app.