Hi We are facing the below issue and the Rancher nodes is stuck in Waiting for registering with kubernetes Kubelet failed to get node info: failed to get instance ID from cloud provider: Retriable: false, RetryAfter: 0s, HTTPStatusCode: 401, RawError: Retriable: false, RetryAfter: 0s, HTTPStatusCode: 401, RawError: azure.BearerAuthorizer#WithAuthorization: Failed to refresh the Token for request to https://management.azure.com/subscriptions/1797627d-40da-4b11-ad4b-e6015a9692a4/resourceGroups//providers/Microsoft.Compute/virtualMachines/prod-4?%24expand=instanceView&api-version=2019-07-01: StatusCode=401 -- Original Error: adal: Refresh request failed. Status Code = ‘401’. Response body: {“error”“invalid client”,“error description”“AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app ‘4fc4e74d-6e9c-4058-aae2-7772ca6b16a5’.\r\nTrace ID: 1b4fb5ca-4776-4f9b-8e71-a01dff0e5800\r\nCorrelation ID: 2198d06b-136a-493c-9228-caded4325d7d\r\nTimestamp: 2023-05-19 085324Z”,“error_codes”[7000215],“timestamp”“2023-05-19 085324Z”,“trace_id”“1b4fb5ca 4776 4f9b 8e71 a01dff0e5800”,“correlation id”“2198d06b-136a-493c-9228-caded4325d7d”,“error_uri”:“https://login.microsoftonline.com/error?code=7000215"} We have also created appropriate subscription in Azure Steps followed: 1. Created app registration 2. Azure added client secret 3. Assigned contributor role to subscription 4. Added cloud credential in Rancher with the secret value 5. Node has appropriate NSG assigned 6. The secrets is valid Somehow the Rancher is still taking the old secret and not fetching the updated one