Report a bug on Power BI Desktop OData Connector

Hello teams,

I have had try to use the latest version of Power BI Desktop (Version 2.92.706.0) to get Azure AD Users’ information by calling Azure AD Graph API: “https://graph.windows.net/Tenant ID/users?api-version=1.6” via OData connector. However, I have met the below error:

Error detail:

I use fiddle to grab the request from Power BI Desktop and compare it with the request from Azure AD API explorer, got the below information:

Request from Power BI Desktop OData Connector

Detail: https://graph.windows.net/a2486d92-68be-49af-96ec-3aca3f969cf6/directoryObjects/$/Microsoft.DirectoryServices.User?$skiptoken=X'44537074020001000000143A6368656C736561406A6566667A68752E746F7029557365725F63333162363539342D316530312D343239302D626363612D646630376564303566383864B900000000000000000000'

Request from Azure AD explorer

Detail: https://graph.windows.net/a2486d92-68be-49af-96ec-3aca3f969cf6/directoryObjects/$/Microsoft.DirectoryServices.User?$skiptoken=X%2744537074020001000000143A6368656C736561406A6566667A68752E746F7029557365725F63333162363539342D316530312D343239302D626363612D646630376564303566383864B900000000000000000000%27&api-version=1.6

Based on Azure AD Graph API Document (https://docs.microsoft.com/en-us/previous-versions/azure/ad/graph/howto/azure-ad-graph-api-versioning)

“You must specify the version of an operation that you want to use by including the api-version query string parameter in your request. Requests without an api-version parameter will be rejected and return a (400) Bad Request response. ”

Regarding the above information, the issue is caused by the Power BI Desktop OData request lake of the suffix of API version when requesting the OdataNextLink.

I also test the behavior on Power BI Desktop (Version 2.91.884.0), and the result is normal. So the issue only happened on the latest version (2.92.706.0) of Power BI Desktop.

Please notice PG fixes this bug.