Why does it show "The Client Secret is invalid" in Site24x7 Azure monitoring?

Why does it show "The Client Secret is invalid" in Site24x7 Azure monitoring?

You may encounter the error message "Client Secret is invalid" in the Site24x7 web client while configuring or updating your Azure monitoring setup.
​
Cause: This error typically occurs when the client secret used to authenticate the Azure application is no longer valid. The following are common reasons for this issue.

1. The client secret is not mapped to the application

Ensure that the client secret you're using was generated for the same Entra ID application registered for Site24x7 monitoring. If the secret belongs to a different application, authentication will fail.

2. The client secret has been deleted in the Azure portal

If the client secret has been deleted from the Azure portal, it will become unusable. Site24x7 will be unable to authenticate the application with Azure, resulting in an "invalid" error.

3. The client secret has expired

Azure client secrets have an expiration period. If the secret has expired, it will no longer be valid for authentication. You can check the expiry date in the Azure portal, under Certificates & secrets for the application.

4. The client secret hasn't synced yet

If your case is not aligned with any of the above reasons, you may have just generated a new client secret. Sometimes, it may take a while for the newly generated client secret to be synced across Azure servers. This means you must wait for a few minutes after generating a new client secret. 
  1. Client Secret and Application ID
  2. How to update Client Secret