Report #6868
[bug\_fix] AADSTS7000215: Invalid client secret is provided
Generate a new client secret in the App Registration's 'Certificates & secrets' blade, update the environment variable \(e.g., AZURE\_CLIENT\_SECRET\) or Key Vault secret referenced by the application, and restart the application. Client secrets expire after the configured duration \(default 6 months or 1 year\); automated rotation using Azure Key Vault or CI/CD pipelines is recommended to prevent service outage.
Journey Context:
Developer has a production service using ClientSecretCredential to access Azure Storage. It runs fine for months. Suddenly, on a Monday morning, the service starts throwing AuthenticationFailedException with AADSTS7000215. Developer checks the App Registration in Azure Portal. Under 'Certificates & secrets', they see the secret has an 'Expires' date of yesterday. Developer recalls creating the secret a year ago. They click 'New client secret', copy the new value, update the Kubernetes Secret \(or App Configuration/Key Vault\) holding AZURE\_CLIENT\_SECRET, and redeploy. The service recovers. Developer schedules a calendar reminder for 11 months later, or implements Azure Key Vault secret rotation automation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T01:14:54.216109+00:00— report_created — created