Reserved addresses in subnets does not take CIDR into account · Issue #61260 · MicrosoftDocs/azure-docs · GitHub
![I'm currently working on an assignment and one of the requirement is to have I'm currently working on an assignment and one of the requirement is to have](https://preview.redd.it/im-currently-working-on-an-assignment-and-one-of-the-v0-34qta6dre12a1.jpg?width=640&crop=smart&auto=webp&s=7e8719f97b6eb7521f1302a325ba6609d9aff822)
I'm currently working on an assignment and one of the requirement is to have "only 16 Ips in the subnet" i tried to get 16 Ip addresses available but it goes as
![Simply Calculate AWS Subnets CIDR Blocks [Create AWS subnets IPv4 range | Reserved 5 IP addresses] - YouTube Simply Calculate AWS Subnets CIDR Blocks [Create AWS subnets IPv4 range | Reserved 5 IP addresses] - YouTube](https://i.ytimg.com/vi/SYyVl3Hk9U0/maxresdefault.jpg)
Simply Calculate AWS Subnets CIDR Blocks [Create AWS subnets IPv4 range | Reserved 5 IP addresses] - YouTube
![PART 3 : MICROSOFT AZURE CREATING AND ADMINISTERING VIRTUAL NETWORK (VNET) | vGeek - Tales from real IT system Administration environment PART 3 : MICROSOFT AZURE CREATING AND ADMINISTERING VIRTUAL NETWORK (VNET) | vGeek - Tales from real IT system Administration environment](http://vcloud-lab.com/files/images/Microsoft-azure-virtual-network-vnet-diagram-designing-and-architect.png)