Merge pull request #228515 from khdownie/kendownie022423

updating link to port 445 blocked

Author: prmerger-automator[bot]

articles/sap/workloads/businessobjects-deployment-guide-windows.md

@@ -160,7 +160,7 @@ To use Azure Files as a file store, you must mount it, which means you assign it
 
 **[A]** To mount the Azure file share, follow the steps in [Mount the Azure file share](../../storage/files/storage-how-to-use-files-windows.md#mount-the-azure-file-share).
 
-To mount an Azure file share on a Windows server, the SMB protocol requires TCP port 445 to be open. Connections will fail if port 445 is blocked. [Check if the firewall or ISP is blocking port 445](../../storage/files/files-troubleshoot.md#general-troubleshooting-first-steps).
+To mount an Azure file share on a Windows server, the SMB protocol requires TCP port 445 to be open. Connections will fail if port 445 is blocked. You can check if your firewall or ISP is blocking port 445 by using the `Test-NetConnection` cmdlet. See [Port 445 is blocked](../../storage/files/files-troubleshoot-smb-connectivity.md#cause-1-port-445-is-blocked).
 
 ## Configure a CMS database: Azure SQL
 

articles/storage/files/storage-how-to-use-files-windows.md

@@ -13,7 +13,7 @@ ms.custom: devx-track-azurepowershell
 # Mount SMB Azure file share on Windows
 [Azure Files](storage-files-introduction.md) is Microsoft's easy-to-use cloud file system. Azure file shares can be seamlessly used in Windows and Windows Server. This article discusses the considerations for using an Azure file share with Windows and Windows Server.
 
-In order to use an Azure file share via the public endpoint outside of the Azure region it is hosted in, such as on-premises or in a different Azure region, the OS must support SMB 3.x. Older versions of Windows that support only SMB 2.1 cannot mount Azure file shares via the public endpoint.
+In order to use an Azure file share via the public endpoint outside of the Azure region it is hosted in, such as on-premises or in a different Azure region, the OS must support SMB 3.x. Older versions of Windows that support only SMB 2.1 can't mount Azure file shares via the public endpoint.
 
 | Windows version | SMB version | Azure Files SMB Multichannel | Maximum SMB channel encryption |
 |-|-|-|-|
@@ -38,7 +38,7 @@ In order to use an Azure file share via the public endpoint outside of the Azure
 | Windows Server 2008 R2<sup>1</sup> | SMB 2.1 | No | Not supported |
 | Windows 7<sup>1</sup> | SMB 2.1 | No | Not supported |
 
-<sup>1</sup>Regular Microsoft support for Windows 7 and Windows Server 2008 R2 has ended. It is possible to purchase additional support for security updates only through the [Extended Security Update (ESU) program](https://support.microsoft.com/help/4497181/lifecycle-faq-extended-security-updates). We strongly recommend migrating off of these operating systems.
+<sup>1</sup>Regular Microsoft support for Windows 7 and Windows Server 2008 R2 has ended. It's possible to purchase additional support for security updates only through the [Extended Security Update (ESU) program](https://support.microsoft.com/help/4497181/lifecycle-faq-extended-security-updates). We strongly recommend migrating off of these operating systems.
 
 > [!Note]  
 > We always recommend taking the most recent KB for your version of Windows.
@@ -51,18 +51,18 @@ In order to use an Azure file share via the public endpoint outside of the Azure
 | Premium file shares (FileStorage), LRS/ZRS | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
 
 ## Prerequisites 
-Ensure port 445 is open: The SMB protocol requires TCP port 445 to be open. Connections will fail if port 445 is blocked. You can check if your firewall or ISP is blocking port 445 by using the `Test-NetConnection` cmdlet. See [Check if your firewall or ISP is blocking port 445](files-troubleshoot.md). To learn about ways to work around a blocked 445 port, see [Port 445 is blocked](files-troubleshoot-smb-connectivity.md#cause-1-port-445-is-blocked).
+Ensure port 445 is open: The SMB protocol requires TCP port 445 to be open. Connections will fail if port 445 is blocked. You can check if your firewall or ISP is blocking port 445 by using the `Test-NetConnection` cmdlet. See [Port 445 is blocked](files-troubleshoot-smb-connectivity.md#cause-1-port-445-is-blocked).
 
 ## Using an Azure file share with Windows
 To use an Azure file share with Windows, you must either mount it, which means assigning it a drive letter or mount point path, or [access it via its UNC path](#access-an-azure-file-share-via-its-unc-path).
 
-This article uses the storage account key to access the file share. A storage account key is an administrator key for a storage account, including administrator permissions to all files and folders within the file share you're accessing, and for all file shares and other storage resources (blobs, queues, tables, etc.) contained within your storage account. If this is not sufficient for your workload, [Azure File Sync](../file-sync/file-sync-planning.md) may be used, or you may use [identity-based authentication over SMB](storage-files-active-directory-overview.md).
+This article uses the storage account key to access the file share. A storage account key is an administrator key for a storage account, including administrator permissions to all files and folders within the file share you're accessing, and for all file shares and other storage resources (blobs, queues, tables, etc.) contained within your storage account. If this isn't sufficient for your workload, you can use [Azure File Sync](../file-sync/file-sync-planning.md) or [identity-based authentication over SMB](storage-files-active-directory-overview.md).
 
 A common pattern for lifting and shifting line-of-business (LOB) applications that expect an SMB file share to Azure is to use an Azure file share as an alternative for running a dedicated Windows file server in an Azure VM. One important consideration for successfully migrating an LOB application to use an Azure file share is that many applications run under the context of a dedicated service account with limited system permissions rather than the VM's administrative account. Therefore, you must ensure that you mount/save the credentials for the Azure file share from the context of the service account rather than your administrative account.
 
 ### Mount the Azure file share
 
-The Azure portal provides you with a script that you can use to mount your file share directly to a host. We recommend using this provided script.
+The Azure portal provides a script that you can use to mount your file share directly to a host. We recommend using this provided script.
 
 To get this script:
 
@@ -143,7 +143,7 @@ Select **Restore** to copy the contents of the entire directory recursively at t
  ![Restore button in warning message](./media/storage-how-to-use-files-windows/snapshot-windows-restore.png) 
 
 ## Enable SMB Multichannel
-Support for SMB Multichannel in Azure Files requires ensuring Windows has all the relevant patches applied to be up-to-date. Several older Windows versions, including Windows Server 2016, Windows 10 version 1607, and Windows 10 version 1507, require additional registry keys to be set for all relevant SMB Multichannel fixes to be applied on fully patched installations. If you are running a version of Windows that is newer than these three versions, no additional action is required.
+Support for SMB Multichannel in Azure Files requires ensuring Windows has all the relevant patches applied to be up-to-date. Several older Windows versions, including Windows Server 2016, Windows 10 version 1607, and Windows 10 version 1507, require additional registry keys to be set for all relevant SMB Multichannel fixes to be applied on fully patched installations. If you're running a version of Windows that is newer than these three versions, no additional action is required.
 
 ### Windows Server 2016 and Windows 10 version 1607
 To enable all SMB Multichannel fixes for Windows Server 2016 and Windows 10 version 1607, run the following PowerShell command: