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
1. If you created a new virtual network and subnet in the previous step, then skip this step. If you have an existing virtual network you want to use, you must first create a [gateway subnet](../../vpn-gateway/vpn-gateway-about-vpn-gateway-settings.md#gwsub) on the virtual network before you can deploy a virtual network gateway.
95
-
96
-
If you haven't enabled public network access to the virtual network previously, the Microsoft.Storage service endpoint will need to be added to the virtual network subnet. This can take up to 15 minutes to complete, although in most cases it will complete much faster. Until this operation has completed, you won't be able to access the Azure file shares within that storage account, including via the VPN connection.
94
+
1. If you created a new virtual network and subnet in the previous step, then skip this step. If you have an existing virtual network you want to use, you must first create a [gateway subnet](../../vpn-gateway/vpn-gateway-about-vpn-gateway-settings.md#gwsub) on the virtual network before you can deploy a virtual network gateway.
97
95
98
96
To add a gateway subnet to an existing virtual network, run the following script. Be sure to replace `<your-subscription-id>`, `<resource-group>`, and `<virtual-network-name>` with your own values. The `$subnetAddressPrefix` parameter defines the IP address block for the subnet, so replace the IP address per your requirements.
99
97
@@ -150,7 +148,7 @@ To add a new or existing virtual network to your storage account, follow these s
150
148
az login
151
149
```
152
150
153
-
1. If you want to add a new virtual network and gateway subnet, run the following script. If you have an existing virtual network that you want to use, then skip this step and proceed to step 3. Be sure to replace `<your-subscription-id>`, `<storage-account-name>`, and `<resource-group>` with your own values. Replace `<virtual-network-name>` with the name of the new virtual network you want to create. The `--address-prefix` and `--subnet-prefix` parameters define the IP address blocks for the virtual network and the subnet, so replace those with your respective values. The virtual network will be created in the same region as the resource group.
151
+
1. If you want to add a new virtual network and gateway subnet, run the following script. If you have an existing virtual network that you want to use, then skip this step and proceed to step 3. Be sure to replace `<your-subscription-id>`, `<storage-account-name>`, and `<resource-group>` with your own values. Replace `<virtual-network-name>` with the name of the new virtual network you want to create. The `--address-prefix` and `--subnet-prefixes` parameters define the IP address blocks for the virtual network and the subnet, so replace those with your respective values. The virtual network will be created in the same region as the resource group.
154
152
155
153
```azurecli-interactive
156
154
# Set your subscription
@@ -162,7 +160,7 @@ To add a new or existing virtual network to your storage account, follow these s
162
160
vnetName="<virtual-network-name>"
163
161
# Virtual network gateway can only be created in subnet with name 'GatewaySubnet'.
164
162
subnetName="GatewaySubnet"
165
-
vnetAddressPrefix = "10.0.0.0/16" # Update this address per your requirements
163
+
vnetAddressPrefix="10.0.0.0/16" # Update this address per your requirements
166
164
subnetAddressPrefix="10.0.0.0/24" # Update this address per your requirements
167
165
168
166
# Create a virtual network and subnet
@@ -171,14 +169,12 @@ To add a new or existing virtual network to your storage account, follow these s
171
169
--name $vnetName \
172
170
--address-prefix $vnetAddressPrefix \
173
171
--subnet-name $subnetName \
174
-
--subnet-prefix $subnetAddressPrefix
172
+
--subnet-prefixes $subnetAddressPrefix
175
173
```
176
174
177
175
1. If you created a new virtual network and subnet in the previous step, then skip this step. If you have an existing virtual network you want to use, you must first create a [gateway subnet](../../vpn-gateway/vpn-gateway-about-vpn-gateway-settings.md#gwsub) on the virtual network before you can deploy a virtual network gateway.
178
176
179
-
If you haven't enabled public network access to the virtual network previously, the Microsoft.Storage service endpoint will need to be added to the virtual network subnet. This can take up to 15 minutes to complete, although in most cases it will complete much faster. Until this operation has completed, you won't be able to access the Azure file shares within that storage account, including via the VPN connection.
180
-
181
-
To add a gateway subnet to an existing virtual network, run the following script. Be sure to replace `<your-subscription-id>`, `<resource-group>` and `<virtual-network-name>` with your own values. The `--address-prefixes` parameter defines the IP address block for the subnet, so replace the IP address block as needed.
177
+
To add a gateway subnet to an existing virtual network, run the following script. Be sure to replace `<your-subscription-id>`, `<resource-group>`, and `<virtual-network-name>` with your own values. The `--address-prefixes` parameter defines the IP address block for the subnet, so replace the IP address block as needed.
182
178
183
179
```azurecli-interactive
184
180
# Set your subscription
@@ -206,7 +202,7 @@ To add a new or existing virtual network to your storage account, follow these s
206
202
az storage account update --resource-group $resourceGroup --name $storageAccount --default-action Deny
207
203
```
208
204
209
-
1. Enable a `Microsoft.Storage` service endpoint on the virtual network and subnet.
205
+
1. Enable a `Microsoft.Storage` service endpoint on the virtual network and subnet. This can take up to 15 minutes to complete, although in most cases it will complete much faster. Until this operation has completed, you won't be able to access the Azure file shares within that storage account, including via the VPN connection.
0 commit comments