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: src/content/docs/azure/services/virtual-network.mdx
+8-12Lines changed: 8 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,21 +10,17 @@ import AzureFeatureCoverage from "../../../../components/feature-coverage/AzureF
10
10
11
11
Azure Virtual Network (VNet) is the core networking service for isolating and routing Azure resources in private IP address spaces.
12
12
It lets you define address ranges, create subnets, and control network behavior for applications.
13
-
VNets are commonly used to model secure, segmented network topologies in cloud environments.
13
+
Virtual networks are commonly used to model secure, segmented network topologies in cloud environments. For more information, see [What is Azure Virtual Network?](https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-overview).
14
14
15
-
LocalStack for Azure allows you to build and test Virtual Network workflows in your local environment.
15
+
LocalStack for Azure provides a local environment to build and test Azure networking resources, such as virtual networks, private endpoints, and private DNS zones.
16
16
The supported APIs are available on our [API Coverage section](#api-coverage), which provides information on the extent of Virtual Network's integration with LocalStack.
17
17
18
18
## Getting started
19
19
20
20
This guide is designed for users new to Virtual Network and assumes basic knowledge of the Azure CLI and our `azlocal` wrapper script.
21
21
22
-
Start your LocalStack container using your preferred method.
23
-
Then start CLI interception:
22
+
Launch LocalStack using your preferred method. For more information, see [Introduction to LocalStack for Azure](/azure/getting-started/). Once the container is running, enable Azure CLI interception by running:
24
23
25
-
```bash
26
-
azlocal start_interception
27
-
```
28
24
29
25
### Create a resource group
30
26
@@ -51,7 +47,7 @@ az group create \
51
47
52
48
### Create and inspect a virtual network
53
49
54
-
Create a VNet with a `10.0.0.0/16` address space:
50
+
Create a virtual network with a `10.0.0.0/16` address space:
55
51
56
52
```bash
57
53
az network vnet create \
@@ -76,7 +72,7 @@ az network vnet create \
76
72
}
77
73
```
78
74
79
-
Get the VNet details:
75
+
Get the virtual network (VNet) details:
80
76
81
77
```bash
82
78
az network vnet show \
@@ -119,7 +115,7 @@ az network vnet subnet create \
119
115
}
120
116
```
121
117
122
-
Get and list subnets:
118
+
Retrieve new subnet details and list all VNet subnets
123
119
124
120
```bash
125
121
az network vnet subnet show \
@@ -147,7 +143,7 @@ az network vnet subnet list \
147
143
]
148
144
```
149
145
150
-
Create a second subnet, delete the first subnet, and list again:
146
+
Add a second subnet to the virtual network, remove the first , and relist all subnets:
151
147
152
148
```bash
153
149
az network vnet subnet create \
@@ -211,7 +207,7 @@ az network vnet update \
211
207
212
208
### Delete and verify
213
209
214
-
Delete the VNet and verify the list is empty:
210
+
Delete the VNet and validate that no virtual networks remain in the resource group:
0 commit comments