Skip to content

Commit fd9e002

Browse files
authored
Merge pull request #289105 from mbender-ms/avnm-IPAM-updates-ARM
virtual network manager - Update IPAM docs
2 parents eb1287c + 3cfd1c8 commit fd9e002

File tree

2 files changed

+88
-1
lines changed

2 files changed

+88
-1
lines changed

articles/virtual-network-manager/how-to-manage-ip-addresses-network-manager.md

Lines changed: 88 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: mbender-ms
55
ms.author: mbender
66
ms.service: azure-virtual-network-manager
77
ms.topic: how-to
8-
ms.date: 10/08/2024
8+
ms.date: 10/25/2024
99
ms.custom: references_regions
1010
#customer intent: As a network administrator, I want to learn how to manage IP addresses with Azure Virtual Network Manager so that I can create and assign IP address pools to my virtual networks.
1111
---
@@ -139,6 +139,8 @@ In this step, you delegate permissions to other users to manage IP address pools
139139

140140
In this step, you create a virtual network with a nonoverlapping CIDR range by allowing IP address manager to automatically provide a nonoverlapping CIDR.
141141

142+
# [Azure Portal](#tab/azureportal)
143+
142144
1. In the Azure portal, search for and select **Virtual networks**.
143145
2. Select **+ Create**.
144146
3. On the **Basics** tab, enter the following information:
@@ -166,6 +168,91 @@ In this step, you create a virtual network with a nonoverlapping CIDR range by a
166168
8. Optionally create subnets referring to the selected pool.
167169
9. Select **Review + create** and then **Create** to create the virtual network.
168170

171+
# [Azure Resource Manager Template](#tab/armtemplate)
172+
173+
In this step, you create a virtual network with a nonoverlapping CIDR range using an Azure Resource Manager template.
174+
175+
1. Sign in to Azure and search for **Deploy a custom template**.
176+
2. In the **Custom deployment** window, select **Build your own template in the editor**.
177+
3. Copy the following template into the editor:
178+
179+
```json
180+
{
181+
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
182+
"contentVersion": "1.0.0.0",
183+
"parameters": {
184+
"virtualNetworkName": {
185+
"defaultValue": "virtual-network",
186+
"type": "String",
187+
"metadata": {
188+
"description": "VNet name"
189+
}
190+
},
191+
"location": {
192+
"defaultValue": "[resourceGroup().location]",
193+
"type": "String",
194+
"metadata": {
195+
"description": "Location for all resources."
196+
}
197+
},
198+
"poolResourceID": {
199+
"defaultValue": "/subscriptions/<subscriptionId>/resourceGroups/resourceGroupName/providers/Microsoft.Network/networkManagers/<networkManagerName>/ipamPools/<ipAddressPoolName>",
200+
"type": "String",
201+
"metadata": {
202+
"description": "Enter the Resource ID for your IP Address Pool. You can find this in the JSON View in the resource's overview window."
203+
}
204+
},
205+
"numberOfIPAddresses": {
206+
"defaultValue": "256",
207+
"type": "String",
208+
"metadata": {
209+
"description": "Enter the number of IP addresses for the virtual network."
210+
}
211+
}
212+
},
213+
"resources": [
214+
{
215+
"type": "Microsoft.Network/virtualNetworks",
216+
"apiVersion": "2024-01-01",
217+
"name": "[parameters('virtualNetworkName')]",
218+
"location": "[parameters('location')]",
219+
"properties": {
220+
"addressSpace": {
221+
"ipamPoolPrefixAllocations": [
222+
{
223+
"pool": {
224+
"id": "[parameters('poolResourceID')]"
225+
},
226+
"numberOfIpAddresses": "[parameters('numberOfIPAddresses')]"
227+
}
228+
]
229+
}
230+
}
231+
}
232+
]
233+
}
234+
235+
```
236+
237+
4. In the **Custom deployment** windows, enter or select the following information:
238+
239+
| **Field** | **Description** |
240+
| --- | --- |
241+
| **Project details** | |
242+
| Subscription | Select your subscription. |
243+
| Resource group | Select the resource group for the virtual network. In this case, the example uses **resource-group**. |
244+
| **Instance details** | |
245+
| Region | Select the region for the virtual network. IP address pools must be in the same region as your virtual network in order to be associated. |
246+
| Virtual network name | Enter a name for the virtual network. The template will default to **virtual-network**. |
247+
| Location | Select the location for the virtual network. This will be the same as the region except all lower case and no spaces.</br>For example, if the region is **(US)westus2**, the location will be **westus2**. |
248+
249+
:::image type="content" source="media/how-to-manage-ip-addresses/custom-deployment-template.png" alt-text="Screenshot of custom deployment page with values.":::
250+
251+
> [!NOTE]
252+
> The **poolResourceID** parameter is the Resource ID for your IP Address Pool. You can find this in the JSON View in the resource's overview window.
253+
254+
5. Select **Review + create** and then **Create** to create the virtual network.
255+
169256
## Next steps
170257

171258
> [!div class="nextstepaction"]
52.3 KB
Loading

0 commit comments

Comments
 (0)