Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
I'm attempting to build, for the first time, a custom connector in the power query sdk. Authentication to the api is handled by OAuth 2, with grant-type=client_credentials. If I were to use curl the request would look like this:
curl -u '<Client ID>:<Client Secret>' \
--data 'grant_type=client_credentials' \
'https://<domain>/oauth/token'
I can't figure out how, in the SDK, to remove the requirement for the user to authenticate against a URI as they'd be expected to do if the grant-type were authorization_code. StartLogin appears to be a mandatory method when Authentication = OAuth, and within StartLogin a ResourceURI is also mandatory. Any help gratefully received.
Solved! Go to Solution.
Support for SPN is currently not supported for custom connectors. You could probably implement this yourself using the API key auth type. Another option is to create a service account as a stand in for the service account. The gateway admin portal does support service principal, so maybe that would work for what you are doing?
Support for SPN is currently not supported for custom connectors. You could probably implement this yourself using the API key auth type. Another option is to create a service account as a stand in for the service account. The gateway admin portal does support service principal, so maybe that would work for what you are doing?
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
10 | |
8 | |
6 | |
6 | |
6 |