Does Azure Data Factory postgreSQL linked service connector no longer support a full connection string stored in Key Vault?

Question

Hi,

Does Azure Data Factory postgreSQL linked service connector no longer support a full connection string stored in Key Vault?

We are using the postgreSQL legacy version and it just points to Key vault where we have a full connection string in format: server=xxxx_server.com;Port=xxxx;Database=xxxx;UID=xxxx;EncryptionMethod=1;ValidateServerCertificate=0;Password=xxxx

But with the new postgreSQL version it seems we can't point to one full connection string? Instead we need to separately separate server name, port, database name, user name, and password?

Am i understanding this correctly or is there a workaround? We will need to update in quite a few places in ADF and files to separate these out.

Thank you for your insight!

Answer 1

Yes, you are correct. With the legacy PostgrSQL connector the entire connection string can be stored in key vault. but, it won't let you parameterize the connection string,

However, you can still parameterize the server name, port, database name, and user name by selecting the connection string option using the PostgreSQL legacy connector.

With PostgreSQL v2

Storing the connection string using the Azure key vault has been removed. This eliminates the need to create a linked service for each database on the logical SQL server. Instead, you can parameterize the properties such as server name, port, database name, and user name.

(by parameterizing the properties).

So uinsg Postgre SQL V2, you can't use the entire connection string in one key valut secret. This is by design.

You can refer to the following documentation for more information on how the linked service parameterization works.

https://learn.microsoft.com/en-us/azure/data-factory/parameterize-linked-services?tabs=data-factory#supported-linked-service-types

I hope this helps.