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
Copy file name to clipboardExpand all lines: articles/storage/files/storage-files-configure-s2s-vpn.md
-12Lines changed: 0 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,8 +44,6 @@ If you don't have an existing network appliance, Windows Server contains a built
44
44
45
45
## Add virtual network to storage account
46
46
47
-
You need an existing Azure storage account with an Azure file share, and a virtual network in the same region as the storage account with a subnet named `GatewaySubnet` (required for the virtual network gateway deployment in the next step).
48
-
49
47
To add a new or existing virtual network to your storage account, follow these steps.
50
48
51
49
# [Portal](#tab/azure-portal)
@@ -227,8 +225,6 @@ To add a new or existing virtual network to your storage account, follow these s
227
225
228
226
## Deploy a virtual network gateway
229
227
230
-
You need a virtual network with a subnet named `GatewaySubnet` in the same region and subscription as your storage account, a public IP address resource (or you'll create one), and you must choose a gateway SKU (avoid Basic SKU if using IKEv2/route-based VPN); optionally, BGP configuration may apply if your organization requires it.
231
-
232
228
To deploy a virtual network gateway, follow these steps.
233
229
234
230
# [Portal](#tab/azure-portal)
@@ -322,8 +318,6 @@ To deploy a virtual network gateway, follow these steps.
322
318
323
319
### Create a local network gateway for your on-premises gateway
324
320
325
-
You need the public IP address of your on-premises VPN device, the on-premises network address ranges (for example, 192.168.0.0/16), and optionally BGP peer IP address information if BGP is required; the local network gateway should be created in the same Azure region as your virtual network gateway.
326
-
327
321
A local network gateway is an Azure resource that represents your on-premises network appliance. It's deployed alongside your storage account, virtual network, and virtual network gateway, but doesn't need to be in the same resource group or subscription as the storage account. To create a local network gateway, follow these steps.
You need a compatible on-premises VPN device (see [list of tested devices](../../vpn-gateway/vpn-gateway-about-vpn-devices.md)), the public IP address of your Azure virtual network gateway, and a shared key (PSK) for establishing the VPN connection.
374
-
375
367
The specific steps to configure your on-premises network appliance depend on the network appliance your organization has selected.
376
368
377
369
When configuring your network appliance, you'll need the following items:
@@ -387,8 +379,6 @@ When configuring your network appliance, you'll need the following items:
387
379
388
380
## Create the site-to-site connection
389
381
390
-
You need an existing Azure virtual network gateway, a local network gateway resource representing your on-premises VPN device, and a shared key (PSK) that matches the key configured on your on-premises VPN device; optionally, choose IKEv1 for policy-based VPN or IKEv2 for route-based VPN depending on your device.
391
-
392
382
To complete the deployment of a S2S VPN, you must create a connection between your on-premises network appliance (represented by the local network gateway resource) and the Azure virtual network gateway. To do this, follow these steps.
393
383
394
384
# [Portal](#tab/azure-portal)
@@ -481,8 +471,6 @@ az network vpn-connection show --name VNet1toSite1 --resource-group <resource-gr
481
471
482
472
## Mount Azure file share
483
473
484
-
You need an established site-to-site VPN connection between your on-premises network and Azure, an Azure file share in a storage account configured for virtual network access, and appropriate client credentials; OS-specific commands apply for Windows, macOS, Linux (NFS), or Linux (SMB).
485
-
486
474
The final step in configuring a S2S VPN is verifying that it works for Azure Files. You can do this by mounting your Azure file share on-premises. See the instructions to mount by OS here:
@@ -68,15 +69,7 @@ Azure Files is built for hybrid access and offers flexible deployment options, i
68
69
69
70
:::image type="content" source="media/windows-server-to-azure-files/azure-files-network-access.png" alt-text="Screenshot showing various access options for Azure file shares." lightbox="media/windows-server-to-azure-files/azure-files-network-access.png":::
70
71
71
-
Moving data from Windows file servers to Azure Files is easy, and you can do it in the background without interrupting user access. Just install Azure File Sync on your file server, connect to an Azure file share, and start the synchronization.
72
-
73
-
**Prerequisites:**
74
-
- An active Azure subscription
75
-
- An Azure storage account with an Azure file share
76
-
- Network connectivity between the server and Azure (internet, VPN, or ExpressRoute)
77
-
- A supported Windows Server with the Azure File Sync agent installed
78
-
79
-
**Verify:** Confirm the Azure file share is mounted and the Azure File Sync agent reports a **Healthy** status.
72
+
Moving data from Windows file servers to Azure Files is easy, and you can do it in the background without interrupting user access. Just install Azure File Sync on your file server, connect to an Azure file share, and start the synchronization.
80
73
81
74
When you migrate to Azure Files, none of your file path links need to break. You can [use DFS Namespaces](files-manage-namespaces.md) and redirect users to Azure Files. If you're extending an existing Windows file server to Azure using Azure File Sync, users continue to access their files using the same file paths.
0 commit comments