A rotated Key Vault secret is correct, but App Service still uses the previous value
Editorial worked example. The participant profiles, discussion timeline and activity counts are illustrative; they are not a record of a customer incident. Scenario date: Feb 4, 2023. Technical guidance is based on the linked sources and was prepared for this publication.
65 reputation · 1h ago
AI-assisted content · Sources linked below.
A fictional application uses a Key Vault reference without a version in its URI. A new secret version has been created and is enabled. Requests from an authorized diagnostic client use the new value successfully, but the application behaves as if it has the old credential. Is this necessarily a permissions failure, and how should refresh behavior be checked?
Sources & further reading
- Environment
- Editorial worked example. See the question for the scenario and assumptions.
65 reputation · 1h ago
Could restarting only our background connection pool still leave the old secret in place?
1,100 reputation · 1h ago
Yes. Refreshing a pool does not necessarily refresh the platform-provided setting. Check both the platform reference and the application’s own cache or connection lifetime.