A cloud-based identity and access management service for securing user authentication and resource access
This problem has been solved. We updated the secret key in the coding and app environment variables value
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
"A configuration issue is preventing authentication - check the error message from the server for details. You can modify the configuration in the application registration portal. See https://aka.ms/msal-net-invalid-client for details. Original exception: 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 '35659fb7-8342-4495-a252-33328b735a7d'. Trace ID: bab89f85-6272-4a5f-91c9-5c1f4f740b00 Correlation ID: 76e96f96-e36a-4c43-b0a7-36676e4f6ff4 Timestamp: 2026-02-11 04:12:27Z"
A cloud-based identity and access management service for securing user authentication and resource access
This problem has been solved. We updated the secret key in the coding and app environment variables value
Hello Joby Chacko,
Thank you for the update, and I’m glad to hear the issue has been resolved.
The error AADSTS7000215: Invalid client secret provided usually occurs when the application is still using an old or incorrect client secret. After creating a new client secret in the App Registration, it is important to update the client secret value (not the secret ID) in all places where the application uses it, such as:
Also, make sure to restart the application or service after updating the secret so the new value is picked up.
As you confirmed, updating the secret in both the code and environment variables resolved the issue. This indicates the application was previously using the old secret value.
If you have any further questions, feel free to reach out.