hey guys welcome back in this video i'm going to show you how you can create a v-net in the azure
portal so i've already logged into the azure portal and before you can create a v-net you
must create a resource group so for this demo i've already created a resource group called resource
group 1 and i'm going to place my new vnet in this resource group all right i will now create a
v-net so in the azure home page i will either type virtual networks in the search box and select that
or if the shortcut is already cached in the home page you can select that as well i
will select virtual network shortcut and it will take me to the virtual network window
and you can click create or create virtual network i will click on create it will open up a create
virtual network window and under the basics tab i will select my pay as you go subscription specify
a resource group i will select resource group 1 specify a name for the vnet i will type vnet1
specify an azure region i will select east us and i will click next ip addresses
now under the ip address tab you need to specify an internal ipv4 address for the vnet in the cidr
format this ip address space for the vnet needs to be unique within your subscription and any
other networks that you connect to within azure on-premises network or any cross-cloud networks
there's already a default ipv for address space which is 10.0.0.16
and it can provide up to 65 536 ip addresses
the idea behind using a big subnet for your v-net is that you can divide that into smaller
ip subnets for example i can create this v-net with ipv4 address space of 10.0.0.0
16 and divide that into multiple subnets let's say i create a slash 24 subnet called
subnet 1 with the address range of 10.0.0.0.24
and another subnet called subnet 2 with the address range of 10.0.1.0
24 which is what we are going to talk about next but you can also add additional ipv4 address
space to your vnet for example i can add another ipv4 address space let's say 192.168.0.0
16 and divide that into multiple ip subnets i'm going to delete this i can also create a vnit
that is a dual stack meaning it supports both ipv6 address space as well as ipv4 address space
i can do that by simply selecting the check box for add ipv6 address space and specifying
the ipv6 address space for this demo i'm not going to add any ipv6 address space to this vnet
so i'm going to unselect this check box like i mentioned before within the ipv4 address space
of your v-net you need to create your different ip subnets for example you can see here
there's already a default subnet called default with the subnet address range of 10.0.0.0.24
and it can provide ip address space from 10.0.0.4 to 10.0.0.254
the other ip addresses in this subnet are reserved by azure platform they are 10.0.0.0 which is used
for network address 10.0.0.1 which is reserved by azure for the default gateway 10.0.0.2
and 10.0.0.3 are reserved to map the azure dns eyepiece to the ip address space of the subnet and
then you have 10.0.0.255 which is used for network broadcast address you can also rename the default
subnet from default to something else by clicking on it i will change the name to subnet one
and i am okay with the subnet address range which is 10.0.0.0.24 which is again
within the ipv4 address space of our vnet so i'm going to click on save to save the changes
and if you need to delete a subnet you simply select the subnet and click on remove subnet i
will now create another subnet called subnet 2 by clicking add subnet in the blade add subnet i will
specify the name of the new subnet as subnet 2. for the subnet address range i will type
10.0.1.0.24 as the ip address range for subnet 2 as it is within the ip address space of our
vnet one if you would like to provide internet or outbound connectivity to the
virtual machines or the azure resources that will be connected to this subnet then you can specify
a nat gateway for this subnet since i have no net gateway configured i will skip this
and if you would like to allow traffic to specific azure resources from this subnet such as azure sql
or any other azure services then you can select these service endpoints i'm not going to do that
for now so i will skip this and i'm going to click on add to add the new subnet so now we have two
subnets within this vnet by the way the routing between subnets will depend on the default routes
or you can define custom routes if required i will click on next security under the security tab you
can enable security features like bastion host ddos protection standard and firewall best in host
is a pass service that is provisioned inside your virtual network it provides a secure and seamless
rdp or ssh connectivity within the azure portal to your virtual machines using a web browser
when you connect via a bastion host your virtual machine do not need a public ip address for you to
connect from outside network such as the internet or use a traditional rdp or ssh tools to connect
your virtual machines from a private network ddos protection standard is a paid service that offers
enhanced ddos mitigation capabilities via adaptive tuning attack notification and telemetry data to
protect against the impacts of a ddos attack for all protected resources within this virtual
network but a basic ddos protection is integrated into the azure platform by default and at no
additional cost azure firewall is a managed cloud-based network security service that protects
your azure resources i'm not going to select any of this for this demo i will simply click on
next tags under the tags tab specify a name or value pair for tagging the resource i'm not going
to specify any name value pair for this demo so i'll simply click on next review plus create under
review plus create ensure that the validation has passed after reviewing your selections click on
create to create your new v-net now wait for a few minutes for the deployment to complete
all right you can see the deployment has succeeded now let me go back to the home
page and back on the virtual networks page our new virtual network vnet1 is listed here
i will click on my virtual network vnet1 and click on address space under settings and it will list
all the ipv4 address space of this virtual network in my case there's only one ipv4 address space
i'll click on subnets under settings and it will list all the subnets created for this
virtual network in my case there are two subnets created at the time of v-net creation alright this
concludes the step-by-step instructions on how to create a virtual network or a v-net using azure
portal i hope you enjoyed this video for more videos like these please subscribe to my channel