TLS 1.0/1.1 in Azure Batch is retiring on March 31st, 2023

[azure-deprecation-automation]

TLS 1.0/1.1 in Azure Batch is retiring on March 31st, 2023

Deprecation ID: 8e364717-3f96-4798-893b-bfbe17a9f36c Deadline: Mar 31, 2023 Impacted Services:

• Azure Monitor

More information:

• Announcement
• Migration Guide

Notice

Here's the official report from Microsoft:

To follow security best practices and remain in compliance with industry standards toward the exclusive use of TLS version 1.2 or later, we’ll retire Azure Batch TLS 1.0/1.1 on 31 March 2023. Please transition to using Batch TLS 1.2 by that date.

Timeline

Phase	Date	Description
Announcement	Sep 30, 2022	Deprecation was announced
Deprecation	Mar 31, 2023	TLS 1.0/1.1 will no longer be supported.

Impact

TLS 1.0/1.1 in Azure Batch is retiring on March 31st, 2023 and migration to TLS 1.2 is required.

Required Action

A migration guide is provided here.

Here's the official report from Microsoft:

To avoid disruptions to your workflow, follow these steps to transition using Batch TLS 1.0/1.1 before 31 March 2023. After that, we will stop supporting Batch TLS 1.0/1.1. TLS 1.0/1.1 workflows will break, and our client application won’t work until you upgrade.

Contact

You can get in touch through the following options:

• Contact Azure support (link).
• Get answers from Microsoft Q&A (link).

[azure-deprecation-automation]

This issue is automatically managed and suggest to use GitHub Discussions to discuss this deprecation.