This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreGet Fabric Certified for FREE during AI Skills Fest. This week only. Secure your voucher now.
Hi,
I am looking for a way to perform an API call that requires client credential flow. My first approach is using the On-prem Gateway with a custom connector. The custom connector has the hardcoded client ID and client secret. This approach is not good enough sine we want to provide a generic custom connector to all of our clients. I want a way for the customer to store client ID and client secret from within PowerBI Service. My alternatives are using parameters or repurposing the user ID and password as client ID and secret. Any suggestions?
Edit: This is with the assumption that our clients will install their own On-prem gate way within their network. We will provide them the client credentials to consume our API.
thank you
I ended up relabeling windows authentication fields. Username to client id and Password to client secret. Is this a recommended practice to store client credentials in powerBI Service?
You will need to create a custom connector and then install the .mez on all gateway cluster members.
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 3 | |
| 2 | |
| 1 |
| User | Count |
|---|---|
| 11 | |
| 11 | |
| 5 | |
| 4 | |
| 3 |