Forum Discussion
Microsoft EmployeeUnable to connect to the Azure table storage
Hi Power BI team
I try to connect Power BI to the Azure table storage, but failed,
These are my steps:
1. Input the storage url:
2. Signed in with my Microsoft work account
3.After click, it will load all of the tables, but it will show an error even I clicked each one table:
DataFormat.Error: OData: The format 'application/json;odata=fullmetadata;streaming=true;charset=utf-8' is not supported.
Details:
application/json;odata=fullmetadata;streaming=true;charset=utf-8
4. Then I uodated the query string like this:
5. After clicked 'Done', it show the error like this:
6. Then I clicked the 'Edit Credentials', tried to signed in with Organaziation account, but got this error
7. Then I switch to Windows
8, After clicked Connect, finally, got this error
Could you please investigate the issue, provide your insights?
Hi yunliu ,
Thanks for reaching out to the Fabric Community.
To bypass the unsupported OData format error when connecting Power BI to Azure Table Storage, the most stable workaround is to skip the native connector and use Power Query’s Web.Contents() function to directly call the Table Storage REST API with custom headers specifically setting "Accept" = application/json;odata=nometadata and authenticating with a Shared Key or SAS token this lets you retrieve and transform the JSON data without running into Power BI’s enforced metadata formatting issues during refresh, and works reliably in both Desktop and Service environments
Workaround:
Use REST API via Web.Contents() Instead of OData
This bypasses the metadata negotiation entirely:
m
let
url = "https://<your_account>.table.core.windows.net/<your_table_name>()",
headers = [
#"Authorization" = "SharedKey <your_auth_header>",
#"Accept" = "application/json;odata=nometadata"
],
result = Json.Document(Web.Contents(url, [Headers=headers]))
in
result
Works in both Desktop and Service
Lets you control headers directly
Avoids OData limitations
Power Query OData Feed connector - Power Query | Microsoft Learn
Solved: Azure Table Storage to Power BI - Microsoft Fabric Community
Solved: Re: DataFormat Error when refreshing data from Azu... - Microsoft Fabric Community
We truly appreciate your continued engagement and thank you for being an active and valued member of the community. If you’re still experiencing any challenges, we’re more than happy to assist you further.
We look forward to hearing from you.
Best regards,
Lakshmi
3 Replies
v-lgarikapatCommunity Support
Hi yunliu ,
Thanks for reaching out to the Fabric Community.
To bypass the unsupported OData format error when connecting Power BI to Azure Table Storage, the most stable workaround is to skip the native connector and use Power Query’s Web.Contents() function to directly call the Table Storage REST API with custom headers specifically setting "Accept" = application/json;odata=nometadata and authenticating with a Shared Key or SAS token this lets you retrieve and transform the JSON data without running into Power BI’s enforced metadata formatting issues during refresh, and works reliably in both Desktop and Service environments
Workaround:
Use REST API via Web.Contents() Instead of OData
This bypasses the metadata negotiation entirely:
m
let
url = "https://<your_account>.table.core.windows.net/<your_table_name>()",
headers = [
#"Authorization" = "SharedKey <your_auth_header>",
#"Accept" = "application/json;odata=nometadata"
],
result = Json.Document(Web.Contents(url, [Headers=headers]))
in
result
Works in both Desktop and Service
Lets you control headers directly
Avoids OData limitations
Power Query OData Feed connector - Power Query | Microsoft Learn
Solved: Azure Table Storage to Power BI - Microsoft Fabric Community
Solved: Re: DataFormat Error when refreshing data from Azu... - Microsoft Fabric Community
We truly appreciate your continued engagement and thank you for being an active and valued member of the community. If you’re still experiencing any challenges, we’re more than happy to assist you further.
We look forward to hearing from you.
Best regards,
Lakshmi
yunliuHi v-lgarikapat
Thanks for your response!
The reason Power BI only supports connecting to Azure Table Storage using the account key (or SAS token) and not directly via Microsoft Entra ID (formerly Azure AD) is primarily due to technical limitations and protocol support.
Hi Lakshmi,
I am tryin to use the SAS key methond described above. I created a SAS token and populated the script above and added it to PowerBi using the powerQuery Editor, I got no errors but dont see any of my data. I must be missing something. Any advise?
Mike
