If you're trying to get your head around networking in Azure, I'll be writing some blog posts to try and simplify it all! Here's the first one on Virtual Networks and Subnets, and how we can manage them with Bicep: www.willvelida.com/posts/implem... #MVPBuzz
Implementing a basic Azure Virtual Network with Bicep
Azure Virtual Networks (or VNETs) are the fundamental building block for private networks in Azure. We can built Azure VNETs that are similar to on-prem networks, with the benefit of Azure infrastruct...
www.willvelida.com
January 13, 2025 at 3:57 AM
If you're trying to get your head around networking in Azure, I'll be writing some blog posts to try and simplify it all! Here's the first one on Virtual Networks and Subnets, and how we can manage them with Bicep: www.willvelida.com/posts/implem... #MVPBuzz
⚠️ Azure retira el acceso saliente por defecto en nuevas VNets el 31 de marzo.
Las VMs nuevas no tendrán internet sin configuración explícita.
Solución recomendada: NAT Gateway en tu plantilla Bicep.
Las VNets existentes no cambian.
#Azure #AzureNetworking #IaC
Las VMs nuevas no tendrán internet sin configuración explícita.
Solución recomendada: NAT Gateway en tu plantilla Bicep.
Las VNets existentes no cambian.
#Azure #AzureNetworking #IaC
March 9, 2026 at 11:43 PM
⚠️ Azure retira el acceso saliente por defecto en nuevas VNets el 31 de marzo.
Las VMs nuevas no tendrán internet sin configuración explícita.
Solución recomendada: NAT Gateway en tu plantilla Bicep.
Las VNets existentes no cambian.
#Azure #AzureNetworking #IaC
Las VMs nuevas no tendrán internet sin configuración explícita.
Solución recomendada: NAT Gateway en tu plantilla Bicep.
Las VNets existentes no cambian.
#Azure #AzureNetworking #IaC
I feel ya! I was there 18 months ago. vnets/subnets, private endpoints, dns links(?!?!), and firewall rules galore! When did devops engineers become the cloud <everything>?
October 24, 2024 at 8:38 PM
I feel ya! I was there 18 months ago. vnets/subnets, private endpoints, dns links(?!?!), and firewall rules galore! When did devops engineers become the cloud <everything>?
Global B2B SaaS service provider was experiencing the “wild west” of multi-cloud computing--1000s of #VPCs and #VNets and 100s of accounts, with Ops having no ability to detect new instances.
Learn how Netography Fusion® was the right choice to bring order to the chaos.
zurl.co/XsOzU
Learn how Netography Fusion® was the right choice to bring order to the chaos.
zurl.co/XsOzU
March 12, 2025 at 12:09 PM
Global B2B SaaS service provider was experiencing the “wild west” of multi-cloud computing--1000s of #VPCs and #VNets and 100s of accounts, with Ops having no ability to detect new instances.
Learn how Netography Fusion® was the right choice to bring order to the chaos.
zurl.co/XsOzU
Learn how Netography Fusion® was the right choice to bring order to the chaos.
zurl.co/XsOzU
🙌 Hooray! In September @yannick.reekmans.be is speaking at @collabdays.org in Finland.
His session will be all about how 𝗴𝗮𝗺𝗲 𝗰𝗵𝗮𝗻𝗴𝗶𝗻𝗴 VNets & Managed Identities are for improving security in Dataverse plug-ins.
collabdays.pulse.ly/zhtcvzofxy
#Qubix #CollabDays #Dataverse #VNets #ManagedIdentities
His session will be all about how 𝗴𝗮𝗺𝗲 𝗰𝗵𝗮𝗻𝗴𝗶𝗻𝗴 VNets & Managed Identities are for improving security in Dataverse plug-ins.
collabdays.pulse.ly/zhtcvzofxy
#Qubix #CollabDays #Dataverse #VNets #ManagedIdentities
August 5, 2025 at 8:33 AM
🙌 Hooray! In September @yannick.reekmans.be is speaking at @collabdays.org in Finland.
His session will be all about how 𝗴𝗮𝗺𝗲 𝗰𝗵𝗮𝗻𝗴𝗶𝗻𝗴 VNets & Managed Identities are for improving security in Dataverse plug-ins.
collabdays.pulse.ly/zhtcvzofxy
#Qubix #CollabDays #Dataverse #VNets #ManagedIdentities
His session will be all about how 𝗴𝗮𝗺𝗲 𝗰𝗵𝗮𝗻𝗴𝗶𝗻𝗴 VNets & Managed Identities are for improving security in Dataverse plug-ins.
collabdays.pulse.ly/zhtcvzofxy
#Qubix #CollabDays #Dataverse #VNets #ManagedIdentities
Managing Access to Multiple VRFs from Azure VNETs by Daniele Gaiulli #AzureExpressRoute #Azure https://techcommunity.microsoft.com/t5/azure-networking-blog/managing-access-to-multiple-vrfs-from-azure-vnets/ba-p/4382355?utm_source=bluesky&utm_medium=social&utm_campaign=azureweekly
Managing Access to Multiple VRFs from Azure VNETs | Microsoft Community Hub
The document outlines methodologies for managing access to multiple VRFs from Azure VNETs, detailing various scenarios and their respective solutions. It...
techcommunity.microsoft.com
February 24, 2025 at 5:25 PM
Managing Access to Multiple VRFs from Azure VNETs by Daniele Gaiulli #AzureExpressRoute #Azure https://techcommunity.microsoft.com/t5/azure-networking-blog/managing-access-to-multiple-vrfs-from-azure-vnets/ba-p/4382355?utm_source=bluesky&utm_medium=social&utm_campaign=azureweekly
Exciting news: Subnet peering is now available in all Azure regions!
This feature is accessible through the latest versions of:
- Azure CLI
- Bicep
- ARM Templates
- Terraform
- PowerShell
Portal support should be added soon
More details at techcommunity.microsoft.com/blog/azurene...
This feature is accessible through the latest versions of:
- Azure CLI
- Bicep
- ARM Templates
- Terraform
- PowerShell
Portal support should be added soon
More details at techcommunity.microsoft.com/blog/azurene...
Subnet Peering | Microsoft Community Hub
The Basics: VNET Peering
Virtual Networks in Azure can be connected through VNET Peering. Peered VNETs become one routing domain, meaning that the entire IP...
techcommunity.microsoft.com
March 28, 2025 at 7:49 PM
Exciting news: Subnet peering is now available in all Azure regions!
This feature is accessible through the latest versions of:
- Azure CLI
- Bicep
- ARM Templates
- Terraform
- PowerShell
Portal support should be added soon
More details at techcommunity.microsoft.com/blog/azurene...
This feature is accessible through the latest versions of:
- Azure CLI
- Bicep
- ARM Templates
- Terraform
- PowerShell
Portal support should be added soon
More details at techcommunity.microsoft.com/blog/azurene...
Scenario 2:
Traffic between peered VNets fails.
✔️ Peering configured
❌ Custom UDR sends traffic elsewhere
👉 Answer: Route table misconfiguration.
Traffic between peered VNets fails.
✔️ Peering configured
❌ Custom UDR sends traffic elsewhere
👉 Answer: Route table misconfiguration.
February 13, 2026 at 3:42 PM
Scenario 2:
Traffic between peered VNets fails.
✔️ Peering configured
❌ Custom UDR sends traffic elsewhere
👉 Answer: Route table misconfiguration.
Traffic between peered VNets fails.
✔️ Peering configured
❌ Custom UDR sends traffic elsewhere
👉 Answer: Route table misconfiguration.
Quick video on the new subnet-level peering capability which is really useful when you don't want to peer the entire address space of vnets or maybe just want IPv6!
youtu.be/L4_k_HwCklE
#azure #cloud #microsoft #azureadministrator #azurearchitect #microsoftcloud #azurenetworking #networking
youtu.be/L4_k_HwCklE
#azure #cloud #microsoft #azureadministrator #azurearchitect #microsoftcloud #azurenetworking #networking
Subnet Level Peering Overview
YouTube video by John Savill's Technical Training
youtu.be
May 15, 2025 at 2:23 PM
Quick video on the new subnet-level peering capability which is really useful when you don't want to peer the entire address space of vnets or maybe just want IPv6!
youtu.be/L4_k_HwCklE
#azure #cloud #microsoft #azureadministrator #azurearchitect #microsoftcloud #azurenetworking #networking
youtu.be/L4_k_HwCklE
#azure #cloud #microsoft #azureadministrator #azurearchitect #microsoftcloud #azurenetworking #networking
You can now bring your own custom VNETs when deploying AKS Automatic clusters! In this video, I show you how you can deploy AKS Clusters with VNETs using Bicep: youtu.be/NY28RELKVCs?... #MVPBuzz #AKS #Kubernetes #Azure
Creating an AKS Automatic cluster with custom VNET in Bicep
YouTube video by Will Velida
youtu.be
February 20, 2025 at 8:41 PM
You can now bring your own custom VNETs when deploying AKS Automatic clusters! In this video, I show you how you can deploy AKS Clusters with VNETs using Bicep: youtu.be/NY28RELKVCs?... #MVPBuzz #AKS #Kubernetes #Azure
After March 31, 2026, new Azure VNets used with Windows 365 Azure Network Connection will lack default outbound internet access, requiring explicit outbound connectivity setup (e.g., NAT Gateway) to avoid provisioning failures. Existing VNets and Microsoft hosted network deployments are unaffecte...
MC1239171: Plan for Change: Windows 365 Azure Network Connection deployments connected to new VNets
After March 31st, 2026, newly created Azure Virtual Networks (VNets) will no longer include default outbound internet access.
Windows 365 customers who deploy Cloud PCs using an Azure Network Connection (ANC) connected to a VNet created on or after this date must explicitly configure outbound connectivity for the Cloud PCs.
Windows 365 deployments using Microsoft hosted network (MHN) are not affected.
## How will this affect your organization?
If your organization deploys Cloud PCs using an Azure Network Connection that is connected to a VNet created on or after March 31, 2026:
* New VNets will default to private subnets with no outbound internet access.
* Without an explicitly configured outbound connectivity method (such as a NAT Gateway), Cloud PC provisioning will fail.
* ANCs using existing VNets created through March 31, 2026, are not impacted and will continue to function with their current outbound configuration.
* Deployments using Microsoft hosted network (MHN) require no changes.
This change only applies when new VNets are created for Azure Network Connection after March 31, 2026. Existing provisioning policies that use VNets created before this date will continue to work as expected.
## What you need to do to prepare
Admins should review their Windows 365 deployment approach and ensure internal teams, including help desks and support staff are aware of this change.
Recommended actions:
* Use Microsoft hosted network (MHN) where possible. MHN is the recommended deployment option for Windows 365 and includes fully managed outbound connectivity.
* If continuing to use Azure Network Connection, ensure all new VNets linked in new or existing ANCs include a supported outbound access method:
* NAT Gateway (recommended)
* Azure Standard Load Balancer
* Azure Firewall or a supported third-party Network Virtual Appliance (NVA)*
*NVAs that automatically scale may interrupt persistent connections such as RDP. A direct outbound method like NAT Gateway is preferred.
* Validate outbound connectivity to ensure Windows 365 service endpoints are reachable and ANC health checks succeed.
* Review deployment automation (ARM, Bicep, Terraform) to confirm it no longer relies on legacy default outbound access behavior.
## Compliance considerations
No compliance considerations identified, review as appropriate for your organization
## Additional Information
Azure Default Outbound Access Changes: Guidance for Windows 365 ANC Customers | Microsoft Community Hub
Azure updates | Microsoft Azure
blog.tophhie.cloud
February 27, 2026 at 1:00 AM
After March 31, 2026, new Azure VNets used with Windows 365 Azure Network Connection will lack default outbound internet access, requiring explicit outbound connectivity setup (e.g., NAT Gateway) to avoid provisioning failures. Existing VNets and Microsoft hosted network deployments are unaffecte...
One of the worst things about selfhosting is that, when you start doing it, no matter how much you read to be well informed, you will never have knowledge to have a proper setup/organization of things. Can be VNETs, VMs, folder structure, physical space in a shelf… Never good enough.
#selfhosted
#selfhosted
February 4, 2025 at 3:00 PM
One of the worst things about selfhosting is that, when you start doing it, no matter how much you read to be well informed, you will never have knowledge to have a proper setup/organization of things. Can be VNETs, VMs, folder structure, physical space in a shelf… Never good enough.
#selfhosted
#selfhosted
I had the pleasure of chatting with Ned and Kyler on Day Two DevOps one evening recently to discuss the basics of Azure networking, using my line "Azure Virtual Networks Do Not Exist". packetpushers.net/podcasts/day... #Azure #MVPBuzz
D2DO273: Azure VNets Don't Exist | Packet Pushers
Cloud networks aren't like traditional data center networks, so applying a traditional network design to the cloud probably isn't the best idea. On today's Day Two Cloud, guest Aidan Finn guides us th...
packetpushers.net
May 28, 2025 at 8:46 AM
I had the pleasure of chatting with Ned and Kyler on Day Two DevOps one evening recently to discuss the basics of Azure networking, using my line "Azure Virtual Networks Do Not Exist". packetpushers.net/podcasts/day... #Azure #MVPBuzz
Wrote up some learnings about Azure Vnets from a recent project that I think really should be the standard now. TL;DR is it's really not that hard to set up and definitely improves your security.
Exception is Service Bus which is $$$ to join a vnet, such a shame.
alexduggleby.com/blog/vnets-a...
Exception is Service Bus which is $$$ to join a vnet, such a shame.
alexduggleby.com/blog/vnets-a...
An Introduction to Azure Virtual Networks and Private Links
A personal website and blog by Alex Duggleby.
alexduggleby.com
April 14, 2025 at 2:15 PM
Wrote up some learnings about Azure Vnets from a recent project that I think really should be the standard now. TL;DR is it's really not that hard to set up and definitely improves your security.
Exception is Service Bus which is $$$ to join a vnet, such a shame.
alexduggleby.com/blog/vnets-a...
Exception is Service Bus which is $$$ to join a vnet, such a shame.
alexduggleby.com/blog/vnets-a...
Sprint Day 7: Azure networking fundamentals.
VNets create isolation, subnets organize traffic, and peering connects networks.
Peering doesn’t bypass NSGs or firewalls, security still applies.
#AZ104 #LearningInPublic
If you want, next up:
VNets create isolation, subnets organize traffic, and peering connects networks.
Peering doesn’t bypass NSGs or firewalls, security still applies.
#AZ104 #LearningInPublic
If you want, next up:
February 8, 2026 at 4:23 PM
Sprint Day 7: Azure networking fundamentals.
VNets create isolation, subnets organize traffic, and peering connects networks.
Peering doesn’t bypass NSGs or firewalls, security still applies.
#AZ104 #LearningInPublic
If you want, next up:
VNets create isolation, subnets organize traffic, and peering connects networks.
Peering doesn’t bypass NSGs or firewalls, security still applies.
#AZ104 #LearningInPublic
If you want, next up:
@liorbela.bsky.social
[New Post] 👉 Microsoft Azure Removes Default Internet Access for New Virtual Networks
www.anoopcnair.com/microsoft-az...
🔊 Starting March 31, 2026, New VNets Will Not Have Automatic Internet Access
#Azure #Windows365 #MicrosoftAzure #HTMDCommunity
[New Post] 👉 Microsoft Azure Removes Default Internet Access for New Virtual Networks
www.anoopcnair.com/microsoft-az...
🔊 Starting March 31, 2026, New VNets Will Not Have Automatic Internet Access
#Azure #Windows365 #MicrosoftAzure #HTMDCommunity
February 13, 2026 at 10:49 AM
@liorbela.bsky.social
[New Post] 👉 Microsoft Azure Removes Default Internet Access for New Virtual Networks
www.anoopcnair.com/microsoft-az...
🔊 Starting March 31, 2026, New VNets Will Not Have Automatic Internet Access
#Azure #Windows365 #MicrosoftAzure #HTMDCommunity
[New Post] 👉 Microsoft Azure Removes Default Internet Access for New Virtual Networks
www.anoopcnair.com/microsoft-az...
🔊 Starting March 31, 2026, New VNets Will Not Have Automatic Internet Access
#Azure #Windows365 #MicrosoftAzure #HTMDCommunity
ZureMap - an open-source Angular application that visualises Azure infrastructure as interactive diagrams. by George Petrakis #Azure github.com/natechsa/Zur...
GitHub - natechsa/ZureMap: ZureMap is an open-source Angular application that visualises Microsoft Azure infrastructure as interactive diagrams. Connect to your Azure subscriptions, scan resources, and explore VNets, subnets, VMs, storage, and more — with FinOps cost overlays, tag-based highlighting, and exportable architecture maps.
ZureMap is an open-source Angular application that visualises Microsoft Azure infrastructure as interactive diagrams. Connect to your Azure subscriptions, scan resources, and explore VNets, sub...
github.com
May 10, 2026 at 4:25 AM
ZureMap - an open-source Angular application that visualises Azure infrastructure as interactive diagrams. by George Petrakis #Azure github.com/natechsa/Zur...
AZ-104 Thursday question 👇
Two VNets are peered, but a VM in VNet-A can not reach a VM in VNet-B.
NSG rules allow the traffic.
What’s the most common thing engineers forget in this situation?
Hint: It’s not DNS.
#AZ104 #LearningInPublic
Two VNets are peered, but a VM in VNet-A can not reach a VM in VNet-B.
NSG rules allow the traffic.
What’s the most common thing engineers forget in this situation?
Hint: It’s not DNS.
#AZ104 #LearningInPublic
March 5, 2026 at 2:23 PM
AZ-104 Thursday question 👇
Two VNets are peered, but a VM in VNet-A can not reach a VM in VNet-B.
NSG rules allow the traffic.
What’s the most common thing engineers forget in this situation?
Hint: It’s not DNS.
#AZ104 #LearningInPublic
Two VNets are peered, but a VM in VNet-A can not reach a VM in VNet-B.
NSG rules allow the traffic.
What’s the most common thing engineers forget in this situation?
Hint: It’s not DNS.
#AZ104 #LearningInPublic
Standardizing network patterns across many VNets (without replatforming everything)Pattern Pack Private endpoints fail for one reason. DNS ownership is unclear. Continue reading on System Weakness »
#cybersecurity #site-reliability-engineer #cloud #microsoft-azure #cloud-computing
Origin | […]
#cybersecurity #site-reliability-engineer #cloud #microsoft-azure #cloud-computing
Origin | […]
Original post on systemweakness.com
systemweakness.com
March 13, 2026 at 5:36 PM
Standardizing network patterns across many VNets (without replatforming everything)Pattern Pack Private endpoints fail for one reason. DNS ownership is unclear. Continue reading on System Weakness »
#cybersecurity #site-reliability-engineer #cloud #microsoft-azure #cloud-computing
Origin | […]
#cybersecurity #site-reliability-engineer #cloud #microsoft-azure #cloud-computing
Origin | […]
Today's learning 💡 Private Endpoints generate a /32 default route that automatically propagates within their vnet and peered vnets. In hub-spoke architectures, this can inadvertently bypass firewalls or an NVA. To mitigate this, take a look at 'Network Policies for Private Endpoints'.
April 16, 2025 at 12:05 PM
Today's learning 💡 Private Endpoints generate a /32 default route that automatically propagates within their vnet and peered vnets. In hub-spoke architectures, this can inadvertently bypass firewalls or an NVA. To mitigate this, take a look at 'Network Policies for Private Endpoints'.
PSA: If you have two Azure App Services in the same App Service Plan, and each is connected to a separate VNet, ensure the VNets’ IP ranges don’t overlap, or else you’ll get cross-communication.
I spent months debugging Heisenbugs until I figured this out.
I spent months debugging Heisenbugs until I figured this out.
June 24, 2025 at 3:18 PM
PSA: If you have two Azure App Services in the same App Service Plan, and each is connected to a separate VNet, ensure the VNets’ IP ranges don’t overlap, or else you’ll get cross-communication.
I spent months debugging Heisenbugs until I figured this out.
I spent months debugging Heisenbugs until I figured this out.
Last week I was asked why our architecture was using VNets (the VPC on Azure), public and private subnets, with security groups and NACLs instead of simply relying on IP whitelisting for our internal components like SQL.
Thought of it as a joke at first, but it wasn't.
Thought of it as a joke at first, but it wasn't.
March 2, 2025 at 12:02 PM
Last week I was asked why our architecture was using VNets (the VPC on Azure), public and private subnets, with security groups and NACLs instead of simply relying on IP whitelisting for our internal components like SQL.
Thought of it as a joke at first, but it wasn't.
Thought of it as a joke at first, but it wasn't.