AZ-500
The Key Vault Lockout
Production is down. Your Azure Function App that powers the online booking system has stopped working. Application logs show: "Azure.Security.KeyVault.Secrets.SecretClient: Access denied. Caller is not authorized to perform action on resource." The Function App connects to Key Vault to retrieve the database connection string at startup. The Key Vault has not changed. But 3 hours ago, a new Terraform deployment updated the Function App's configuration. The deployment log shows the Managed Identity was "re-enabled" as part of the change. Customer bookings have been failing for 2 hours.
STEP 1 OF 5 — FREE PREVIEW
Diagnose the root cause. A Managed Identity was "re-enabled" during the Terraform deployment. Why would re-enabling a Managed Identity cause Key Vault access to fail even if the vault's access policies haven't changed?
🔒
Steps 2–5 require purchase
One-time purchase — lifetime access to all 5 AZ-500 labs
Sign in to purchase