Skip to content
Permalink
Browse files

deploy

  • Loading branch information...
mbcrump committed Sep 8, 2019
1 parent b142d4e commit ff6d4bdc362fb579daf4b36be6c2217f137f3829
BIN +0 Bytes (100%) .DS_Store
Binary file not shown.
@@ -32,7 +32,7 @@ module.exports = {
{
title: 'Recently Added',
collapsable: false,
children: ['/blog/tip223','/blog/tip222','/blog/tip221','/blog/tip220','/blog/tip219','/blog/tip218','/blog/tip217','/blog/tip216','/blog/tip215','/blog/tip214','/blog/tip213','/blog/tip212','/blog/tip211','/blog/tip210']
children: ['/blog/tip224','/blog/tip223','/blog/tip222','/blog/tip221','/blog/tip220','/blog/tip219','/blog/tip218','/blog/tip217','/blog/tip216','/blog/tip215','/blog/tip214','/blog/tip213','/blog/tip212','/blog/tip211','/blog/tip210']
},
{
title: 'App Service',
BIN +0 Bytes (100%) .vuepress/public/.DS_Store
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@@ -0,0 +1,55 @@
---
type: post
title: "Tip 224 - How do I add a new CIDR to an existing Virtual Network"
excerpt: "How do I add a new CIDR to an existing Virtual Network"
tags: [azure, networking, VNet, CIDR, subnet]
share: true
date: 2019-09-08 02:00:00
---


::: tip

:bulb: Learn more : [Azure Virtual Networking](https://docs.microsoft.com/en-us/azure/networking/networking-overview/?WT.mc_id=docs-azuredevtips-micrum)

:::

This post was brought to you by **[Kumar Allamraju](https://twitter.com/kumarallamraju)**.

Azure Networking (VNet) allows customers to expand their Virtual Networkx by adding secondary IPv4 address ranges (CIDRs) to their VNets. Customers can add the secondary CIDR blocks to the VNet directly from the Azure Portal or by using the Azure CLI, Powershell.


#### Adding a new CIDR to an existing Virtual Network

1. Sign in to Azure Portal (https://portal.azure.com)
2. Navigate to Virtual Network blade. Choose your existing VNet. e.g. myvNet
3. Click on Settings >> Address Space
4. Add a new CIDR space e.g. I already have 10.0.0.0/16 configured as primary CIDR. So I add 192.168.0.0/16 as secondary CIDR block.
5. Click Save button to save the changes.

<img :src="$withBase('/files/azurevnetcidr-file1.jpg')">

6. Click on Settings >> Subnets, +Subnet
7. Add a new subnet e.g. Subnet Name: subnetB, enter a new subnet range that falls under the secondary CIDR space i.e. 192.168.0.0/24. Save the changes.

<img :src="$withBase('/files/azurevnetcidr-file2.jpg')">

8. Now provision a new virtual machine using the subnetB that was created above.

#### A sample architecture with one CIDR and two CIDRs is shown below

<img :src="$withBase('/files/azurevnetcidr-file3.jpg')">

#### Conclusion

Adding a new CIDR to an existing VNet has two key benefits. First, customers, who are launching more and more resources in their VNets, can now scale up their VNets on-demand. Second, customers no longer have to over-allocate private IPv4 space to their VNets - they can allocate only what is required at the VNet creation time, and later expand it as needed. With these benefits, this feature can make it significantly easier for customers to manage their private IPv4 address space. There is no additional charge to use this feature. This feature is available in all Azure regions.

* [Creating a Virtual Network using Azure Portal](https://docs.microsoft.com/en-us/azure/virtual-network/quick-create-portal?toc=%2fazure%2fnetworking%2ftoc.json?WT.mc_id=docs-azuredevtips-micrum)

* [Creating a Virtual Network using Azure CLI](https://docs.microsoft.com/en-us/cli/azure/network/vnet?view=azure-cli-latest#az-network-vnet-create?WT.mc_id=docs-azuredevtips-micrum)






0 comments on commit ff6d4bd

Please sign in to comment.
You can’t perform that action at this time.