You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cloud-services/applications-dont-support-tls-1-2.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ This article describes how to enable the older TLS protocols (TLS 1.0 and 1.1) a
22
22
We understand that while we are taking steps to deprecate TLS 1.0 and TLS 1.1, our customers may need to support the older protocols and cipher suites until they can plan for their deprecation. While we don't recommend re-enabling these legacy values, we are providing guidance to help customers. We encourage customers to evaluate the risk of regression before implementing the changes outlined in this article.
23
23
24
24
> [!NOTE]
25
-
> Guest OS Family 6 release enforces TLS 1.2 by explicitly disabling TLS 1.0 and 1.1 and defining a specific set of cipher suites.
25
+
> Guest OS Family 6 release enforces TLS 1.2 by explicitly disabling TLS 1.0 and 1.1 and defining a specific set of cipher suites.For more information on Guest OS families see [Guest OS release news](https://docs.microsoft.com/azure/cloud-services/cloud-services-guestos-update-matrix#family-6-releases)
26
26
27
27
28
28
## Dropping support for TLS 1.0, TLS 1.1 and older cipher suites
@@ -338,7 +338,7 @@ Here is an example that shows both the worker role and web role.
338
338
339
339
## Step 4: Add the scripts to your Cloud Service
340
340
341
-
1) In Visual Studio, right-click on your WebRole
341
+
1) In Visual Studio, right-click on your WebRole or WorkerRole
342
342
2) Select **Add**
343
343
3) Select **Existing Item**
344
344
4) In the file explorer, navigate to your desktop where you stored the **TLSsettings.ps1** and **RunTLSSettings.cmd** files
@@ -348,7 +348,7 @@ Here is an example that shows both the worker role and web role.
348
348
349
349
To ensure the scripts are uploaded with every update pushed from Visual Studio, the setting *Copy to Output Directory* needs to be set to *Copy Always*
350
350
351
-
1) Under your WebRole, right-click on RunTLSSettings.cmd
351
+
1) Under your WebRole or WorkerRole, right-click on RunTLSSettings.cmd
352
352
2) Select **Properties**
353
353
3) In the properties tab, change *Copy to Output Directory* to *Copy Always"*
0 commit comments