Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Compete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.

Reply
yunliu
Microsoft Employee
Microsoft Employee

Unable 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:

yunliu_0-1753435878899.png

2. Signed in with my Microsoft work account

yunliu_2-1753436074915.png

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

yunliu_3-1753436262025.png

4. Then I uodated the query string like this:

yunliu_4-1753436400418.png

5. After clicked 'Done', it show the error like this:

yunliu_5-1753436529158.png

6. Then I clicked the 'Edit Credentials', tried to signed in with Organaziation account, but got this error

yunliu_6-1753436650067.png

7. Then I switch to Windows

yunliu_7-1753436786454.png

8, After clicked Connect, finally, got this error

yunliu_8-1753436932663.png

Could you please investigate the issue, provide your insights?

 

 

 

 

 

 

1 ACCEPTED SOLUTION
v-lgarikapat
Community Support
Community 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

View solution in original post

2 REPLIES 2
v-lgarikapat
Community Support
Community 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

Hi @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.

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.

Top Solution Authors