You have a Power BI tenant that contains 10 workspaces. You need to create dataflows in three of the workspaces. The solution must ensure that data engineers can access the resulting data by using…

Associating the Power BI tenant with an Azure Data Lake Storage Gen2 account enables all new workspaces in that tenant to use this storage for dataflows by default, allowing external services like Data Factory to access the data. This tenant-level configuration sets up the external storage capability.

Adding the managed identity for Data Factory as a member of the workspaces would provide access to Power BI items within the workspace, but it does not directly grant access to the underlying dataflow data stored in Azure Data Lake Storage Gen2, which requires permissions on the storage account itself.

To make dataflow data accessible to external services like Azure Data Factory, the dataflows must be created and saved to an Azure Data Lake Storage Gen2 account rather than Power BI's internal storage. This externalizes the data, making it available for other Azure services.

Saving dataflows to the internal storage of Power BI makes the data inaccessible to external services like Azure Data Factory, as it is managed solely within the Power BI service.