Answered

Who can access connections?

(0) Share

Report

Posted on by Cooper01

664

If I create a connection, is there any level of user who can access that connection (like a system admin for example)? I know that some connections are implicitly shared via Power Apps. I am trying to understand what else I would need to be aware of, if anything, when creating connections that allow access to sensitive data.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (1)

AhmedSalih 6,680 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hello, @Cooper01 , this is a very broad topic, I would recommend that you start here:
https://docs.microsoft.com/en-us/power-apps/maker/data-platform/create-connection-reference
And then, here:
https://docs.microsoft.com/en-us/power-apps/maker/canvas-apps/connections-list#security-and-types-of-authentication

Then, if you have any specific use case, let me know.

Regards,

Ahmed

If my reply helped you, please give a 👍. And if it has solved your issue, please consider a 👍 & Accepting it as the Solution to help other members of the community find it more.
My Blog: www.powerplatformplace.com

Was this reply helpful? Yes No
Cooper01 664 on at

Like (0)

Report
Copy link

Link copied!

Thanks so much for the links @AhmedSalih . For a specific use case, let's say I create a SQL Server connection using SQL Server Authentication. I can then use that connection in my apps and flows to write to whatever server/database I specified. My understanding is that because SQL Server connection is implicitly shared via any Power Apps I may create, other users can use the same connection. That is okay, since I would only share the apps with the people who should be able to interact with its underlying data.

So given that use case, are there any other measures I should take in order to guard the connection for use outside of my own and the users who have access to the apps I create that implicitly share the connection?

Was this reply helpful? Yes No
eleung83 232 on at

Like (0)

Report
Copy link

Link copied!

It would come down to identifying what privileges that connection allows to do with with the target system of the connnection, or if the connection is used to retrieve data, what's the risks posed with giving a user access to reuse the connection.

For example, imagine you setup a connection to a 3rd party api, that either deleted or retrieved data. If you shared that connection with the user, then they could, in theory create their own Flow, or app, that calls these actions, so they could also delete a record or possibly retrieve the data and export it somewhere else (fortunately you can apply DLP policies to restrict this but generally better to give as little access as required)

Was this reply helpful? Yes No
Verified answer

AhmedSalih 6,680 Moderator on at

Like (0)

Report
Copy link

Link copied!
Good morning @Cooper01, your use case seems standard and no one else other than those whom you shared the app with will have access to the connection. Two things you might need to take into consideration:
Users who have the implicit authentication, and can create another apps, can use the same connection in their new apps.
You can set up DLP policies in your Environment to restrict a combination of your SQL connections with other connector such as twitter or office365. Here is how to create DLP if needed.
Regards,

Ahmed

If my reply helped you, please give a 👍. And if it has solved your issue, please consider a 👍 & Accepting it as the Solution to help other members of the community find it more.
My Blog: www.powerplatformplace.com

Was this reply helpful? Yes No