Power Apps and secure implicit connections

The text discusses Power Apps and the concept of secure implicit connections. In Power Apps, data can be shared either 'implicitly' or 'explicitly' with external resources. With explicitly shared connections, the end user must authenticate to the back-end data source via their own credentials. This happens typically through Azure Active Directory or Windows authentication. The process is seamless, and the user may not even detect the authentication procedure. Explicitly shared connections are highly secure.

The text also mentions implied shared connections, a common feature in many Power Apps applications. In this regard, applications connect to resources like Azure SQL, SQL Server, or other external data sources. With implicitly shared connections, users use the account credentials of the app maker for connection and authentication to the data source during app creation, rather than their own login credentials.

Further Discussion on Connection Types in Power Apps

Understanding the distinction between explicit and implicit sharing is vital for application security and user login validation. Explicit sharing makes an app more secure since it requires user authentication, thus preventing unauthorized access.

On the other hand, implicit sharing can heighten the risk of unauthorized access because the user's credentials are not required for authentication. The app maker's credentials are the ones used to connect to the data source. In conclusion, while choosing a connection type in Power Apps, developers should balance between the ease of use offered by implicit sharing and the enhanced security offered by explicit sharing.

Read the full article Power Apps and secure implicit connections

Learn about Power Apps and secure implicit connections

Power Apps is a powerful tool that can be used to create connections to external resources such as Azure SQL, SQL Server, and other data sources. Depending on the security settings configured, the connection can be either explicitly or implicitly shared. Explicitly shared connections require the end user to authenticate with their own credentials, usually through Azure Active Directory or Windows authentication. This is the most secure way to connect to external resources. Implicitly shared connections, on the other hand, use the credentials of the account that the app maker used to authenticate during the app creation process. In this case, the end user's credentials are not used. Whenever the app is used, the credentials of the app maker are used to authenticate the connection. It is important to consider both types of connections when creating Power Apps applications and to always ensure that the security settings are set up properly.

More links on about Power Apps and secure implicit connections

Implicitly shared connections in Power Apps: what's the risk?

Oct 24, 2022 — An implicitly shared connection means that the user implicitly uses the credentials of the account that the app maker used to connect and ...

Enhanced security for implicitly shared connections in ...

Apr 1, 2023 — Microsoft has released a new feature for Power Apps called “Secure Implicit Connections” that provides enhanced security for implicitly ...

Caution! This is how users can hack shared SQL ...

If we create a connection using SQL Server or Windows Integrated authentication, Power Apps creates the connection as a shared "implicit" connection. This means ...

how secure are your power apps - everything you need to know

May 9, 2022 — An implicitly shared connection means that the user implicitly uses the credentials of the account that the app maker used to connect and ...

Implicit and explicit SQL connection, which one mimic the ...

Nov 14, 2022 — Implicit connection to sql from PowerApps. This means you will directly use sql inside powerapps as connection. In this case the user who will ...

Keywords

Power Apps, Explicitly Shared Connection, Implicitly Shared Connection, Azure Active Directory, Windows Authentication, Azure SQL