Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
I am trying to include both AAD and OAuth authentication supports in a customer connector (using data connector SDK + ODBC driver). But it seems like Power BI will take only the first one. For example, if I have the following code:
Authentication = [
Aad = [
AuthorizationUri = AadGetAuthorizationUri,
Resource = AadGetResource,
Scope = ".default"
],
OAuth = [
StartLogin = StartLogin,
FinishLogin = FinishLogin,
Refresh = Refresh,
Logout = Logout,
Label = "OAuth"
],
Implicit = [],
UsernamePassword = [
Label = "LDAP"
],
Windows = [
Label = "Kerberos"
],
Key = [
Label = "Personal Access Token (JWT)",
KeyLabel = "Personal Access Token (JWT)"
]
],
I will get:
If I move OAuth to the top, I will get:
Is it possible to have both AAD and OAuth in the same connector?
I saw that Databaricks connector provides two connectors, one supports OAuth, and the other supports AAD. Do I have to do the same?
Solved! Go to Solution.
Hi @xsgao ,
Based on your description, it is indeed difficult to support both AAD and OAuth authentication in the same custom connector in Power BI. This is because Power BI usually prioritizes the first authentication method listed, which is why you'll run into problems when trying to include both.
To implement support for both AAD and OAuth, you may need to create two separate connectors, similar to what the Databricks connector does. This way, each connector can handle specific authentication methods without conflict.
Best regards,
Albert He
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Hi @xsgao ,
Based on your description, it is indeed difficult to support both AAD and OAuth authentication in the same custom connector in Power BI. This is because Power BI usually prioritizes the first authentication method listed, which is why you'll run into problems when trying to include both.
To implement support for both AAD and OAuth, you may need to create two separate connectors, similar to what the Databricks connector does. This way, each connector can handle specific authentication methods without conflict.
Best regards,
Albert He
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly