Forum Discussion
Power BI Government API
Hi Everyone,
At this moment we are building some automation scripts that make use of the Power BI API. When connecting to Power BI government tenant we are having some authentication issues.
Could someone inform me what the difference is between the two versions government / Non government. And how we can use the api's within a government tenant.
With regards
11 Replies
I think you mean Government. Governance is something different.
I couldn't find an API specific link but here is a general feature comparison between "regular" and "government" capacities:
https://docs.microsoft.com/en-us/power-bi/admin/service-govus-overview
lbendlin : You are totally right. I was working on a Azure Governance model and mixed things up.
Also thank you for that information, I really hope that there is someone who has more information regarding the API's
The biggest difference between Government and Commerical is that Government has more restrictions than Commerical does. So, lots of features come later on GC Cloud.
This link goes over the limitations of the different Government Cloud options:
Microsoft 365 Government Community Cloud (GCC) is designed for federal, state, and local government.
Microsoft 365 Government Community Cloud High (GCC High) is designed for federal agencies, defense industry, aerospace industry, and other organizations that hold controlled unclassified information. This environment is suited for national security organizations and companies that have International Traffic in Arms Regulations (ITAR) data or Defense Federal Acquisition Regulations Supplement (DFARS) requirements.
The Microsoft 365 DoD environment is designed exclusively for the US Department of Defense.
This link goes over all the different API web addresses for government
Here's the Power BI Government Blog
For using the API you would use it the same way as you would use the Commerical API with the difference being the address.
https://api.powerbi.com/v1.0/myorg/
vs
https://api.powerbigov.us/v1.0/myorg/
So the same calls found on this link would be used
https://docs.microsoft.com/en-us/rest/api/power-bi/admin/datasets_getdatasetsasadmin
Hope this helps.
Did my answer(s) help you? Give it a kudos by clicking the Thumbs Up! ?
Did my post answer your question(s)? Mark my post as a solution. This will help others find the solution.This is exactly what I'm looking for! Thanks!
Do you maybe also know if there are ways to test it? I'm building automation scripts and would also like to make them compatible with the government api's
Sure try this
Did my answer(s) help you? Give it a kudos by clicking the Thumbs Up! ?
Did my post answer your question(s)? Mark my post as a solution. This will help others find the solution.
Hi Watsky
I am also using Government Power BI Version.
I can get a bearer token using postman.
But when I tried to do a simple GET or POST method using postman I am getting this error "403 Forbidden - The request was a legal request but the server is refusing to respond to it. Unlike a 401 Authorization response, Authenticating will make no difference."
Any thoughts on this error message?
Get request I am using - https://api.powerbigov.us/v1.0/myorg/groups/{dataset_ID}/datasets
Hey Anonymous ,
It's hard for me to say without knowing more background on how you're trying to connect to it for instance what you're using for your token uri, auth uri, or redirect uri. What I can tell you is that if you're Azure authentication is MFA then Postman can't handle the request. Postman can only do single factor. If you want to test using Postman you can still do it but you'll need to grab a token from a different place.
1. Log into apps.powerbigov.us
2. Click F12
3. Navigate over to Network
4. Click through the different requests that are shown (Some may just have numbers. These usually have the bearer)
5. Copy the token and give that a try.
Did my answer(s) help you? Give it a kudos by clicking the Thumbs Up! ?
Did my post answer your question(s)? Mark my post as a solution. This will help others find the solution.
