Azure Networking
published: June 18, 2022
Intro
A
VNetenables you to glue and connect Azure resources between each other, over the internet and on-premises networks.
Types of communications
All resources in a VNet can communicate directly to the internet by default, this is only for outbound direction
To the internet
| Type | example | notes |
|---|---|---|
Public IP to VM | Does not scale as networks grow | |
Load Balancer | Port allocation needs to be declared upfront | |
NAT Gateway | Uses static public IPs for easy scaling of networks |
Between Azure resources
You have three options on this part.
| Type | example | notes |
|---|---|---|
Virtual Network | All resources inside a VNet can communicate between each other directly. The complete list can be found here | |
Virtual network service endpoint | Extend virutal network private address to other Azure services outside of their VNet | |
VNet Peering | Connect networks on the same or different Azure regions. |
Communicate with on-premises resources
Work in Progress...
Filter traffic
Work in Progress...
Route traffic
Work in Progress...
Summary
As you can see there are some pending items, I will update the cheatsheet as I go.
By the way, if you are on desktop, did you notice you can move the icons inside the diagrams? It took a while to understand and create a network force diagram using d3 js. I will probably create a post later about this.
More Posts
