
Walkthrough of using Key Vault secrets as variables for Terraform in Azure DevOps
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.
Markdown supported · ⌘↵ to post
Pax
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.