aRegister your application in Microsoft Entra ID and generate client ID, tenant ID, and client secret.
The connector does not require any API permissions assigned to your application. Additionally, you can remove any API permissions that are assigned to the application.
bCreate a security group with assigned owners or members in Microsoft Entra ID.
3To allow Microsoft Entra app to use the Power BI APIs, enable the Power BI service admin settings, and then add the Microsoft Entra app to the workspace in Power BI.
Note:
The Manage access pane in the Microsoft Entra app allows you to add roles based on the required capabilities. The pane displays admin, member, contributor, and viewer roles. The maximum number of capabilities are associated with the admin role. However, to access Microsoft Fabric OneLake and perform read and write operations, you need at least the Contributor role.
For more information about enabling access in the Power BI admin portal and adding the Microsoft Entra app to the workspace, see Enabling access in the Power BI portal.
Connect to Microsoft Fabric Lakehouse
Let's configure the Microsoft Fabric Lakehouse connection properties to connect to Microsoft Fabric Lakehouse.
Before you begin
Before you get started, you'll need to keep the client ID, client secret, tenant ID, workspace, and database details handy.
Check out Prerequisites to make sure that the setup is complete and all the prerequisites are in place before you configure a connection.
Connection details
The following table describes the basic connection properties:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
When you enable the secret vault in the connection, you can select the credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
Note:
If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.