you video title seems incorrect . should be create VM with Public Ip and without public IP ... how will you justify vnet creation with public subnet and private subnet ?
It does not cover almost 99% of the real architectures. There are backend servers, DBs and then load balancers/proxys in front of backend servers. Front end is optional in this case.
This video tells how to create a virtual machine in azure with and without a public ip.. There is nothing related to public and private subnet in azure.. Misleading..
very confusing to be honest.. not as per flow.. just some random click and trying to make connectivity. You need to make proper diagram and explain with packet flow.
superb ga cheparu, real time lo kuda oka document follow avali ani ardham avthundhi ,kontha valaki kuda
There is nothing called private and public subnets in azure like AWS. you can attach an internet or NAT gateway in AWS. so it is clearly a disconnect.
you video title seems incorrect . should be create VM with Public Ip and without public IP ... how will you justify vnet creation with public subnet and private subnet ?
How we will define public and private subnet which you have created
What we will we give in VM2 password? Or can we leave it as empty?
It does not cover almost 99% of the real architectures. There are backend servers, DBs and then load balancers/proxys in front of backend servers. Front end is optional in this case.
This video tells how to create a virtual machine in azure with and without a public ip.. There is nothing related to public and private subnet in azure.. Misleading..
how to create a windows 11 vnet
very confusing to be honest.. not as per flow.. just some random click and trying to make connectivity. You need to make proper diagram and explain with packet flow.
ok ok
durka durka chicken masala