The credentials provided for the AzureTables source are invalid.

[JolinTsai]

Hi,

I'm facing data source error.

I am using the Power BI desktop which connects to my data successfully, and when I publish up to the PowerBI server/workspace. My data connections no longer work. I receieve the following message. Would you kindly help with providing some insights?

Error Messages:

Data source error: The credentials provided for the AzureTables source are invalid. (Source at https://xxxx.table.core.windows.net/.). The exception was raised by the IDbCommand interface.
Cluster URI: DF-MSIT-SCUS-redirect.analysis.windows.net
Activity ID: e68b3cd5-dd9e-43a4-baed-08cb04d92a38
Request ID: a85c86ec-9647-d25f-e87c-6f182a28add7
Time: 2025-08-06 10:10:41Z

Backgrounds:

Provided Credentials: Work Identity (my organizational account)

No Data

Data Source: AzureTable

Regions of AzureTable: Japan East

Regions of PowerBI workspace: West Central US(MSIT)

Data Source's Privacy Level on Desktop: None

Data Source's Privacy Level on Workspace: None

Connection Status on PowerBI Workspace: Green

Gateway Connections on PowerBI Workspace: Off and using default clode connections.

[JolinTsai]

Okay...
I see the statement on the official document. This is so unsatisfying. What's the meaning to make credentials only works on Desktop? How come a product make an assumption that the users will not share their reports? And every reports that users made are one-time only, no more data updates?

Power Query Azure Table Storage connector - Power Query | Microsoft Learn

You've answered my question, though.

[v-karpurapud · Accepted solution]

Hi @JolinTsai 

Thank you for contacting the Microsoft Fabric Community Forum.

The error occurs because Power BI Service does not support using Azure Active Directory (Organizational Account) authentication for Azure Table Storage connections. While the connection works successfully in Power BI Desktop using your organizational credentials, these credentials are not automatically transferred to the Power BI Service after publishing. As a result, the dataset fails to refresh with the error: “The credentials provided for the Azure Tables source are invalid.” To fix this, go to the dataset settings in Power BI Service and update the data source credentials. Switch the authentication method from "Organizational Account" to either "Account Key" or "Shared Access Signature (SAS)", as these are supported. After entering and saving the correct credentials, your dataset should refresh successfully. Also, make sure the privacy level is set to “None” to match your Power BI Desktop settings. This will ensure a stable connection and proper authentication in Power BI Service.

I hope this information is useful. If you need more assistance, feel free to reach out us . We will be happy to assist you.

Regards,
Karpurapu D,
Microsoft Fabric Community Support Team.

[oscarhermoso]

Hi @v-karpurapud,

Any plans to fix this? Our organisation does not allow us to deploy storage accounts with SAS / Account Keys due to the security concern of long-lived passwords. I have run into the same issue as @JolinTsai when attempting to use Workspace Identity with Azure Table storage.

Thanks, 

Oscar

[v-karpurapud]

Hi @oscarhermoso 

Currently, Microsoft has not released a public roadmap, announcement, or confirmed timeline for adding Azure AD, Managed Identity, or Workspace Identity support for Azure Table Storage in Power BI Service. The connector only allows authentication via Account Key and SAS token, and there are no updates on planned authentication improvements for this source. As a result, organizations that restrict the use of SAS tokens or account keys cannot connect Azure Table Storage directly to Power BI Service at this time.

To address this, customers with strict security policies often use a Managed Identity–secured middle tier, like an Azure Function, Logic App, or API, to access Table Storage data, or they migrate the data to other services that support Azure AD authentication in Power BI, such as Azure SQL, ADLS Gen2, or Fabric Lakehouse. Until native AAD or Workspace Identity support is available, these are the only keyless alternatives.

If you have any more questions, please let us know and we’ll be happy to help.

Regards,

Microsoft Fabric Community Support Team.