gMSA authentication fails in AppInsight for SQL when the account name contains special characters in Server and Application Monitor

When Testing credentials in AppInsights for SQL, test connection fails when using a gMSA account.

• The application status shows: Unable to establish SQL connection, check credentials.
• Application log is missing the following indication below:

DEBUG SolarWinds.APM.Probes.Management.WinRM.WinRmConnection - User account '<gMSA Account>' is identified as gMSA

• SQL-related logs show the account being used as a regular SQL login, for example integrated security=False together with user id=<fqdn>\<gmsa>$, followed by Login failed for user ....

• The issue can persist even after configuring WinRM only, Kerberos authentication, SPNs, delegation, and other documented gMSA prerequisites. Refer: https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-gmsa-for-apps-and-components.htm 

The SolarWinds Platform does not correctly recognize certain gMSA account names when the account contains special characters such as . or -. When that happens, the account is not processed through the gMSA authentication flow and the product instead falls back to the regular connection path, which results in the SQL login failure.

Resolution:

Workaround:

Use a different gMSA account whose name does not include special characters such as . or -, and then retest AppInsight for SQL.