Diagram

A sequence diagram showing a pipeline fetching a secret from Azure Key Vault at runtime, injecting it into an ephemeral variable, using it for a task, and then clearing it from memory so it is never persisted to disk or logs.
Injecting Secrets at Runtime
Pipeline tasks can inject secrets into the environment at the moment they are needed, keeping them out of source code entirely. When a pipeline runs, it requests the secret from Key Vault and loads it into a temporary variable that exists only for the duration of that pipeline execution. Once the task that needs the secret completes, the temporary variable is cleared from memory. This approach ensures secrets never get written to disk, logged, or stored in any persistent location where they could be discovered later. Teams should configure pipelines to use these ephemeral variables rather than hardcoding values in pipeline definitions or scripts.
Domain 4 of 4
3 practice questions
Practice this DomainLast updated