Forum Discussion

svenchio's avatar
svenchio
Icon for Super User rankSuper User
5 months ago
Solved

Using key vault reference with on-prem connections

Hi everybody, according to article https://learn.microsoft.com/en-us/fabric/data-factory/azure-key-vault-reference-configure it seems like Key Vault references are not supported for on-prem data gateway connections ... assuming this was introduced between May 2025 and today (not sure when) 

 

But here's the test I did:

#01. Create a gateway, as shown, is update to latest version available 

 

#02. Added a Key Vault reference, checked the "Allow this Azure Key Vault reference to be utilized with either on-prem data gateways..."  as shown below.

 

#03. Create an on-prem connection to my local SQL Server (confirmed that using User/Psw worked) and then, change the connection to use my azure key vault reference... but I'm getting the error  "Unable to update connection credentials. DMTS_KeyVaultNotFoundErrorCode"

Needless to say that I'm the admin/owner of the key vault (via Azure's role Key Vault Administrator), gateway, azure key vault reference and connection  😅

 

It would be a GREAT DEAL OF HELP if any of you guys can reproduce the issue and let me know if you're getting the same result or is something specific on my environment. Thanks in advance. 

admin
  • tayloramy's avatar
    tayloramy
    5 months ago

    Hi svenchio, 

     

    I was able to reproduce this issue. 

    The keyvault just doesn't work for the gateway connection. 

     

    I hope Microsoft will fix this soon. 

4 Replies

  • tayloramy's avatar
    tayloramy
    Icon for Super User rankSuper User
    5 months ago

    Hi svenchio, 

     

    I was able to reproduce this issue. 

    The keyvault just doesn't work for the gateway connection. 

     

    I hope Microsoft will fix this soon. 

    • svenchio's avatar
      svenchio
      Icon for Super User rankSuper User
      5 months ago

      To be honest, I was kind of hoping you got a different result and me doing something wrong  😅 as i wanted to create an on-prem connection and use the key vault ref.!  Thanks tayloramy  I appreciate dearly you took the time to confirm! Kudos mate ... all the very best 😅 

       

       

      • tayloramy's avatar
        tayloramy
        Icon for Super User rankSuper User
        5 months ago

        Nope, no user error here unless you and I both did it. 

        I do wonder if this works with other gateway versions, something for me to test out at some point I guess. 

         

        I'm now also curious if this works for cloud connections that are using the gateway, or if that is also broken. 

         

        Lots to explore here! 

  • heihei's avatar
    heihei
    New Member
    2 months ago

    Hey!

     

    I was referenced to this thread and wanted to hop on to give my experience. I've been using this and have not had issues with this. 
    When you add a data source connection that uses the Azure Key Vault, it will try to fetch the key vault info via the gateway. Two points that you could check.

    1. If your Azure Key Vault has the networking configurations in place with the Firewall, your gateway will not be able to connect to it. 
    So what you can do is go to the Key Vault -> Settings -> Networking and in the Firewall section Add your client IP address. Add the on-prem gateway VM public IP address here.

    2. There could be something blocking outbound access from the on-prem gateway or that name resolution is not working properly. To trouble shoot, you could start by going onto your on-prem gateway, opening commandprompt and running:
    nslookup yourkeyvaultname.vault.azure.net