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

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Reply
JoshT
Advocate II
Advocate II

Status code 400 (bad request) on some Admin API calls

I've been getting a bad request calls to two of the admin APIs, GetGroupsAsAdmin and GetAppsAsAdmin, despite making calls in line with what the documentation (https://learn.microsoft.com/en-us/rest/api/power-bi/admin/groups-get-groups-as-admin) says.

 

I can make calls successfully to other admin APIs (e.g. dataflows and datasets). The difference with these two seems to be that they both have mandatory $top parameters, but I get the error whether or not I supply this parameter.

 

 

Connect-PowerBIServiceAccount
Invoke-PowerBIRestMethod -Method Get -Url "https://api.powerbi.com/v1.0/myorg/admin/groups?$top=10"
$Error[$Error.Count - 1].Exception.InnerException

 

JoshT_0-1668685418845.png

 

I've connected both as a tenant admin and as a service principal with the admin scope allowed and not had success with either. Are these APIs broken or am I doing something wrong?

1 ACCEPTED SOLUTION
JoshT
Advocate II
Advocate II

Using fiddler, found out that $top parameter wasn't being sent - the dollar sign required for the parameter name meant PowerShell was pulling in a session variable that didn't exist (so the uri would have been "https://api.powerbi.com/v1.0/myorg/admin/groups?=10" ).

 

The correct syntax is as below:

 

Invoke-PowerBIRestMethod -Method Get -Url "https://api.powerbi.com/v1.0/myorg/admin/groups?`$top=10"

 

I guess that's the problem with using the PowerShell ISE, string and variable are highlighted in only slightly different shades of brown!

View solution in original post

3 REPLIES 3
JoshT
Advocate II
Advocate II

Using fiddler, found out that $top parameter wasn't being sent - the dollar sign required for the parameter name meant PowerShell was pulling in a session variable that didn't exist (so the uri would have been "https://api.powerbi.com/v1.0/myorg/admin/groups?=10" ).

 

The correct syntax is as below:

 

Invoke-PowerBIRestMethod -Method Get -Url "https://api.powerbi.com/v1.0/myorg/admin/groups?`$top=10"

 

I guess that's the problem with using the PowerShell ISE, string and variable are highlighted in only slightly different shades of brown!

Habitat
Regular Visitor

Hi @JoshT 

 

Check this:

Permissions

  • The user must have administrator rights (such as Office 365 Global Administrator or Power BI Service Administrator) or authenticate using a service principal.
  • Delegated permissions are supported.

Required Scope

Tenant.Read.All or Tenant.ReadWrite.All

Yes, sorry, by tenant admin I meant Power BI service admin, and the service principal I'm using as an alternative has the necessary scope - as I said, other admin APIs work fine, it's just the groups and apps ones that don't work under any circumstances, with any of the parameters specified as per documentation.

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!

Jan25PBI_Carousel

Power BI Monthly Update - January 2025

Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.

Jan NL Carousel

Fabric Community Update - January 2025

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