docs/quick-ingestion-guides/powerbi/configuration.md
Now that you have created a DataHub-specific Microsoft Entra application with the relevant access to Power BI in the prior step, it's now time to set up a connection via the DataHub UI.
:::note If you do not see the Ingestion tab, please contact your DataHub admin to grant you the correct permissions :::
This will securely store your client secret value.
POWER_BI_CLIENT_SECRET - we will use this later to refer to the client secretEnter details into the Power BI Recipe
You need to set minimum 3 field in the recipe:
a. tenant_id: Use the Directory (tenant) ID from your Microsoft Entra application.
b. client_id: Use the Application (client) ID from your Microsoft Entra application.
c. client_secret: Use the secret POWER_BI_CLIENT_SECRET with the format "${POWER_BI_CLIENT_SECRET}".
d. environment: (Optional) Specify the Power BI environment to connect to. Use 'commercial' for commercial Power BI (default) or 'government' for Power BI Government Community Cloud (GCC).
Optionally, use the workspace_id_pattern field to filter for specific workspaces.
config:
...
workspace_id_pattern:
allow:
- "258829b1-82b1-4bdb-b9fb-6722c718bbd3"
Your recipe should look something like this:
<p align="center"> </p>After completing the recipe, click Next.
Now it's time to schedule a recurring ingestion pipeline to regularly extract metadata from your Power BI instance.
You will now find your new ingestion source running
<p align="center"> </p>Congratulations! You've successfully set up Power BI as an ingestion source for DataHub!