Authentication types supported from Azure AS to Azure SQL

Question

Dear Experts,
as part of a migration project I am trying to connect Azure AS Tabular to Azure SQL through Database Gateway and Private Endpoint.
(This method was actually recommended by Microsoft experts to be able to use only Private Endpoint and disable Public Access to Azure SQL).

Without Database Gateway and Private Endpoint, the following worked for me:

• SQL / UsernamePassword
  "credential": {
  "AuthenticationKind": "UsernamePassword",
  "kind": "SQL",
  "path": "something",
  "Username": "USER_NAME",
  "Password": "PASSWORD",
  "EncryptConnection": false
  }
• OAuth2, getting token from https://database.windows.net, and using
  "credential": {
  "AuthenticationKind": "OAuth2",
  "AccessToken": "ACCESS_TOKEN"
  }

Side note, Powershell Get-AzAccessToken does not return Refresh Token, only access token. Strange.

But my first question is, exactly what authentication kinds are availabe in this scenario without Database Gateway?
Because I could not find a list anywhere. Tried the list of values found for ADO with and without spaces (ActiveDirectoryPassword, Active Directory Password, Active Directory MFA, Active Directory Default, Active Directory Integrated etc.) but for all listed ones the following error appearead at data load time:
Error returned: '<ccon>The data source kind doesn't support the credential type. Data source kind: SQL. Credential type: ActiveDirectoryPassword.</ccon>. The exception was raised by the IDbConnection interface.

After connecting through Database Gateway + Private link, even the OAuth2 stops working with this error message:
<ccon>The server name provided doesn't match the server name on the SQL Server SSL certificate. Please see https://go.microsoft.com/fwlink/?LinkId=394782. (Source at INSTANCE.privatelink.database.windows.net;DBNAME.)</ccon>. The exception was raised by the IDbCommand interface.

The link points to ADO.Net Data Provider What's new page, no actual information about the problem.

Tried Googling, crawled Microsoft Learn links, ADO, SSAS, ASQL resources, no actual luck.

So my second question is, has anyone faced the same error? If so, could you please point me to the right direction?

Any help is greatly appreciated.

Barna

Answer 1

@Barnabas Sipos Sorry for the delay in my response
you should use the same FQDN regardless of the private link or not. SSL will fail since the SSL cert does not contain an entry for *.privatelink.database.windows.net. The “private link” FQDN is not to be used directly.

Please let me know if you need any additional information.

Regards
Geetha