This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 87%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENG%3C/text%3E%3C/svg%3E)
In Azure, under Virtual Networks>company-vnet>Subnets we created 2 subnets (Subnet A and Subnet B). Still in company-vnet, under Address space, we then added those 2 newly created subnets to our company-vnet. These are not attached to any NSGs currently. These subnets are also attached to a storage account.
The question is, are these 2 newly created vnets exposed to the public?
Based on your question, you added subnets under a Vnet, then Azure routes network traffic between all subnets in a virtual network, by default. So by default, the subnets are exposed to the public depends on whether you assigned public IP to it.
Hope this helps
Hi sreejukg,
Sorry if this might sound like a silly question. Where on my vnet can I confirm if it is exposed or not? I only see private IP subnets in the vnet. In the storage account that the vnet is attached to, specifically under Firewall, I only see my public IP address.
If you added a public IP address to the subnet, It allows public IP address. as per the screenshot, you already assigned a public IP and it means, it can be accessed from internet. So to apply restrictions you must add NSG, otherwise your subnet is public.