Update on retirement of TLS 1.0 and TLS 1.1 versions for Azure Services

Chad Rodriguez 391 Reputation points
2024-10-25T14:18:55.03+00:00

We have several '2012 Window servers' that have the Azure arc on them for purposes of security updates. Does anyone know if this article from Microsoft would impact our servers?

|Update on retirement of TLS 1.0 and TLS 1.1 versions for
Azure Services 
Following
the announcement on 10 November 2023, we’re continuing our transition to
requiring TLS 1.2 or later for all connections to Azure services.
To
minimize disruption to customer workloads, several services will continue
supporting TLS 1.0 and TLS 1.1 versions and complete their transitions by 31
August 2025 when TLS 1.2 or later will be required for all connections to
Azure services (unless explicitly indicated in service documentation). The list of remaining services
will be updated as transitions to TLS 1.2 or later complete. 
While the
Microsoft implementation of TLS 1.0 and TLS 1.1 versions isn’t known to have
vulnerabilities, TLS 1.2 or later versions provide improved security
features, including perfect forward secrecy and stronger cipher suites. 
Customers
still using TLS 1.0 or 1.1 should transition their workloads to TLS 1.2 or
later versions to ensure uninterrupted connectivity to Azure
services.  
Recommended action
To avoid
potential service disruptions, confirm that your
resources that interact with Azure services are using TLS 1.2 or later.
Then:

If
they're already exclusively using TLS 1.2 or later, you don't need to
take further action.
If
they still have a dependency on TLS 1.0 or 1.1, transition them
to TLS 1.2 or later.

Help and support
Read more
about the update to TLS 1.2. If
you have questions, get answers from community experts in Microsoft Q&A. If
you have a support plan and you need technical help, please create a support request.| | -------- | |Update on retirement of TLS 1.0 and TLS 1.1 versions for Azure Services  Following the announcement on 10 November 2023, we’re continuing our transition to requiring TLS 1.2 or later for all connections to Azure services. To minimize disruption to customer workloads, several services will continue supporting TLS 1.0 and TLS 1.1 versions and complete their transitions by 31 August 2025 when TLS 1.2 or later will be required for all connections to Azure services (unless explicitly indicated in service documentation). The list of remaining services will be updated as transitions to TLS 1.2 or later complete.  While the Microsoft implementation of TLS 1.0 and TLS 1.1 versions isn’t known to have vulnerabilities, TLS 1.2 or later versions provide improved security features, including perfect forward secrecy and stronger cipher suites.  Customers still using TLS 1.0 or 1.1 should transition their workloads to TLS 1.2 or later versions to ensure uninterrupted connectivity to Azure services.   Recommended action To avoid potential service disruptions, confirm that your resources that interact with Azure services are using TLS 1.2 or later. Then: If they're already exclusively using TLS 1.2 or later, you don't need to take further action. If they still have a dependency on TLS 1.0 or 1.1, transition them to TLS 1.2 or later. Help and support Read more about the update to TLS 1.2. If you have questions, get answers from community experts in Microsoft Q&A. If you have a support plan and you need technical help, please create a support request.|

Azure Arc
Azure Arc
A Microsoft cloud service that enables deployment of Azure services across hybrid and multicloud environments.
436 questions
0 comments No comments
{count} votes

Accepted answer
  1. Vinodh247 23,111 Reputation points MVP
    2024-10-27T10:44:43.7333333+00:00

    Hi Chad Rodriguez,

    Thanks for reaching out to Microsoft Q&A.

    Yes, the TLS 1.2 update could impact your Windows Server 2012 instances, particularly if they are using TLS 1.0 or TLS 1.1 for Azure-related communication. Windows Server 2012 does support TLS 1.2, but you might need to check and ensure that it’s enabled and configured for Azure connections. Here are the recommended steps:

    Verify Current TLS Configuration: Confirm that your servers are using TLS 1.2 for all Azure connections. Some legacy configurations default to TLS 1.0/1.1, even if TLS 1.2 is supported.

    Enable TLS 1.2: If TLS 1.2 is not enabled, apply the necessary registry changes to enforce it. Ensure that you have the required updates, as older builds may not support TLS 1.2 fully.

    Azure Arc Configuration: Check if any specific components or extensions used with Azure Arc require TLS 1.2 settings.

    After confirming these, your servers should remain compliant, avoiding any service disruptions by August 2025. If you have further concerns about compatibility, Microsoft’s support can help verify your configurations.

    https://learn.microsoft.com/en-us/azure/security/fundamentals/tls-transport-layer-security-protocol-support

    https://learn.microsoft.com/en-us/azure/azure-arc/overview

    Please feel free to click the 'Upvote' (Thumbs-up) button and 'Accept as Answer'. This helps the community by allowing others with similar queries to easily find the solution.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful

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.