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

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

Reply
bkuhse
Frequent Visitor

401 Error when rebinding report

We're doing some preliminary exploration of the API via PowerShell and receiving a 401 error when attempting to rebind a report to a new dataset.  Other API calls are successful, including other POST actions like cloning.  There are no details provided with the 401.

 

Can anyone offer any insight as to what may be causing this?

 

A GET to this URL works fine: 

https://api.powerbi.com/v1.0/myorg/groups/$ReportWorkspace/reports/$ReportID

 

And so does a POST here (necessary parameters passed in the body):

https://api.powerbi.com/v1.0/myorg/groups/$ReportWorkspace/reports/$ReportID/Clone

 

A POST to this URL results in a 401 (datasetID passed in the body):

https://api.powerbi.com/v1.0/myorg/groups/$ReportWorkspace/reports/$ReportID/Rebind

 

 

Having this functionality work is an important part of our planned deployment for PowerBI, and I spent far too long yesterday pounding my head against this vague error.  Any direction would be appreciated!

 

 

 

 

1 ACCEPTED SOLUTION
Eric_Zhang
Microsoft Employee
Microsoft Employee

@bkuhse

The Rebind API works in my test, as to 401, it is a unauthorized issue, please go to Azure portal and ensure that you've set all permissions for the registered app and then click grant permissions.

 

Capture2.PNGCapture.PNG

 

 

View solution in original post

2 REPLIES 2
Eric_Zhang
Microsoft Employee
Microsoft Employee

@bkuhse

The Rebind API works in my test, as to 401, it is a unauthorized issue, please go to Azure portal and ensure that you've set all permissions for the registered app and then click grant permissions.

 

Capture2.PNGCapture.PNG

 

 

We've been skating by so far using the ClientID supplied by the PowerShell library we're using - attemping to pass our own ClientID results in errors I've been trying to avoid troubleshooting, but it sounds like it's time for us to put our big boy pants on and do this the right way.

 

Appreciate the info!

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

November Carousel

Fabric Community Update - November 2024

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

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.