Skip to content

Commit 8cbbf67

Browse files
authored
Merge pull request #216781 from khdownie/kendownie110122-3
Replacing screenshots for public endpoint restrictions
2 parents 6a7b2ae + a54f5e9 commit 8cbbf67

File tree

7 files changed

+14
-14
lines changed

7 files changed

+14
-14
lines changed

articles/storage/file-sync/file-sync-networking-endpoints.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Configuring Azure File Sync network endpoints | Microsoft Docs
2+
title: Configuring Azure File Sync network endpoints
33
description: Learn how to configure Azure File Sync network endpoints.
44
author: khdownie
55
ms.service: storage
66
ms.topic: how-to
7-
ms.date: 05/24/2021
7+
ms.date: 11/01/2022
88
ms.author: kendownie
99
ms.subservice: files
1010
ms.custom: devx-track-azurepowershell, devx-track-azurecli
@@ -15,7 +15,7 @@ Azure Files and Azure File Sync provide two main types of endpoints for accessin
1515
- Public endpoints, which have a public IP address and can be accessed from anywhere in the world.
1616
- Private endpoints, which exist within a virtual network and have a private IP address from within the address space of that virtual network.
1717

18-
For both Azure Files and Azure File Sync, the Azure management objects, the storage account and the Storage Sync Service respectively, control both the public and private endpoints. The storage account is a management construct that represents a shared pool of storage in which you can deploy multiple file shares, as well as other storage resources, such as blob containers or queues. The Storage Sync Service is a management construct that represents registered servers, which are Windows file servers with an established trust relationship with Azure File Sync, and sync groups, which define the topology of the sync relationship.
18+
For both Azure Files and Azure File Sync, the Azure management objects, the storage account and the Storage Sync Service respectively, control both the public and private endpoints. The storage account is a management construct that represents a shared pool of storage in which you can deploy multiple file shares, as well as other storage resources, such as blob containers or queues. The Storage Sync Service is a management construct that represents registered servers, which are Windows file servers with an established trust relationship with Azure File Sync, and sync groups, which define the topology of the sync relationship.
1919

2020
This article focuses on how to configure the networking endpoints for both Azure Files and Azure File Sync. To learn more about how to configure networking endpoints for accessing Azure file shares directly, rather than caching on-premises with Azure File Sync, see [Configuring Azure Files network endpoints](../files/storage-files-networking-endpoints.md?toc=%2fazure%2fstorage%2ffilesync%2ftoc.json).
2121

@@ -32,7 +32,7 @@ Additionally:
3232
- If you intend to use the Azure CLI, [install the latest version](/cli/azure/install-azure-cli).
3333

3434
## Create the private endpoints
35-
When you creating a private endpoint for an Azure resource, the following resources are deployed:
35+
When you are creating a private endpoint for an Azure resource, the following resources are deployed:
3636

3737
- **A private endpoint**: An Azure resource representing either the private endpoint for the storage account or the Storage Sync Service. You can think of this as a resource that connects your Azure resource and a network interface.
3838
- **A network interface (NIC)**: The network interface that maintains a private IP address within the specified virtual network/subnet. This is the exact same resource that gets deployed when you deploy a virtual machine, however instead of being assigned to a VM, it's owned by the private endpoint.
@@ -138,7 +138,7 @@ The **Configuration** blade allows you to select the specific virtual network an
138138

139139
Click **Review + create** to create the private endpoint.
140140

141-
You can test that your private endpoint has been setup correctly by running the following commands from PowerShell.
141+
You can test that your private endpoint has been set up correctly by running the following commands from PowerShell.
142142

143143
```powershell
144144
$privateEndpointResourceGroupName = "<your-private-endpoint-resource-group>"
@@ -319,7 +319,7 @@ if ($null -eq $dnsZone) {
319319
-ErrorAction Stop
320320
}
321321
```
322-
Now that you have a reference to the private DNS zone, you must create an A records for your Storage Sync Service.
322+
Now that you have a reference to the private DNS zone, you must create an A record for your Storage Sync Service.
323323

324324
```powershell
325325
$privateEndpointIpFqdnMappings = $privateEndpoint | `
@@ -488,7 +488,7 @@ then
488488
fi
489489
```
490490

491-
Now that you have a reference to the private DNS zone, you must create an A records for your Storage Sync Service.
491+
Now that you have a reference to the private DNS zone, you must create an A record for your Storage Sync Service.
492492

493493
```bash
494494
privateEndpointNIC=$(az network private-endpoint show \
272 KB
Loading
192 KB
Loading

includes/storage-files-networking-endpoints-public-disable-portal.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,12 @@
55
author: khdownie
66
ms.service: storage
77
ms.topic: include
8-
ms.date: 01/25/2021
8+
ms.date: 11/01/2022
99
ms.author: kendownie
1010
ms.custom: include file
1111
---
1212
Navigate to the storage account for which you would like to restrict all access to the public endpoint. In the table of contents for the storage account, select **Networking**.
1313

14-
At the top of the page, select the **Selected networks** radio button. This will un-hide a number of settings for controlling the restriction of the public endpoint. Check **Allow trusted Microsoft services to access this storage account** to allow trusted first party Microsoft services such as Azure File Sync to access the storage account.
14+
At the top of the page, select the **Enabled from selected virtual networks and IP addresses** radio button. This will un-hide a number of settings for controlling the restriction of the public endpoint. Select **Allow Azure services on the trusted services list to access this storage account** to allow trusted first party Microsoft services such as Azure File Sync to access the storage account.
1515

16-
[![Screenshot of the Networking blade with the appropriate restricts in place](media/storage-files-networking-endpoints-public-disable-portal/disable-public-endpoint-0.png)](media/storage-files-networking-endpoints-public-disable-portal/disable-public-endpoint-0.png#lightbox)
16+
:::image type="content" source="media/storage-files-networking-endpoints-public-disable-portal/disable-public-endpoint.png" alt-text="Screenshot of the Networking blade with the required settings to disable access to the storage account public endpoint." lightbox="media/storage-files-networking-endpoints-public-disable-portal/disable-public-endpoint.png":::

includes/storage-files-networking-endpoints-public-restrict-portal.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,15 +5,15 @@
55
author: khdownie
66
ms.service: storage
77
ms.topic: include
8-
ms.date: 01/25/2021
8+
ms.date: 11/01/2022
99
ms.author: kendownie
1010
ms.custom: include file
1111
---
1212

1313
Navigate to the storage account for which you would like to restrict the public endpoint to specific virtual networks. In the table of contents for the storage account, select **Networking**.
1414

15-
At the top of the page, select the **Selected networks** radio button. This will un-hide a number of settings for controlling the restriction of the public endpoint. Click **+Add existing virtual network** to select the specific virtual network that should be allowed to access the storage account via the public endpoint. This will require selecting a virtual network and a subnet for that virtual network.
15+
At the top of the page, select the **Enabled from selected virtual networks and IP addresses** radio button. This will un-hide a number of settings for controlling the restriction of the public endpoint. Select **+Add existing virtual network** to select the specific virtual network that should be allowed to access the storage account via the public endpoint. Select a virtual network and a subnet for that virtual network, and then select **Enable**.
1616

17-
Check **Allow trusted Microsoft services to access this storage account** to allow trusted first party Microsoft services such as Azure File Sync to access the storage account.
17+
Select **Allow Azure services on the trusted services list to access this storage account** to allow trusted first party Microsoft services such as Azure File Sync to access the storage account.
1818

19-
[![Screenshot of the Networking blade with a specific virtual network allowed to access the storage account via the public endpoint](media/storage-files-networking-endpoints-public-restrict-portal/restrict-public-endpoint-0.png)](media/storage-files-networking-endpoints-public-restrict-portal/restrict-public-endpoint-0.png#lightbox)
19+
:::image type="content" source="media/storage-files-networking-endpoints-public-restrict-portal/restrict-public-endpoint.png" alt-text="Screenshot of the Networking blade with a specific virtual network allowed to access the storage account via the public endpoint." lightbox="media/storage-files-networking-endpoints-public-restrict-portal/restrict-public-endpoint.png":::

0 commit comments

Comments
 (0)