Configure subscriptions Flashcards
Things to know about regional pairs
Most Azure regions are paired with another region within the same geography to make a regional pair (or paired regions). Regional pairs help to support always-on availability of Azure resources used by your infrastructure.
Physical isolation
Azure prefers at least 300 miles of separation between datacenters in a regional pair. This principle isn’t practical or possible in all geographies. Physical datacenter separation reduces the likelihood of natural disasters, civil unrest, power outages, or physical network outages affecting both regions at once.
Platform-provided replication
Some services like Geo-Redundant Storage provide automatic replication to the paired region.
Region recovery order
During a broad outage, recovery of one region is prioritized out of every pair. Applications that are deployed across paired regions are guaranteed to have one of the regions recovered with priority.
Sequential updates
Planned Azure system updates are rolled out to paired regions sequentially (not at the same time). Rolling updates minimizes downtime, reduces bugs, and logical failures in the rare event of a bad update.
Data residency
Regions reside within the same geography as their enabled set (except for the Brazil South and Singapore regions).
Consider resource and region deployment
Plan the regions where you want to deploy your resources. For most Azure services, when you deploy a resource in Azure, you choose the region where you want your resource to be deployed.
Consider service support by region.
Research region and service availability. Some services or Azure Virtual Machines features are available only in certain regions, such as specific Virtual Machines sizes or storage types.
Consider services that don’t require regions.
Identify services that don’t need region support. Some global Azure services that don’t require you to select a region. These services include Microsoft Entra ID, Microsoft Azure Traffic Manager, and Azure DNS.
Consider exceptions to region pairing.
Check the Azure website for current region availability and exceptions. If you plan to support the Brazil South region, note this region is paired with a region outside its geography. The Singapore region also has an exception to standard regional pairing.
Consider benefits of data residency
Take advantage of the benefits of data residency offered by regional pairs. This feature can help you meet requirements for tax and law enforcement jurisdiction purposes.
Things to know about subscriptions
Every Azure cloud service belongs to a subscription.
Each subscription can have a different billing and payment configuration.
Multiple subscriptions can be linked to the same Azure account.
More than one Azure account can be linked to the same subscription.
Billing for Azure services is done on a per-subscription basis.
If your Azure account is the only account associated with a subscription, you’re responsible for the billing requirements.
Programmatic operations for a cloud service might require a subscription ID
Consider the types of Azure accounts required.
Determine the types of Azure accounts your users will link with Azure subscriptions. You can use a Microsoft Entra account or a directory that’s trusted by Microsoft Entra ID like a work or school account. If you don’t belong to one of these organizations, you can sign up for an Azure account by using your Microsoft Account, which is also trusted by Microsoft Entra ID.
Consider multiple subscriptions.
Set up different subscriptions and payment options according to your company’s departments, projects, regional offices, and so on. A user can have more than one subscription linked to their Azure account, where each subscription pertains to resources, access privileges, limits, and billing for a specific project.
Consider a dedicated shared services subscription
Plan for how users can share resources allocated in a single subscription. Use a shared services subscription to ensure all common network resources are billed together and isolated from other workloads. Examples of shared services subscriptions include Azure ExpressRoute and Virtual WAN.