Forum Discussion

jip34's avatar
jip34
Icon for Helper I rankHelper I
5 months ago
Solved

Help to publish report from ADLS Gen2 datasource with technical account

Hi everyone,

I’m running into an issue when working with Power BI Desktop and Azure Storage, and I’m hoping someone can clarify the correct approach.

🔹Context

My data (CSV files) is stored in Azure Data Lake Storage Gen2.
To access these files, I am required to use a technical account (a non‑personal account) because this is the only account that has the necessary permissions on the ADLS container.

When I use this technical account in Power BI Desktop:

  • I can authenticate successfully
  • I can access the CSV files
  • The refresh works fine locally

So far so good.

🔹Problem

When I try to publish my report to Power BI Service, I get a message saying that a Power BI Pro license is required.

However:

  • The technical account does not have a Power BI Pro license,
  • It cannot be assigned a license (company policy + it’s not a standard user account),
  • Therefore Power BI automatically switches to my personal account,
  • The dataset ends up being published under my personal account,
  • And then the refresh fails in Power BI Service, because my personal account does not have access to ADLS (only the technical account does).

🔹Question

Is there any supported way to:

  • publish a dataset using a technical account,
    OR
  • configure Power BI Service so that the dataset refresh uses the technical account,
    OR
  • handle this scenario in a recommended way?

 

I assume a gateway or service principal might be involved, but I am not sure what the best practice is in this situation.

Thanks in advance for any guidance!

  • Hii jip34 

     

    The recommended approach is to publish the report using a licensed account (or workspace with Premium capacity) and then configure the dataset credentials in Data source settings to use the technical account or a service principal that has access to the ADLS Gen2 storage. This way the dataset refresh can authenticate to ADLS using the technical identity while the publishing requirement is still met.

2 Replies

  • Hii jip34 

     

    The recommended approach is to publish the report using a licensed account (or workspace with Premium capacity) and then configure the dataset credentials in Data source settings to use the technical account or a service principal that has access to the ADLS Gen2 storage. This way the dataset refresh can authenticate to ADLS using the technical identity while the publishing requirement is still met.

  • Hi jip34

     

    rohit1991 is correct. After you publish the report with your licensed account, go to the semantic model settings and set up the datasource connections to use an account that has permissions on the ADLS storage.