azure:qnd:azure_architecture [Whizzbang Tech Stuff]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Azure Architecture ======
  * [[https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/|Cloud Adoption Framework]]
  * [[https://docs.microsoft.com/en-us/azure/architecture/framework/|Microsoft Azure Well-Architected Framework]]
  * [[https://learn.microsoft.com/en-us/azure/architecture/reference-architectures/hybrid-networking/hub-spoke|Hub and Spoke Architecture]]

====== Landing Zones ======
  * [[https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/]]
  * [[https://docs.microsoft.com/en-us/azure/architecture/framework/security/design-governance-landing-zone]]
  * //Landing Zones// are pre-configured environments that cover all the core aspects of modern cloud native IT where you can host your workloads. They are a kind of a template that provides a baseline environment to facilitate the transition from on-prem to cloud while following best practices. Instead of a straight lift and shift Landing Zones are a way of rethinking IT resources and architecture in a cloud native way.
  * Landing Zones are implemented with //IaC// technologies like Blueprint or Terraform.

> A landing zone is an environment for hosting your workloads, pre-provisioned through code. 

> From a workload perspective, a landing zone refers to a prepared platform into which the application gets deployed. A landing zone implementation can have compute, data sources, access controls, and networking components already provisioned.

===== Deployment Methods =====
  * ARM Templates
      * [[https://github.com/Azure/Enterprise-Scale]]
  * Blueprints
  * Terraform

====== Virtual WAN ======
  * [[https://docs.microsoft.com/en-us/azure/virtual-wan/virtual-wan-about]]
  * [[https://docs.microsoft.com/en-us/azure/virtual-wan/virtual-wan-global-transit-network-architecture]]