Where should Azure DevOps pipeline secrets live?
Prefer no secret, then Azure Key Vault, then variable groups, then pipeline secret variables. How each scopes access and what log masking cannot protect.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
Prefer no secret, then Azure Key Vault, then variable groups, then pipeline secret variables. How each scopes access and what log masking cannot protect.
Microsoft advises against granting every pipeline access to an Azure DevOps service connection. What the option does and how to authorize pipelines singly.
The required template check makes a pipeline extend an approved YAML template before it can use a protected resource. How it works, and where it stops.
Fork pull request builds can run untrusted code. Azure DevOps has settings to withhold secrets, cut permissions, and require a team member comment first.
Azure DevOps has tenant and organization policies to restrict global and full scoped PATs, cap lifetime, limit creation, and auto revoke leaked tokens.
The Azure DevOps minimum reviewer policy has settings that decide whether approval means anything: self approval, most recent pusher, and vote resets.
Job authorization scope sets whether an Azure DevOps pipeline runs with a project or collection identity. Turn on the project limit and protect YAML repos.
Microsoft says Azure DevOps global PATs stop working on 1 December 2026. Find them, replace them with scoped tokens or Entra auth, and test before then.
Azure DevOps build validation can expire when the target branch moves. See the three expiration options and which to pick so merged code was really built.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.