Hi - I am trying to set up a Microsoft SQL server source. Unfortunately, the only way I can auth into it is via a service principal certificate (eg. I have a client id, tenant id, certificate and private key). Is there an easy way to make the existing connector work with certificates? Or should I create a custom connector for this?

I'm sorry, but the knowledge sources do not indicate that the current Airbyte Microsoft SQL Server (MSSQL) source connector supports authentication using a service principal certificate (i.e., client ID, tenant ID, certificate, and private key) as is typical for Azure AD Service Principal authentication. The supported authentication methods for the MSSQL connector are primarily username and password (basic authentication). There is some discussion and partial support for Active Directory authentication using username and password (ActiveDirectoryPassword), but this requires additional Java libraries and is not officially documented as supported or stable in the connector. There is no mention of support for certificate-based authentication (service principal with certificate/private key) in the available documentation or community discussions. Several users have requested support for Windows Authentication and other non-basic authentication methods, but these are not currently available features and are tracked as open issues in the Airbyte project roadmap [source-MSSQL Support Windows authentication](https://github.com/airbytehq/airbyte/issues/9557), [MSSQL Domain Credential](https://github.com/airbytehq/airbyte/issues/5300). If you require this authentication method, you would likely need to create a custom connector or extend the existing one to support service principal certificate authentication. Alternatively, you could monitor the open issues and feature requests for updates on this capability. In summary: The existing connector does not support service principal certificate authentication out of the box, and a custom solution would be required for your use case.