Most of the articles/posts/questions published on community or websites would be on Power BI “Commercial” product. The URL you have seen would be https://app.powerbi.com
This blog post is about “https://app.powerbigov.us” – Power BI URL for US Gov customers. More specifically this blog post is about embedding Power BI assets (Reports, Dashboards, QnA) for US Gov customers.
I would like to highlight certain differences in app registration URL and config URLs when embedding Power BI assets for US Gov clouds.
-> App Registration URL
The app registration URL for commercial cloud and US Gov cloud for Power BI Embedded are different. For:
-> When you register your app, the Power BI API name in Azure Portal would look like this:
US Gov Product
TIP: Based on our experience, when troubleshooting please look out for the API name that you see in Azure Portal. If you are embedding for Gov clouds, the API name should be “Microsoft Power BI Government Community Cloud”. If that is not the name, you would need to register the app on https://dev.powerbigov.us/apps
-> Embedding Config URLs
US Gov Product
You would see “resourceUrl”, “apiUrl” and “embedUrlBase” is different in case of US Gov clouds.
That’s it. These are the only changes in configuration and setup required for embedding in Power BI US Gov clouds. Everything else remain the same.
If you are looking for details on embedding with a sample .NET code, please head to our blog post on baby steps to embed your Power BI report.
Apply the configuration changes as mentioned in this blog post and you would be set to see the Power of embedded analytics for your US Gov clouds.
Questions? Please contact us through our website.