How to use ClientID and ClientSecrets to create pipelines

Hi itsAftab,

Thank you for reaching out to the Microsoft Fabric Community Forum.

We really apologies for the inconvenience, I have gone through the details that you have shared based on how to use client id and client secrets to create pipelines.

Please go through the following steps may resolve the issue:

• Kindly refer to the vendor's API documentation for details on the access token URL, the exact payload and headers required for authentication, and the necessary scopes or permissions to access the data.
• Generally, you can obtain the access token by sending a POST request to the vendor's token endpoint. Here is a standard example using OAuth 2.0.

POST <vendor's Access Token URL>

Content-Type: application/x-www-form-urlencoded

client_id=<vendor-client-id>

client_secret=<vendor-client-secret>

grant_type=client_credentials

scope=<vendor-specified-scope>

Replace the placeholders <vendor-client-id>, <vendor-client-secret>, etc. with the actual values provided by the vendor.

• Prior to integrating this into your MS Fabric pipeline, please test the token generation process using tools such as Postman or cURL. Ensure you can successfully retrieve an access token and utilize it to make authenticated API requests.
• In your MS Fabric pipeline, go to the settings for the connection or data source. Enter the vendor's client ID, client secret, and access token URL in the authentication configuration.

If required, set up custom headers or parameters to pass the access token in API requests. For example, use the header:

Authorization: Bearer <access-token>

• If the connection fails, check the logs or responses for specific errors e.g., invalid credentials, missing scopes. Ensure the vendors API is accessible from your network.

If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Thank you.