Skip to content

Commit 028cbd4

Browse files
authored
Update batch-tls-101-migration-guide.md
1 parent 53138b8 commit 028cbd4

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/batch/batch-tls-101-migration-guide.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ To support security best practices and remain in compliance with industry standa
1616

1717
TLS versions 1.0 and TLS 1.1 are known to be susceptible to BEAST and POODLE attacks and to have other Common Vulnerabilities and Exposures (CVE) weaknesses. TLS 1.0 and TLS 1.1 don't support the modern encryption methods and cipher suites that the Payment Card Industry (PCI) compliance standards recommends. Microsoft is participating in an industry-wide push toward the exclusive use of TLS version 1.2 or later.
1818

19-
If you have already migrated to use TLS 1.2 in your Batch client application, then this retirement does not apply to you. Only APIs requests which go directly to the Batch service via the data plane API (i.e., not management plane) are impacted. API requests at the management plane layer are routed through ARM and are subject to ARM TLS minimum version requirements, although we recommend for security best practices to migrate to TLS 1.2 across all client calls, if applicable.
19+
If you've already migrated to use TLS 1.2 in your Batch client application, then this retirement doesn't apply to you. Only APIs requests that go directly to the Batch service via the data plane API (that is, not management plane) are impacted. API requests at the management plane layer are routed through ARM and are subject to ARM TLS minimum version requirements. We recommend that you migrate to TLS 1.2 across Batch data plane or management plane API calls for security best practices, if applicable.
2020

2121
## Alternative: Use TLS 1.2
2222

@@ -40,11 +40,11 @@ For more information, see [TLS best practices for the .NET Framework](/dotnet/fr
4040

4141
- What happens if I don’t upgrade?
4242

43-
After the feature retirement from Azure Batch, your client application will not be able to communicate with Batch data plane API services unless you upgrade to TLS 1.2.
43+
After the feature retirement from Azure Batch, your client application won't be able to communicate with Batch data plane API services unless you upgrade to TLS 1.2.
4444

45-
- Will upgrading to TLS 1.2 affect the performance of my application?
45+
- Does upgrading to TLS 1.2 affect the performance of my application?
4646

47-
Upgrading to TLS 1.2 shouldn't affect your application's performance.
47+
Upgrading to TLS 1.2 generally shouldn't affect your application's performance.
4848

4949
- How do I know if I’m using TLS 1.0 or TLS 1.1?
5050

0 commit comments

Comments
 (0)