Reference:

Azure support for TLS 1.0 and TLS 1.1 will end by 31 October 2024

If I look at the metrics for “Successful Connections” and split them by TLS version for a user database, I see that 100% of the connections come with TLS version 1.2. I checked for “Failed Connections: System Errors” and “Failed Connections: User Errors”; both are zero.

For Azure SQL Database (PaaS), when I run this in the log analytics workspace, I see only the TLS columns populated for the MASTER database and not the user databases.

 AzureDiagnostics

|project TimeGenerated, ResourceId, Resource, client_tls_version_d, client_tls_version_name_s

Question: Why _client_tls_version_d, client_tls_version_name_s _columns are blank for the user database?

​Reference:
Azure support for TLS 1.0 and TLS 1.1 will end by 31 October 2024
If I look at the metrics for “Successful Connections” and split them by TLS version for a user database, I see that 100% of the connections come with TLS version 1.2. I checked for “Failed Connections: System Errors” and “Failed Connections: User Errors”; both are zero.
For Azure SQL Database (PaaS), when I run this in the log analytics workspace, I see only the TLS columns populated for the MASTER database and not the user databases.
 AzureDiagnostics
|project TimeGenerated, ResourceId, Resource, client_tls_version_d, client_tls_version_name_s
 
Question: Why _client_tls_version_d, client_tls_version_name_s _columns are blank for the user database?  Read More

​