Use Azure Key Vault Secrets in Azure Data Factory for SQL Connection and Blob Connection ADF 2021

[@rogerfleming3165]

Great video on the use of keyvault

[@satellitepop]

Great work. Thanks !!!!!!!

[@java_interview]

Thank you so much 😀

[@BACHARBOUAZZA]

Thank you very much, good job.

[@azeezullasheriff7746]

Neat explanation, I know it would take time for me to do all these steps. Thanks

[@sravankumar1767]

superb..........

[@anjaliyadav]

My sql server database is set up to allow managed identity authentication only, no sql authentication is permitted (even for the admin), how/where do I copy the connection string from in that case? Goal is to save the sql connection as kv secret and use it to connect from ADF.thx

[@ntozakhona4806]

Brilliant

[@kanyagudipati8605]

Why is video is getting blurred occasionally

[@hugomartinezf]

Is it possible to do it via IAM instead of Policies?

[@rirockzone]

Yes, it's possible if you have "Azure role-based access control (recommended)" configured in "Access configuration". If you want to grant access to your ADF, you just need to add your ADF in IAM with the appropriate Role assignment. I chose the "Key Vault Secrets User" role for my ADF, and after that, the connection check passed.

[@suneelchavali]

I created Azure Key Vault and secret as Access Key value of storage account. It is successful in creating linked service of storage account with KV. When I tried to connect the same with secret as connection string of storage account, It is getting failed in connecting through linked service. Error is "The specified account key is invalid. Check your ADF configuration. The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters."

[@sravanthiyethapu9970]

Hi While creating linked service for SQL database using key vault getting an error that invalid database connection string provided ( The length of argument 'password' exceeds its limit of '128') Please help me with the issue

[@FreakONcW1]

Got the same issue. Did you get any resolution?