Week 3
Core Azure Architechture
Azure Infrastructure Topology
Azure Regions
• Provides flexibility and scale.
• Preserves data residency.
• Select regions close to your users.
Worldwide there are 50+ regions representing
140 countries
Regions Services
Regional Pairs Region Region
North Central US South Central US
East US West US
• Each Azure region is paired with another West US 2 West Central US
region.
US East 2 Central US
Canada Central Canada East
• In an outage, recovery of one region is
North Europe West Europe
prioritized out of every pair.
UK West UK South
• Azure system updates are rolled out to Germany Central Germany Northeast
paired regions sequentially (not at the same South East Asia East Asia
time). East China North China
Japan East Japan West
Australia Southeast Australia East
India South India Central
Brazil South (Primary) South Central US
Adopting a Risk Model
Availability Options
Availability Sets
Fault Domain
A fault domain is a group of resources in a
data center rack that share the same
power and network. When a failure
occurs in a fault domain, all resources in
that fault domain are unavailable.
If the servers shared the same fault
domain, then they all would be affected
by the failure.
Update Domain
Availability Zones
Azure Management Scopes
Azure provides four management
scopes, listed as follows so that RBAC
and Azure Policy can be targeted at
those levels:
•Management group level
•Subscription level
•Resources group level
•Resource level
Resource Groups
Resource groups
(web + DB, VM, Storage) in one group
OR
Web and DB Virtual Storage
resource machine resource
group resource group group
Resource Group Characteristics
You should understand the following characteristics of resource groups:
• Resources must belong in a resource group and can only exist in one resource group but can be moved
between resource groups.
• Resources can interact with other resources in the same resource group, other resource groups, and other
subscriptions. Resources work at the data plane level, while resource groups and subscriptions work at the
management plane level.
• Resource groups don't have to use the same region; they can contain resources from other regions.
• Resource groups don't contain subscriptions, but subscriptions contain resource groups.
• Resource groups are not physical; they are a logical entity and not a billable item.
• Resource groups contain metadata about the resources they include.
Resource Characteristics cont…
• Resources inherit all permissions set at the resource group level they belong to by default.
• When adding new resources to a resource group, they inherit those permissions and any access assignments.
• When moving resources, they lose the permissions of the resource group they belonged to and inherit those
of the new resource group they are moved to.
• If access and permissions are assigned at the resource group level, all resources in that resource group can be
managed.
• Deleting a resource group will remove all resources within that resource group and not delete the
subscription or tenant.
• Because all resources are contained in the same resource group, it is easy to take action on all resources with
a single activity; all resources within the resource group inherit the access assignments and policies set at the
resource group.
• When assigning tags to a resource group, the resources in that resource group do not inherit those tags; you
would have to apply the tags individually to each resource in that group.
