DokuWiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
**[[https://cloud.google.com/free/docs/aws-azure-gcp-service-comparison]]** 

  * VNET : Azure virtual networks
  * VPN Network Gateway
  * EXPRESS ROUTE
  * Azure Firewall
  * Virtual HUb (~AWS TGW)
  * Cross VNET peering
  * Azure virtual NAT
  * Azure virtual WAN
  * Azure Load Balancer
    * Traffic Manager
  * Azure Application gateway
  * NVA in Virtual Hub - see [[https://learn.microsoft.com/en-us/azure/virtual-wan/about-nva-hub|Link]]
  * Resource manager (is the infrastructure tool ~ cloud formation)
  * Subscription (~account)
  * They have 'regional subnets' (like oci unlike aws)


----
=== Azure specific concepts ===
  * Management groups > Subscriptions > Resource groups ( see [[https://www.ibm.com/blog/microsoft-azure-resource-groups-introduction-and-best-practices/|External Link]] )
  * SKU (from the classical sku ) : Is the specific version or offering of a resource (vms, storage accounts, databases,.). Also used to define the characteristics and capabilities of different Azure resources and services



----
ACTIVE DIRECTORY IN AZURE - named ENTRA ID : [[https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/whatis#:~:text=Microsoft%20Entra%20ID%20is%20a,thousands%20of%20other%20SaaS%20applications.|External Link]]


===== Azure Networking Overview (Webinar: 2021-04-08) =====

===== General Notes =====
  * No IPv6 support.
  * Hub-and-spoke topology is supported.
  * VNet transit (similar to OCI’s VCN transit).

===== Virtual Hubs =====
  * Most Azure **networking** relies on **Virtual Hubs**.
    * A virtual hub is essentially a VNet implemented with a group of Windows servers performing routing functions.
    * [[https://learn.microsoft.com/en-us/azure/virtual-wan/about-virtual-hub-routing|External Link]]
  * **Virtual WANs and Hubs**:
    * Traffic traversing virtual hubs incurs charges based on **time**, not traffic volume (to be confirmed).
    * Virtual hubs bind different regions, offering cost efficiency.
    * Functionality is similar to AWS Transit Gateway but with worse performance.

===== Key Commands =====
  * **View NIC Route Tables**:
    * Command: `az network nic show-effective-route-table`
    * Example from Webinar (Slide 18): Shows route table for a NIC.

===== Route Propagation =====
  * Virtual hubs propagate routes and manage connectivity automatically.
    * Unlike AWS Transit Gateway, which requires manual static route configuration.
  * **Labels** (similar to MPLS Route Targets) can control propagation between route tables (Slide 20).
  * **AS-Prepending** is the only way to influence route preferences (similar to OCI).

===== Terraform Notes =====
  * `for_each` only works with dictionaries, not lists.
    * Lists must be converted for usage (Slides 27-28).
  * Terraform code for multiple VRFs:
    * Forwarding is separated but cannot duplicate IP blocks.