Create a Client Secret
Confirm that a secret is required
Section titled “Confirm that a secret is required”Create a client secret only if the verified product authentication method needs one. Other credential types and their product support are not confirmed here.
Microsoft platform steps
Section titled “Microsoft platform steps”For the registered application, open Certificates & secrets → Client secrets → New client secret. Add a meaningful description and choose an expiration consistent with your organization’s policy.
Copy the secret value when it is displayed and store it in an approved secret manager. The secret ID is not the credential value. Record the expiration and connection owner without copying the value into documentation.
Handoff and renewal
Section titled “Handoff and renewal”Give the authorized HighLevel connection owner secure access to the value, rather than putting it in a Drive ID map, email body, screenshot, or workflow example. Plan rotation and test the updated connection before retiring the previous secret.
Microsoft documents credentials in its application and service principal guide. Product-specific secret support and field mapping require implementation review.
Related: credential handling and authentication errors.