---
title: "Discussion on \"Azure DevOps: Terraform variables with Azure Key Vault\" | Hashnode"
description: "Discussion on \"Azure DevOps: Terraform variables with Azure Key Vault\". Walkthrough of using Key Vault secrets as variables for Terraform in Azure DevOps"
url: "https://hashnode.com/posts/azuredevops-keyvault-terraformvariables/6110d74b528eff11aea8c1b5"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Azure DevOps: Terraform variables with Azure Key Vault](https://jamescook.dev/azuredevops-keyvault-terraformvariables?utm_source=hashnode&utm_medium=feed)

Walkthrough of using Key Vault secrets as variables for Terraform in Azure DevOps

Aug 9, 2021 · 3 min read · jamescook.dev  
Read the article

-   [#terraform](https://hashnode.com/tag/terraform)
-   [#devops](https://hashnode.com/tag/devops)
-   [#azure](https://hashnode.com/tag/azure)
-   [#security](https://hashnode.com/tag/security)
-   [#code](https://hashnode.com/tag/code)

## Written by

[James Cook](https://hashnode.com/@JamesCook)

@JamesCook · London, UK

  
[View profile](https://hashnode.com/@JamesCook)

Award-Winning Technology Executive Driving Platform, Risk & Scale

Executive technology leader responsible for platform reliability, cloud operations, security posture, and enterprise technology risk within an investor-backed fintech environment. I lead technology operations at the intersection of engineering execution, governance, and business outcomes — ensuring platforms are scalable, resilient, and trusted by investors, regulators, and clients. Currently VP of DevOps at InvestorFlow, where I focus on building board-ready technology operations, strengthening risk and resilience, and shaping long-term platform strategy to support growth and regulatory confidence.

## Responses 1

Markdown supported · ⌘↵ to post

[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.
