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
@@ -17,9 +17,11 @@ This article covers configuring your Elastic SAN volume group to use private end
17
17
18
18
## Prerequisites
19
19
20
-
- If you're using Azure PowerShell, install the [latest Azure PowerShell module](/powershell/azure/install-azure-powershell)
21
-
- If you're using Azure CLI, install the [latest version](/cli/azure/install-azure-cli)
22
-
- Once you've installed the latest version, run `az extension add -n elastic-san` to install the extension for Elastic SAN
20
+
-[Deploy an Elastic SAN](elastic-san-create.md).
21
+
- Read through [Learn about networking configurations for Elastic SAN](elastic-san-networking.md) to understand whether private endpoints or service endpoints work better for your environment.
22
+
- If you're using Azure PowerShell, install the [latest Azure PowerShell module](/powershell/azure/install-azure-powershell).
23
+
- If you're using Azure CLI, install the [latest version](/cli/azure/install-azure-cli).
24
+
- Once you've installed the latest version, run `az extension add -n elastic-san` to install the extension for Elastic SAN.
A service endpoint enables secure connectivity to Elastic SAN from a subnet within your virtual network, without requiring a private IP. Virtual network service endpoints are public and accessible via the internet. You can [Configure virtual network rules](#configure-virtual-network-rules) to control access to your volume group when using storage service endpoints.
15
15
16
-
To use a service endpoint, you must configure [Network Policies](../../private-link/disable-private-endpoint-network-policy.md) on your Elastic SAN volume group to allow traffic from specific subnets. These network rules apply only to the public endpoint of the volume group — they are not used for private endpoints. In other words, traffic from a subnet using a service endpoint must be explicitly permitted through a configured rule at the volume group level. Once network access is configured for a volume group, the configuration is inherited by all volumes belonging to the group.
17
-
18
-
This article configures service endpoint connections to your Elastic SAN.
16
+
This article shows you how to configure service endpoint connections to your Elastic SAN.
19
17
20
18
## Prerequisites
21
19
20
+
-[Deploy an Elastic SAN](elastic-san-create.md).
21
+
- Read through [Learn about networking configurations for Elastic SAN](elastic-san-networking.md) to understand whether private endpoints or service endpoints work better for your environment.
22
22
- If you're using Azure PowerShell, install the [latest Azure PowerShell module](/powershell/azure/install-azure-powershell).
23
23
- If you're using Azure CLI, install the [latest version](/cli/azure/install-azure-cli).
24
24
- Once you've installed the latest version, run `az extension add -n elastic-san` to install the extension for Elastic SAN.
25
25
26
26
## Configure public network access
27
27
28
-
You enable public Internet access to your Elastic SAN endpoints at the SAN level. Enabling public network access for an Elastic SAN allows you to configure public access to individual volume groups over storage service endpoints. By default, public access to individual volume groups is denied even if you allow it at the SAN level. You must explicitly configure your volume groups to permit access from specific IP address ranges and virtual network subnets.
28
+
You enable public internet access to your Elastic SAN endpoints at the SAN level. Enabling public network access for an Elastic SAN allows you to configure public access to individual volume groups over storage service endpoints. By default, public access to individual volume groups is denied even if you allow it at the SAN level. You must explicitly configure your volume groups to permit access from specific IP address ranges and virtual network subnets.
29
29
30
30
You can enable public network access when you create an elastic SAN, or enable it for an existing SAN using the Azure PowerShell module or the Azure CLI.
31
31
@@ -88,7 +88,7 @@ Virtual network service endpoints are public and accessible via the internet. Yo
88
88
89
89
### [PowerShell](#tab/azure-powershell)
90
90
91
-
Use this sample code to create a storage service endpoint for your Elastic SAN volume group with PowerShell.
91
+
Use the following sample code to create a storage service endpoint for your Elastic SAN volume group.
Use this sample code to create a storage service endpoint for your Elastic SAN volume group with the Azure CLI.
109
+
Use the following sample code to create a storage service endpoint for your Elastic SAN volume group:
110
110
111
111
```azurecli
112
112
# Define some variables
@@ -139,46 +139,42 @@ You can manage virtual network rules for volume groups through the Azure portal,
139
139
140
140
### [PowerShell](#tab/azure-powershell)
141
141
142
-
- List virtual network rules.
143
-
- Enable service endpoint for Azure Storage on an existing virtual network and subnet.
144
-
- Add a network rule for a virtual network and subnet.
142
+
The following script lists enables the service endpoint for Azure Storage on an existing virtual network and subnet, then adds a network rule for a virtual network and subnet.
145
143
146
-
> [!TIP]
147
-
> To add a network rule for a subnet in a virtual network belonging to another Microsoft Entra tenant, use a fully qualified **VirtualNetworkResourceId** parameter in the form "/subscriptions/subscription-ID/resourceGroups/resourceGroup-Name/providers/Microsoft.Network/virtualNetworks/vNet-name/subnets/subnet-name".
144
+
> [!TIP]
145
+
> To add a network rule for a subnet in a virtual network belonging to another Microsoft Entra tenant, use a fully qualified **VirtualNetworkResourceId** parameter in the form "/subscriptions/subscription-ID/resourceGroups/resourceGroup-Name/providers/Microsoft.Network/virtualNetworks/vNet-name/subnets/subnet-name".
- List information from a particular volume group, including their virtual network rules.
175
-
- Enable service endpoint for Azure Storage on an existing virtual network and subnet.
176
-
- Add a network rule for a virtual network and subnet.
172
+
The following script lists information from a particular volume group, enables the service endpoint for Azure Storage on an existing virtual network and subnet, and adds a networking rule for a virtual network and subnet.
177
173
178
-
> [!TIP]
179
-
> To add a rule for a subnet in a virtual network belonging to another Microsoft Entra tenant, use a fully-qualified subnet ID in the form `/subscriptions/\<subscription-ID\>/resourceGroups/\<resourceGroup-Name\>/providers/Microsoft.Network/virtualNetworks/\<vNet-name\>/subnets/\<subnet-name\>`.
180
-
>
181
-
> You can use the **subscription** parameter to retrieve the subnet ID for a virtual network belonging to another Microsoft Entra tenant.
174
+
> [!TIP]
175
+
> To add a rule for a subnet in a virtual network belonging to another Microsoft Entra tenant, use a fully-qualified subnet ID in the form `/subscriptions/\<subscription-ID\>/resourceGroups/\<resourceGroup-Name\>/providers/Microsoft.Network/virtualNetworks/\<vNet-name\>/subnets/\<subnet-name\>`.
176
+
>
177
+
> You can use the **subscription** parameter to retrieve the subnet ID for a virtual network belonging to another Microsoft Entra tenant.
182
178
183
179
```azurecli
184
180
az elastic-san volume-group show -e $sanName -g $RgName -n $volumeGroupName
@@ -37,7 +37,7 @@ This article explains how to deploy and configure an Elastic SAN.
37
37
38
38
Increasing your SAN's base size will also increase its IOPS and bandwidth. Increasing additional capacity only increase its total size (base+additional) but won't increase IOPS or bandwidth, however, it's cheaper than increasing base.
39
39
40
-
1. Select **Next : Volume groups**.
40
+
1. Select **Next**.
41
41
42
42
:::image type="content" source="media/elastic-san-create/elastic-san-create-flow.png" alt-text="Screenshot of creation flow." lightbox="media/elastic-san-create/elastic-san-create-flow.png":::
Now that you've deployed an Elastic SAN, configure its networking using either [private endpoints](elastic-san-configure-private-endpoints.md) or [service endpoints](elastic-san-configure-service-endpoints.md).
282
+
Now that you've deployed an Elastic SAN, configure its networking using either [private endpoints](elastic-san-configure-private-endpoints.md) or [service endpoints](elastic-san-configure-service-endpoints.md).
0 commit comments