Based on the information provided, here’s how you can address the situation:
Details on TLS 1.0 and TLS 1.1 Communications:
Azure Resource Manager logs may provide insights into the specific requests using older TLS protocols. You can enable diagnostic settings for Azure Resource Manager to capture detailed logs and analyze them for any occurrences of TLS 1.0 or 1.1 communications.
Check if any legacy applications, scripts, or integrations are making API calls to Azure Resource Manager. These might be hardcoded to use older TLS versions.
If you’re unable to identify the source, consider reaching out to Microsoft Support for a detailed analysis of the detected communications.
**Assuming There’s No Issue**:
If you’ve verified that all resources and browsers are configured to use TLS 1.2 or later, and no legacy systems are in use, it’s likely that there’s no immediate issue on your end.
However, to ensure compliance and avoid disruptions, it’s recommended to monitor logs and confirm that all clients interacting with Azure are indeed using TLS 1.2 or higher.
For further guidance, you can refer to the Azure Resource Manager TLS support documentation or explore tools and methods to identify resources using older TLS versions, as outlined here.