O-365 Integration Error for Testing GET PowerBI Usage API

Asmita7
Tera Expert

Hello friends,

 

I am working on O-365 Integration to get software usage details automatically. I have created account on Microsoft Azure Portal as per the steps given in article :

https://docs.servicenow.com/bundle/vancouver-it-asset-management/page/product/software-asset-managem...

 

Direct integration profile created in ServiceNow with parameters like tenand ID, client secret etc.

OAuth token is successfully created. Then it has created 5 API/http methods :

1. GET PowerBI Usage

2. POST Users By Batch

3. GET users

4. Default GET

5. GET Reports

Out of these 5 API's, when tested using the related link "TEST", first 2 API tested failed:

1. GET PowerBI Usage : Error screenshot --

Asmita7_0-1693228688396.png

2. POST Users By Batch

Asmita7_1-1693228771620.png

The PowerBI error might be due to firewall but not sure.

 

Anyone please help on this.  How to resolve these errors.

 

Your support is valuable and will be appreciated.

 

Thank you

 

 

 

1 ACCEPTED SOLUTION

Community Alums
Not applicable

Sure. Will update accordingly. 

By the time, please check the Power Bi set up steps and admin center steps as per Docs.

View solution in original post

5 REPLIES 5

Community Alums
Not applicable

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

Asmita7
Tera Expert

Please provide the update if ServiceNow team provides any solution.

Community Alums
Not applicable

Sure. Will update accordingly. 

By the time, please check the Power Bi set up steps and admin center steps as per Docs.

aschwarz1
Tera Contributor

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?