Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
We are trying to build a database with PowerBI auditing information.
In our case, the ideal solution is, that we want to load data from the REST APIs towards AWS. (I know.. don't ask... 🙂
We have setup an Azure AD App registration for this. Inspired by several youtube videos and this blog post:
How to Call the Power BI REST API from Postman - Carl de Souza
For this app, we have requested our office tenant admin to approve Tenant.Read.All privileges.
That is probably a little different than what Carl described. I dont want to use the "delegated permissions" since I dont want to logon with my corporate ID, but I want to login with a clientID and secret coming from our AWS environment.
My issue is now, that I am trying to connect from Postman, but I am failing.
First I am trying to do a Post to get a bearer token. This seems succesful, although I am wondering: should I also see a "scope" mentioned in the result? I have seen it with other screenshots on the web.
Then, while trying to do a simple get, using this bearer token, I am getting a "401 unauthorized".
Can someone please suggest what I am doing wrong? Any suggestion would be highly appreciated!
Update:
meanwhile I came across this article about Service Principals
Enable service principal authentication for read-only admin APIs - Power BI | Microsoft Docs
Would that be the right way to go? I tried some of the steps, and went to a different error message:
Solved! Go to Solution.
@Anonymous , the link is the right way to do it. You need to:
1. Create the security group
2. Add the service principal in a security group.
3. Enable the "Allow service principals to use read only ..." feature
4. Add the security group in "Allow service principals to use read only ..."
Re-test after 10-15 minutes (AAD groups and member propagation in all services)
@Anonymous , the link is the right way to do it. You need to:
1. Create the security group
2. Add the service principal in a security group.
3. Enable the "Allow service principals to use read only ..." feature
4. Add the security group in "Allow service principals to use read only ..."
Re-test after 10-15 minutes (AAD groups and member propagation in all services)
Indeed! I just figured out that this works!
It took quite some time to learn that this was the right approach.
Thanks for your support!
I maybe won't help to much with this but, for the app that we have, we need to invite the user as a guest to the tenant and add him to the security group on the Azure ad, then that group need to be part of the app access. When you create any app on Azure, you also have enterprise applications and under your app, you need to add that group otherwise, they won't be able to access it.