You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -15,7 +15,7 @@ Azure Files and Azure File Sync provide two main types of endpoints for accessin
15
15
- Public endpoints, which have a public IP address and can be accessed from anywhere in the world.
16
16
- Private endpoints, which exist within a virtual network and have a private IP address from within the address space of that virtual network.
17
17
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.
19
19
20
20
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).
21
21
@@ -32,7 +32,7 @@ Additionally:
32
32
- If you intend to use the Azure CLI, [install the latest version](/cli/azure/install-azure-cli).
33
33
34
34
## 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:
36
36
37
37
-**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.
38
38
-**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
138
138
139
139
Click **Review + create** to create the private endpoint.
140
140
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.
Copy file name to clipboardExpand all lines: includes/storage-files-networking-endpoints-public-disable-portal.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,12 +5,12 @@
5
5
author: khdownie
6
6
ms.service: storage
7
7
ms.topic: include
8
-
ms.date: 01/25/2021
8
+
ms.date: 11/01/2022
9
9
ms.author: kendownie
10
10
ms.custom: include file
11
11
---
12
12
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**.
13
13
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.
15
15
16
-
[](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":::
Copy file name to clipboardExpand all lines: includes/storage-files-networking-endpoints-public-restrict-portal.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,15 +5,15 @@
5
5
author: khdownie
6
6
ms.service: storage
7
7
ms.topic: include
8
-
ms.date: 01/25/2021
8
+
ms.date: 11/01/2022
9
9
ms.author: kendownie
10
10
ms.custom: include file
11
11
---
12
12
13
13
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**.
14
14
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**.
16
16
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.
18
18
19
-
[](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