Azure Resource Manager will stop supporting protocols older than TLS 1.2

Thin Tran Van 20 Reputation points
2025-04-17T08:33:05.1433333+00:00

Hello,

We received the following message from Microsoft Japan:

日本マイクロソフトから、
 
Subscription 1: ****
Subscription 2: ****
 
以上のサブスクリプションにおいて、TLS 1.2 未満のリクエストが多数Azure Resource Managerに対して実行されている状況のようですが、以下リンクの通り、2025年3月1日までにTLS1.2より古いプロトコルのサポートが停止される予定となっているため、未対応の場合、下記リンクを参考にAzure を呼び出すクライアントで TLS 1.2 以降が使用されるようご対応をするように、とのメッセージが届きました。
Azure Resource Manager でサポートされている TLS バージョン - Azure Resource Manager | Microsoft Learn <https://learn.microsoft.com/ja-jp/azure/azure-resource-manager/management/tls-support>

We have checked all the resources in Subscription 1 and Subscription 2, and none of them are using protocols older than TLS 1.2. The browsers we use to access the Azure Portal also do not use protocols older than TLS 1.2.

We would like to ask the following two questions:

  1. To the extent possible, could you provide details on what kind of TLS 1.0 and/or TLS 1.1 communications were detected?
  2. Can we assume that there is currently no issue?

Thank you.

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
8,732 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Loganathan Thangamuthu 6 Reputation points
    2025-04-17T09:16:51.3133333+00:00

    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.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.