Skip to content

Commit 7d5cc54

Browse files
committed
Updates.
1 parent 6761f9a commit 7d5cc54

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/storage/elastic-san/elastic-san-networking.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -171,15 +171,15 @@ To create a private endpoint for an Elastic SAN volume group, you must have the
171171

172172
If you create the endpoint from a user account that has all of the necessary roles and permissions required for creation and approval, the process can be completed in one step. If not, it requires two separate steps by two different users.
173173

174-
The Elastic SAN and the virtual network could be in different resource groups, regions and subscriptions, including subscriptions that belong to different Microsoft Entra tenants. In these examples, we're creating the private endpoint in the same resource group as the virtual network.
174+
The Elastic SAN and the virtual network could be in different resource groups, regions, and subscriptions, including subscriptions that belong to different Microsoft Entra tenants. In these examples, we're creating the private endpoint in the same resource group as the virtual network.
175175

176176
# [Portal](#tab/azure-portal)
177177

178178
You can create a private endpoint in the Azure portal either when you create a volume group or when modifying an existing volume group. You need an existing virtual network to create a private endpoint.
179179

180-
When creating or modifying a volume group, select the **Networking** page, then select **+ Create a private endpoint** under **Private endpoint connections**.
180+
When creating or modifying a volume group, select **Networking**, then select **+ Create a private endpoint** under **Private endpoint connections**.
181181

182-
Fill out the values in the menu that pops up, select the virtual network and the subnet that your applications will use.
182+
Fill out the values in the menu that pops up, select the virtual network and the subnet that your applications will use to connect. When you're done, select **Add**, and **Save**.
183183

184184
:::image type="content" source="media/elastic-san-create/elastic-san-private-endpoint.png" alt-text="Screenshot" lightbox="media/elastic-san-create/elastic-san-private-endpoint.png":::
185185

0 commit comments

Comments
 (0)