---
title: "Comment by Pax on \"Azure DevOps: Terraform variables with Azure Key Vault\" | Hashnode"
description: "Question: Did you allow &quot;public access from all networks&quot; on your key vault&#39;s networking config? Or did you use self-hosted agents, where the agen"
url: "https://hashnode.com/posts/azuredevops-keyvault-terraformvariables/6110d74b528eff11aea8c1b5/comment/65262c2890eb89e1e464f564"
---

[Discussion](https://hashnode.com/posts/azuredevops-keyvault-terraformvariables/6110d74b528eff11aea8c1b5)

Comment [Azure DevOps: Terraform variables with Azure Key Vault](https://hashnode.com/posts/azuredevops-keyvault-terraformvariables/6110d74b528eff11aea8c1b5)

[Pax](https://hashnode.com/@paxcodes)

[Oct 11, 2023](https://hashnode.com/posts/azuredevops-keyvault-terraformvariables/6110d74b528eff11aea8c1b5/comment/65262c2890eb89e1e464f564)

Question: Did you allow "public access from all networks" on your key vault's networking config?

Or did you use self-hosted agents, where the agent is in a virtual network that have access to the key vault?

I'm thinking those are the only 2 ways our pipeline can have access to our keyvault but I might be missing something.
