Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now

Reply
BrunoM
Helper I
Helper I

Credentials provided for the OData source are invalid. (Source at https://api.security.microsoft)

Dear all,
We have several dataflows that are conected to the MS API via an Enterprise Gateway and an oData Source.

Three of them are connected to https://api.security.microsoft.com/api/xxxx . Power Bi Service Refreshs are OK

One of them is using this URL : https://api.security.microsoft.com/api/recommendations . The connexion is not possible On PowerBI Services whereas it is working fine in the PBI Desktop.

BrunoM_0-1670580330843.png

 

How can we do to solve this pb ?

 

 

PS : here the Code M in each case :

OData.Feed("https://api.security.microsoft.com/api/machines", null, [Implementation = "2.0"]) (OK in Power BI services)
OData.Feed("https://api.security.microsoft.com/api/recommendations", null, [Implementation = "2.0"]) (KO i Power BI Services with the error: Credentials are required to connect to the OData source. (Source at https://api.security.microsoft.com/api/recommendations.) )

 


In advance thank you for your help.
Bruno



 

1 ACCEPTED SOLUTION

Hi , @BrunoM 

According to your error screenshot, the error message you are currently encountering is still an "invalid credential" error, so you can confirm that the credential you input for the datasource definition configuration is the same credential you entered when connecting to the data source and creating the data flow, and the privacy level is also consistent, if confirmed, you can put error The detail expansion is sent in text format here for further study.

 

Thank you for your time and sharing, and thank you for your support and understanding of PowerBI! 

 

Best Regards,

Aniya Zhang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

View solution in original post

7 REPLIES 7
v-yueyunzh-msft
Community Support
Community Support

Hi , @BrunoM 

According to my understanding of Power BI gateway, it is generally used as a bridge between Power BI Service and on-premises data sources, and you describe that you want to connect to some MS APIs through the gateway to configure data flow refresh on the service, which is also possible in principle. According to your description, you have a problem configuring the gateway connection to connect OData.Feed("https://api.security.microsoft.com/api/recommendations", null, [Implementation = "2.0"]) with the error: Credentials are required to connect to the OData source. For convenience, you can check if you can enter credentials for this data source by editing the credential directly in the datasource credential. Can skipping the gateway level avoid this error?

vyueyunzhmsft_0-1670810108723.png

 

Thank you for your time and sharing, and thank you for your support and understanding of PowerBI! 

 

Best Regards,

Aniya Zhang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

Hi Aniya,
Thank you for your message. 
You propose to skip the gateway: In fact, as you can see in the screenshot, those sources do not use the gateway

BrunoM_0-1670835376661.png

 

They are identified as a connexion in the gateway admin portal but they do not use the Gateway cluster and software.

Trying to redo a complete setting of this connexion, i have removed it from the Gateway admin portal then à i recreated it throught the dataflow :

BrunoM_1-1670836481828.png

 

BrunoM_2-1670836526183.png

 

BrunoM_3-1670836561398.png

 

Result : Same error message in the dataflow power query interface.

Trying to update the connexion in the dataflows settings tab :

BrunoM_4-1670836668491.png

 

 

BrunoM_6-1670839011104.png

 

Changing Private into organizational then sign in :

BrunoM_10-1670839786267.png

 

BrunoM_7-1670839609467.png

 

BrunoM_9-1670839733892.png

 

 

Best regards, Bruno

 

Hi , @BrunoM 

According to your error screenshot, the error message you are currently encountering is still an "invalid credential" error, so you can confirm that the credential you input for the datasource definition configuration is the same credential you entered when connecting to the data source and creating the data flow, and the privacy level is also consistent, if confirmed, you can put error The detail expansion is sent in text format here for further study.

 

Thank you for your time and sharing, and thank you for your support and understanding of PowerBI! 

 

Best Regards,

Aniya Zhang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

Hello Aniya,
Thank you for your message and sorry for my late update.
I need to give a feedback : the pb has been solved by the author of the dataflow. He put his credentials and the connexion was OK.

Hi @BrunoM ,

 

I would really appreciate it if you could share any details how fix it?

I have the same problem with OData feed connection.

 

Thanks,

Alina 

lbendlin
Super User
Super User

What made you choose to use a gateway for this?

Hi,
Sorry for my late update ...
I need to give a feedback : the pb has been solved by the author of the dataflow. He put his credentials and the connexion was OK.

Helpful resources

Announcements
November Carousel

Fabric Community Update - November 2024

Find out what's new and trending in the Fabric Community.

Live Sessions with Fabric DB

Be one of the first to start using Fabric Databases

Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.

Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.

Nov PBI Update Carousel

Power BI Monthly Update - November 2024

Check out the November 2024 Power BI update to learn about new features.