- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2023 09:05 AM
I am also facing the same issue. Actually the Direct Integration profile created is correct.
Please check following :
1. Please create a security group and follow the steps in ServiceNow Docs to provide Power BI access on Azure application.
I have created a High Ticket with ServiceNow. If I get any update, will update here. You also can create a Vendor case and update the status.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2023 09:06 AM
Please provide the update if ServiceNow team provides any solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2023 09:07 AM
Sure. Will update accordingly.
By the time, please check the Power Bi set up steps and admin center steps as per Docs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2024 06:41 AM
Were you able to solve this issue? I am getting the exact same errors on my end. Did you figure out what the specific issue was with your Power BI set up steps?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-29-2024 11:27 AM
Hello, I was able to solve the issue for my client. My client is on a GCC instance of Power BI. This requires updating two things.
1. REST Endpoint
2. OAuth Scope
By default, ServiceNow uses the worldwide versions of these. Currently, their installation documentation only mentions endpoints, not OAuth scope. I have an open HI Case informing them of this omission.
GCC Scope: https://analysis.usgovcloudapi.net/powerbi/api/.default
GCC GET PowerBI Usage endpoint: https://api.powerbigov.us/v1.0/myorg/admin/activityevents
Keep in mind, the endpoints vary and you can figure out which one you need to use using this Microsoft article:
https://learn.microsoft.com/en-us/power-bi/enterprise/service-govus-overview
Once I updated both of these and re-ran the SAM - Collect Microsoft 365 Usage scheduled job, I got the Power BI success indicator.