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

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

JoshT — Thu, 17 Nov 2022 11:54:00 GMT

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

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?

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

Habitat — Thu, 17 Nov 2022 16:24:31 GMT

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

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

JoshT — Fri, 18 Nov 2022 12:37:39 GMT

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.

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

JoshT — Tue, 22 Nov 2022 17:27:11 GMT

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!