Skip to content

Commit 3ddea74

Browse files
authored
Merge pull request #295722 from LouisBerner/v-loberner-ado-368852-feb-content-freshness-alpa-3
Revised the include for sku support, light edit.
2 parents 235ac6a + 547159d commit 3ddea74

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

articles/databox-online/azure-stack-edge-gpu-configure-tls-settings.yml

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -9,24 +9,24 @@ metadata:
99

1010
ms.service: azure-stack-edge
1111
ms.topic: how-to
12-
ms.date: 02/28/2025
12+
ms.date: 03/04/2025
1313
ms.author: alkohli
1414
title: |
1515
Configure TLS 1.2 on Windows clients accessing Azure Stack Edge Pro device
1616
introduction: |
17-
[!INCLUDE [applies-to-GPU-and-pro-r-and-mini-r-skus](../../includes/azure-stack-edge-applies-to-gpu-pro-r-mini-r-sku.md)]
17+
[!INCLUDE [applies-to-GPU-and-pro-r-skus](../../includes/azure-stack-edge-applies-to-gpu-pro-r-sku.md)]
1818
19-
If you use a Windows client to access your Azure Stack Edge Pro device, you are required to configure Transport Layer Security (TLS) 1.2 on your client. This article provides resources and guidelines to configure TLS 1.2 on your Windows client.
19+
If you use a Windows client to access your Azure Stack Edge Pro device, you're required to configure Transport Layer Security (TLS) 1.2 on your client. This article provides resources and guidelines to configure TLS 1.2 on your Windows client.
2020
2121
The guidelines provided here are based on testing performed on a client running Windows Server 2016.
2222
prerequisites:
2323
summary: |
2424
Before you begin, make sure that you have access to a Windows Server client that can connect to your Azure Stack Edge device. The client should be running Windows Server 2016 or later.
2525
procedureSection:
2626
- title: |
27-
Configure TLS 1.2 for current PowerShell session
27+
Configure TLS 1.2 for the current PowerShell session
2828
summary: |
29-
Use the following steps to configure TLS 1.2 on your client.
29+
Use the following steps to configure TLS 1.2 on your client:
3030
steps:
3131
- |
3232
Run PowerShell as administrator.
@@ -37,12 +37,12 @@ procedureSection:
3737
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
3838
```
3939
- title: |
40-
Configure TLS 1.2 on client
40+
Configure TLS 1.2 on the client machine
4141
summary: |
42-
To set system-wide TLS 1.2 for your environment, follow these steps:
42+
Use the following steps to set system-wide TLS 1.2 for your environment:
4343
steps:
4444
- |
45-
To enable TLS 1.2 on the clients, use the guidelines in these documents:
45+
To enable TLS 1.2 on the clients, use guidelines in the following articles:
4646
4747
- [General- how to enable TLS 1.2](/windows-server/security/tls/tls-registry-settings#tls-12)
4848
- [How to enable TLS 1.2 on clients](/configmgr/core/plan-design/security/enable-tls-1-2-client)
@@ -51,7 +51,7 @@ procedureSection:
5151
- |
5252
Configure [Cipher Suites](/windows-server/security/tls/tls-registry-settings#tls-12).
5353
- Specifically [Configuring TLS Cipher Suite Order](/windows-server/security/tls/manage-tls#configuring-tls-cipher-suite-order)
54-
- Make sure that you list your current cipher suites and prepend any missing from the following list:
54+
- Make sure to list your current cipher suites and prepend any missing from the following list:
5555
5656
* TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
5757
* TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

0 commit comments

Comments
 (0)