Skip to content

Commit dd3ad3c

Browse files
authored
Merge pull request #106944 from jeffpatt24/patch-7
Update storage-files-planning.md
2 parents 16d6472 + 06864df commit dd3ad3c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/storage/files/storage-files-planning.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ For customers migrating from on-premises file servers, or creating new file shar
4040
If you intend to use the storage account key to access your Azure file shares, we recommend using service endpoints as described in the [Networking](#networking) section.
4141

4242
## Networking
43-
Azure file shares are accessible from anywhere via the storage account's public endpoint. This means that authenticated requests, such as requests authorized by a user's logon identity, can originate securely from inside or outside of Azure. In many customer environments, an initial mount of the Azure file share on your on-premises workstation will fail, even though mounts from Azure VMs succeed. The reason for this is that many organizations and internet service providers (ISPs) block the port that SMB uses to communicate, port 445.
43+
Azure file shares are accessible from anywhere via the storage account's public endpoint. This means that authenticated requests, such as requests authorized by a user's logon identity, can originate securely from inside or outside of Azure. In many customer environments, an initial mount of the Azure file share on your on-premises workstation will fail, even though mounts from Azure VMs succeed. The reason for this is that many organizations and internet service providers (ISPs) block the port that SMB uses to communicate, port 445. To see the summary of ISPs that allow or disallow access from port 445, go to [TechNet](https://social.technet.microsoft.com/wiki/contents/articles/32346.azure-summary-of-isps-that-allow-disallow-access-from-port-445.aspx).
4444

4545
To unblock access to your Azure file share, you have two main options:
4646

@@ -168,4 +168,4 @@ In many cases, you will not be establishing a net new file share for your organi
168168
## Next steps
169169
* [Planning for an Azure File Sync Deployment](storage-sync-files-planning.md)
170170
* [Deploying Azure Files](storage-files-deployment-guide.md)
171-
* [Deploying Azure File Sync](storage-sync-files-deployment-guide.md)
171+
* [Deploying Azure File Sync](storage-sync-files-deployment-guide.md)

0 commit comments

Comments
 (0)