All posts about configuring Virtual Network (vNet) in Azure, including Network Security Groups, User Defined Routes and subnetting.
I was recently working on a network design that was using a Hub and Spoke VNet Peering. The Hub network was connected to on-premises using VPN and this was transitioning to ExpressRoute. Once we transitioned to ExpressRoute we wanted to enforce a Default Route 0.0.0.0/0 back on-premises. This is done by advertising 0.0.0.0/0 to Azure […]
Read More »I had some scripts that I used to export all of the Network Security Groups (NSG) to CSV files. Recently I wanted to be able to use the exports of the NSGs to be able to restore the rule configuration for an NSG during some planned configuration changes. Additionally, this could be used to create […]
Read More »Service Endpoints are a new feature that allows for restricting access to Azure Services to Virtual Networks. By doing this you can remove public internet access to resources. Another benefit of Service Endpoints, is that traffic is automatically routed to the service when it is enabled. This greatly simplifies the design and implementation by removing […]
Read More »If you read the documentation on the Azure docs page it is not clear that if you have VNets configured in a Hub and Spoke design, it is possible for each spoke to be able to communicate with each other without requiring Network Virtual Appliance (NVA). This is possible using Gateway Transit and User Defined […]
Read More »VNet Peering in Azure enables 2 VNets within the same region to be connected directly through the Azure backbone fabric network. Previously there was a requirement to use a VNet gateway and establish a VNet-VNet VPN connection. One of the major downsides to this was the requirement to enable to use a VNet Gateway which […]
Read More »