• Management groups > Subscruptions > Resource groups ( see 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 : External Link

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

• Most Azure networking relies on Virtual Hubs.
  • A virtual hub is essentially a VNet implemented with a group of Windows servers performing routing functions.
• 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.

• View NIC Route Tables:
  • Command: `az network nic show-effective-route-table`
  • Example from Webinar (Slide 18): Shows route table for a NIC.
  • Query: Can this functionality be replicated in OCI?

• Virtual hubs propagate routes and manage connectivity automatically.
  • Unlike AWS Transit Gateway, which requires manual static route configuration.
  • Query: How does OCI handle route propagation?
• 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).

• `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.