Merge pull request #108147 from TimShererWithAquent/us1679050h

Change SSL to TLS per 1679050

Author: itechedit

articles/databox/data-box-deploy-copy-data-via-rest.md

@@ -89,7 +89,7 @@ Use the Azure portal to download certificate.
 
 ### Import certificate 
 
-Accessing Data Box Blob storage over HTTPS requires an SSL certificate for the device. The way in which this certificate is made available to the client application varies from application to application and across operating systems and distributions. Some applications can access the certificate after it is imported into the system's certificate store, while other applications do not make use of that mechanism.
+Accessing Data Box Blob storage over HTTPS requires a TLS/SSL certificate for the device. The way in which this certificate is made available to the client application varies from application to application and across operating systems and distributions. Some applications can access the certificate after it is imported into the system's certificate store, while other applications do not make use of that mechanism.
 
 Specific information for some applications is mentioned in this section. For more information on other applications, consult the documentation for the application and the operating system used.
 

articles/databox/data-box-heavy-deploy-copy-data-via-rest.md

@@ -95,7 +95,7 @@ Use the Azure portal to download certificate.
 
 ### Import certificate 
 
-Accessing Data Box Blob storage over HTTPS requires an SSL certificate for the device. The way in which this certificate is made available to the client application varies from application to application and across operating systems and distributions. Some applications can access the certificate after it is imported into the system’s certificate store, while other applications do not make use of that mechanism.
+Accessing Data Box Blob storage over HTTPS requires a TLS/SSL certificate for the device. The way in which this certificate is made available to the client application varies from application to application and across operating systems and distributions. Some applications can access the certificate after it is imported into the system’s certificate store, while other applications do not make use of that mechanism.
 
 Specific information for some applications is mentioned in this section. For more information on other applications, consult the documentation for the application and the operating system used.
 

articles/databox/data-box-troubleshoot-rest.md

@@ -23,7 +23,7 @@ This section details some of the issues faced when using Azure Storage Explorer
 |---------|---------|
 |Unable to retrieve child resources. The value for one of the HTTP headers is not in the correct format.|From the **Edit** menu, select **Target Azure Stack APIs**. <br>Restart Azure Storage Explorer.|
 |`getaddrinfo ENOTFOUND <accountname>.blob.<serialnumber>.microsoftdatabox.com` |Check that the endpoint name `<accountname>.blob.<serialnumber>.microsoftdatabox.com` is added to the hosts file at this path: <li>`C:\Windows\System32\drivers\etc\hosts` on Windows, or </li><li> `/etc/hosts` on Linux.</li>|
-|Unable to retrieve child resources. <br>Details: self-signed certificate |Import the SSL certificate for your device into Azure Storage Explorer: <li>Download the certificate from the Azure portal. For more information, go to [Download the certificate](data-box-deploy-copy-data-via-rest.md#download-certificate).</li><li>From the **Edit** menu, select **SSL Certificates** and then select **Import Certificates**.</li>|
+|Unable to retrieve child resources. <br>Details: self-signed certificate |Import the TLS/SSL certificate for your device into Azure Storage Explorer: <li>Download the certificate from the Azure portal. For more information, go to [Download the certificate](data-box-deploy-copy-data-via-rest.md#download-certificate).</li><li>From the **Edit** menu, select **SSL Certificates** and then select **Import Certificates**.</li>|
 
 ## Errors seen in AzCopy for Windows
 
@@ -32,7 +32,7 @@ This section details some of the issues faced when using AzCopy for Windows with
 |Error message  |Recommended action |
 |---------|---------|
 |AzCopy command appears to hang for a minute before displaying this error: <br>Failed to enumerate directory https://… The remote name could not be resolved `<accountname>.blob.<serialnumber>.microsoftdatabox.com`|Check that the endpoint name `<accountname>.blob.<serialnumber>.microsoftdatabox.com` is added to the hosts file at: `C:\Windows\System32\drivers\etc\hosts`.|
-|AzCopy command appears to hang for a minute before displaying this error: <br>Error parsing source location. The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.|Import the SSL certificate for your device into the system’s certificate store. For more information, go to [Download the certificate](data-box-deploy-copy-data-via-rest.md#download-certificate).|
+|AzCopy command appears to hang for a minute before displaying this error: <br>Error parsing source location. The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.|Import the TLS/SSL certificate for your device into the system’s certificate store. For more information, go to [Download the certificate](data-box-deploy-copy-data-via-rest.md#download-certificate).|
 
 
 ## Errors seen in AzCopy for Linux
@@ -42,7 +42,7 @@ This section details some of the issues faced when using AzCopy for Linux with D
 |Error message  |Recommended action |
 |---------|---------|
 |AzCopy command appears to hang for 20 minutes before displaying this error: <br>Error parsing source location `https://<accountname>.blob.<serialnumber>.microsoftdatabox.com/<cntnr>`. No such device or address|Check that the endpoint name `<accountname>.blob.<serialnumber>.microsoftdatabox.com` is added to the hosts file at: `/etc/hosts`.|
-|AzCopy command appears to hang for 20 minutes before displaying this error: <br>Error parsing source location… The SSL connection could not be established.|Import the SSL certificate for your device into the system’s certificate store. For more information, go to [Download the certificate](data-box-deploy-copy-data-via-rest.md#download-certificate).|
+|AzCopy command appears to hang for 20 minutes before displaying this error: <br>Error parsing source location… The SSL connection could not be established.|Import the TLS/SSL certificate for your device into the system’s certificate store. For more information, go to [Download the certificate](data-box-deploy-copy-data-via-rest.md#download-certificate).|
 
 ## Errors seen in Azure Storage library for Python
 
@@ -51,7 +51,7 @@ This section details some of the top issues faced during deployment of Data Box
 |Error message  |Recommended action |
 |---------|---------|
 |The value for one of the HTTP headers is not in the correct format. |The installed version of the Microsoft Azure Storage Library for Python is not supported by Data Box. See Azure Data Box Blob storage requirements for supported versions.|
-|… [SSL: CERTIFICATE_VERIFY_FAILED] …|Before running Python, set the REQUESTS_CA_BUNDLE environment variable to the path of the Base64-encoded SSL certificate file (see how to [Download the certificate](data-box-deploy-copy-data-via-rest.md#download-certificate)). <br>For example:<br>`export REQUESTS_CA_BUNDLE=/tmp/mycert.cer` <br>`python` <br>Alternately, add the certificate to the system’s certificate store and then set this environment variable to the path of that store. <br> For example, on Ubuntu: <br>`export REQUESTS_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt` <br>`python`|
+|… [SSL: CERTIFICATE_VERIFY_FAILED] …|Before running Python, set the REQUESTS_CA_BUNDLE environment variable to the path of the Base64-encoded TLS certificate file (see how to [Download the certificate](data-box-deploy-copy-data-via-rest.md#download-certificate)). <br>For example:<br>`export REQUESTS_CA_BUNDLE=/tmp/mycert.cer` <br>`python` <br>Alternately, add the certificate to the system’s certificate store and then set this environment variable to the path of that store. <br> For example, on Ubuntu: <br>`export REQUESTS_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt` <br>`python`|
 
 
 ## Common errors

articles/storsimple/storsimple-8000-diagnostics.md

@@ -319,7 +319,7 @@ hcs_startup                                   Stopped hcs_startup
 
 ### Network test
 
-This test validates the status of the network interfaces, ports, DNS and NTP server connectivity, SSL certificate, storage account credentials, connectivity to the Update servers, and web proxy connectivity on your StorSimple device.
+This test validates the status of the network interfaces, ports, DNS and NTP server connectivity, TLS/SSL certificate, storage account credentials, connectivity to the Update servers, and web proxy connectivity on your StorSimple device.
 
 #### Sample output of network test when only DATA0 is enabled
 
@@ -329,7 +329,7 @@ Here is a sample output of the 8100 device. You can see in the output that:
 * The DNS server configuration is valid and the device can connect via the DNS server.
 * The NTP server connectivity is also fine.
 * Ports 80 and 443 are open. However, port 9354 is blocked. Based on the [system network requirements](storsimple-system-requirements.md), you need to open this port for the service bus communication.
-* The SSL certification is valid.
+* The TLS/SSL certification is valid.
 * The device can connect to the storage account: _myss8000storageacct_.
 * The connectivity to Update servers is valid.
 * The web proxy is not configured on this device.

articles/storsimple/storsimple-8000-manage-storage-accounts.md

@@ -37,7 +37,7 @@ Storage accounts contain the credentials that the StorSimple device uses to acce
 On the **Storage account credentials** blade, all storage accounts that are created for the billing subscription are displayed in a tabular format containing the following information:
 
 * **Name** – The unique name assigned to the account when it was created.
-* **SSL enabled** – Whether the SSL is enabled and device-to-cloud communication is over the secure channel.
+* **SSL enabled** – Whether the TLS is enabled and device-to-cloud communication is over the secure channel.
 * **Used by** – The number of volumes using the storage account.
 
 The most common tasks related to storage accounts that can be performed are:
@@ -57,7 +57,7 @@ There are three types of storage accounts that can be used with your StorSimple
 
 ## Add a storage account
 
-You can add a storage account by providing a unique friendly name and access credentials that are linked to the storage account (with the specified cloud service provider). You also have the option of enabling the secure sockets layer (SSL) mode to create a secure channel for network communication between your device and the cloud.
+You can add a storage account by providing a unique friendly name and access credentials that are linked to the storage account (with the specified cloud service provider). You also have the option of enabling the Transport Layer Security (TLS) mode, previously known as Secure Sockets Layer (SSL) mode, to create a secure channel for network communication between your device and the cloud.
 
 You can create multiple accounts for a given cloud service provider. Be aware, however, that after a storage account is created, you cannot change the cloud service provider.
 
@@ -83,7 +83,7 @@ Use the following procedures to add Azure storage account credentials:
 
     3. In the **Storage account access key** text box, supply the primary Access Key for your Azure storage account credential. To get this key, go to the Azure Storage service, select your storage account credential, and click **Manage account keys**. You can now copy the primary access key.
 
-    4. To enable SSL, click the **Enable** button to create a secure channel for network communication between your StorSimple Device Manager service and the cloud. Click the **Disable** button only if you are operating within a private cloud.
+    4. To enable TLS, click the **Enable** button to create a secure channel for network communication between your StorSimple Device Manager service and the cloud. Click the **Disable** button only if you are operating within a private cloud.
 
     5. Click **Add**. You are notified after the storage account credential is successfully created.
 

articles/storsimple/storsimple-8000-remote-connect.md

@@ -198,11 +198,11 @@ Each of the preceding procedures, is described below.
 
 ### Connect to the device from the remote host
 
-Use Windows PowerShell and SSL to enter an SSAdmin session on your device from a remote host or client. The SSAdmin session maps to option 1 in the [serial console](storsimple-8000-windows-powershell-administration.md#connect-to-windows-powershell-for-storsimple-via-the-device-serial-console) menu of your device.
+Use Windows PowerShell and TLS to enter an SSAdmin session on your device from a remote host or client. The SSAdmin session maps to option 1 in the [serial console](storsimple-8000-windows-powershell-administration.md#connect-to-windows-powershell-for-storsimple-via-the-device-serial-console) menu of your device.
 
 Perform the following procedure on the computer from which you want to make the remote Windows PowerShell connection.
 
-#### To enter an SSAdmin session on the device by using Windows PowerShell and SSL
+#### To enter an SSAdmin session on the device by using Windows PowerShell and TLS
 1. Start a Windows PowerShell session as an administrator. If using a Windows 10 client, by default, the Windows Remote Management service is set to manual. You may need to start the service by typing:
 
     `Start-Service WinRM`
@@ -227,9 +227,9 @@ Perform the following procedure on the computer from which you want to make the
 5. Type:
    
      `Enter-PSSession $session`
-6. You will need to wait a few minutes, and then you will be connected to your device via HTTPS over SSL. You see a message that indicates you are connected to your device.
+6. You will need to wait a few minutes, and then you will be connected to your device via HTTPS over TLS. You see a message that indicates you are connected to your device.
    
-    ![PowerShell remoting using HTTPS and SSL](./media/storsimple-remote-connect/HCS_PSRemotingUsingHTTPSAndSSL.png)
+    ![PowerShell remoting using HTTPS and TLS](./media/storsimple-remote-connect/HCS_PSRemotingUsingHTTPSAndSSL.png)
 
 ## Next steps
 

articles/storsimple/storsimple-8000-system-requirements.md

@@ -77,7 +77,7 @@ Your StorSimple device is a locked-down device. However, ports need to be opened
 <sup>3</sup> The controller fixed IPs on your StorSimple device must be routable and able to connect to the Internet directly or via the configured web proxy. The fixed IP addresses are used for servicing the updates to the device and for garbage collection. If the device controllers cannot connect to the Internet via the fixed IPs, you will not be able to update your StorSimple device and garbage collection will not work properly.
 
 > [!IMPORTANT]
-> Ensure that the firewall does not modify or decrypt any SSL traffic between the StorSimple device and Azure.
+> Ensure that the firewall does not modify or decrypt any TLS traffic between the StorSimple device and Azure.
 
 
 ### URL patterns for firewall rules

articles/storsimple/storsimple-ova-best-practices.md

@@ -196,7 +196,7 @@ Use the following best practices when configuring ACRs for StorSimple volumes:
 Your StorSimple Virtual Array has data security and encryption features that ensure the confidentiality and integrity of your data. When using these features, it is recommended that you follow these best practices: 
 
 * Define a cloud storage encryption key to generate AES-256 encryption before the data is sent from your virtual array to the cloud. This key is not required if your data is encrypted to begin with. The key can be generated and kept safe using a key management system such as [Azure key vault](../key-vault/key-vault-overview.md).
-* When configuring the storage account via the StorSimple Manager service, make sure that you enable the SSL mode to create a secure channel for network communication between your StorSimple device and the cloud.
+* When configuring the storage account via the StorSimple Manager service, make sure that you enable the TLS mode to create a secure channel for network communication between your StorSimple device and the cloud.
 * Regenerate the keys for your storage accounts (by accessing the Azure Storage service) periodically to account for any changes to access based on the changed list of administrators.
 * Data on your virtual array is compressed and deduplicated before it is sent to Azure. We don't recommend using the Data Deduplication role service on your Windows Server host.
 

articles/storsimple/storsimple-ova-system-requirements.md

@@ -96,7 +96,7 @@ The following table lists the ports that need to be opened in your firewall to a
 <sup>1</sup> No inbound ports need to be opened on the public Internet.
 
 > [!IMPORTANT]
-> Ensure that the firewall does not modify or decrypt any SSL traffic between the StorSimple device and Azure.
+> Ensure that the firewall does not modify or decrypt any TLS traffic between the StorSimple device and Azure.
 > 
 > 
 

articles/storsimple/storsimple-virtual-array-deploy3-fs-setup.md

@@ -146,7 +146,7 @@ Perform the following steps in the [Azure portal](https://portal.azure.com/) to
 
     3. The location will be automatically populated based on the specified storage account. 
 
-    4. Enable SSL to ensure a secure network communication channel between the device and the cloud.
+    4. Enable TLS to ensure a secure network communication channel between the device and the cloud.
 
     5. Click **Add** to add this storage account credential.