SQL Server environment variables (Entra) for Power Apps will save you time moving your solutions from one environment to another. For example, from an environment used for dev or test to a different environment used for test or production. Manually create environment variables in your solution or set a switch in your app to auto-create them for you when you add a data source to your app while in your solution. Note that this feature is specifically for Entra. Power Apps with shared connections (e.g., SQL Auth) continue with connection references.

There are two environment variables to set for SQL connections: server and database. The database environment variable depends on the server environment variable. First you create an environment variable for your server. Once that is created you can create an environment variable for the database that attaches to the server environment variable.

Use an environment variable by selecting to create data source and instead of creating a new server database combo, use the ‘Advanced’ tab to select the environment variable to bind to the controls in your app.

Use SQL Server environment variables (Entra) to easily enable professional deployment patterns. See the documentation for this feature for an in-depth discussion: Use environment variables in Power Platform solutions – Power Apps | Microsoft Learn

The post SQL Server environment variables available for Power Apps appeared first on Microsoft Power Platform Blog.

The new AAD user table is available automatically with no additional configuration required.

AAD User is different from the User table in Dataverse. The User table only displays users who have a Dataverse license assigned to them. AAD User will show anyone in the AAD User address book.  Note that the AAD User table is read only.

Here is a brief video about the new table, also information is available below.

The AAD User virtual table can be found in your Tables view by selecting “All”.

The table itself includes many valuable columns of information about each user.

AAD User can be used as a Lookup column in an existing table, which will immediately provide a list of all AAD Users.

With some additional formulas you can also use the selected dropdown value to populate additional information from the AAD User table into your forms

For example, the AAD User Lookup dropdown is DataCardValue5.  In the text field named Job Title the Default value is formula:

DataCardValue5.selected.’Job Title’

When the app is run, selecting a user from the dropdown will automatically retrieve the job title from the AAD User table and insert it into the text field.

Note: At this time, AAD User will not retrieve groups or provide expanded information such as manager. These are potential future enhancements to the table.

Important: AAD User is not currently available for Automate. This is planned for a future release.

API information for the AAD User table can be found here.

The post Announcing the AAD User Virtual Table – Find and add any AAD user to your records. appeared first on Microsoft Power Platform Blog.