---
title: "How should an Azure app cache Key Vault secrets without delaying rotation?"  
description: "How should an Azure app cache Key Vault secrets without delaying rotation?"  
author: "Raghunandan Mishra"  
published: 2026-10-12  
updated: 2026-10-12  
canonical: https://www.mindstick.com/forum/162264/how-should-an-azure-app-cache-key-vault-secrets-without-delaying-rotation  
category: "Azure Key Vault"  
tags: ["Azure Key Vault", "Secrets Management", "Credential Rotation"]  
reading_time: 1 minute  

---

# How should an Azure app cache Key Vault secrets without delaying rotation?

Our application reads secrets from Azure Key Vault at startup and caches them so it doesn’t make a vault request for every operation. That keeps normal traffic light, but it raises a practical question: if a secret is rotated, how quickly should the running app pick up the new value?

What caching pattern do you use for **Key Vault secrets** in long-running services? I’m weighing a short time-to-live against refresh-on-demand, and would like to hear how people handle rotation without creating request spikes or a window where instances use different credentials.


---

Original Source: https://www.mindstick.com/forum/162264/how-should-an-azure-app-cache-key-vault-secrets-without-delaying-rotation

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.