Client secret key is expired error occurs when deploying or terminating virtual machines
This article provides a solution for a "Client secret key is expired" error that occurs when you deploy or terminate virtual machines (VMs).
Note
Was this article helpful? Your input is important to us. Please use the Feedback button on this page to let us know how well this article worked for you or how we can improve it.
Symptoms
When you deploy or terminating VMs, you may encounter an error such as the following:
Azure.Cell.CreateLoadBalancerCreating load balancer (AADSTS7000222: The provided client secret keys are expired. Visit the Azure Portal to create new keys for your app, or consider using certificate credentials for added security:
https://docs.microsoft.com/azure/active-directory/develop/active-directory-certificate-credentials
Trace ID: <Trace ID> Correlation ID: <Correlation ID> Timestamp: <Date Time>
When you validate the credential in the CycleCloud portal, you see the following error message:
Invalid Azure credentials provided: AADSTS7000215: Invalid client secret is provided. Trace ID <Trace ID> Correlation ID: <Correlation ID> Timestamp: <Date Time>
Resolution
To resolve this issue, reset the client secret keys in the Azure portal.
Sign in to the Azure portal and navigate to the Microsoft Entra service.
Select the application name under the App Registrations.
Select Certificates & Secrets > New client secret to renew it.
After a client secret key is added, the new secret key value will be shown under the Key column.
Go to the CycleCloud portal and select Configure. Select the account in Cloud Provider Accounts, and then select Credentials > Edit. In the Edit Credential dialog, enter the password in Application Secret, and then select Validate. If the validation succeeds, select Save.
More information
Contact us for help
If you have questions or need help, create a support request, or ask Azure community support. You can also submit product feedback to Azure feedback community.