Welcome back to Microsoft Azure Fundamentals.
This is Module three of the course Azure Global Infrastructure and SLA's
In this module will discuss as yours global footprint and the service guarantees it offers.
We'll start with an overview of azure data centers around the world and introduce some important terminology.
Then we'll talk about availability zones and how those relate to the global azure footprint.
After that, we'll define what a service level agreement is and talk about the fellas for different azure services.
And at the end, we'll learn how the for our own applications are impacted when using cloud services, as well as how to improve that
throughout, this module will introduce a lot of new terminology that you're going to need in your work with Azure.
Let's see how Azure is able to provide it services around the world.
Here's a map of Asia's global footprint.
It's available on azure website, and you can check it regularly for updates.
Each blue dot on the map represents the so called region.
A region is a geographical area with at least one but sometimes multiple data centers
as your controls the resources within the region to make sure that they're appropriately balanced. And at the time of this recording,
Azure has 48 available regions and six new ones. They've announced
two of the regions are not shown on the map because they are secret US government regions and are in undisclosed locations.
When you create a new resource in azure, you may be required to select a region.
Some services are available only in certain regions.
not all virtual machine sizes are available in every region.
G. C. D s VMS are available in west US to west US and east US two regions, but not in the other US regions.
There are also services that are global and do not require you to select a specific region.
Some examples are azure active directory as your traffic manager and as your DNS.
One important thing to note is that there are certain limits to the resources that you can create within a region.
If you reach this limit, you need to create a support ticket to extend the limit or create resources in another region where you have not reached the limit.
Some regions are special, though, and you can use them for building applications that need to meet certain compliance or legal requirements.
You may also not be allowed to deploy to those regions if you don't meet those compliance requirements.
The US government and Department of Defense regions are available for US government agencies and partners.
They are operated by personnel with higher clearance and have additional certifications.
China's regions are offered in partnership with a third party provider, and Microsoft doesn't maintain the data centers.
Germany's regions are available via Data Trustee model, where the data trustee is a Deutsche Telekom's company called T Systems.
This is the company that ensures that the data remains within Germany.
Why does Azure need data centers in so many regions?
Well, there are several reasons.
First, it allows you to bring your data and application closer to your customers.
It also provides better scalability and redundancy, and last but not least, it preserves the data residency for your users and helps you to stay compliant with local requirements
as your divides the world into four geography, ease
the Americas, Europe,
Asia Pacific and the Middle East and Africa.
A Geography is a discrete market with two or more regions that preserves residency and compliance boundaries.
So why is there yet another subdivision of the world?
Well, there are some legal and compliance reasons.
There are two main reasons for using geography ease.
They ensure that data residency and sovereignty requirements are honored within the geographical boundaries,
and they are fault tolerant to withstand complete region failure.
Speaking of data residency, one typical example is GDP are which we talked about in the previous videos.
The law requires that European citizens data is to remain on European soil.
Each azure region belongs to a single geography and has specific data residency compliance and service availability rules applied to it.
Another important thing to know about regions is that every region is paired with another region in the same geography.
This is called a region pair
Region pairs are helpful when you think about business continuity and disaster recovery plans.
Region Paris are directly connected and must be 300 miles away from each other.
This ensures that in the case of disaster, your workloads will continue to run even if one of the region's is down.
Some services offer automatic geo redundant data application using region pairs.
Additional advantages of region pairs are that in the case of extensive azure outage, one of the region's is prioritized to reduce the downtime.
Also planned updates are rolled out to regions with one at a time.
Additionally, data continues to reside within the same geography. If disaster occurs,
some examples of region pairs are East, US and West, US,
North Europe and Ireland, and West Europe in the Netherlands
and East Asia and South Asia.
One exception to the rule is Brazil South that is paired with South Central US.
In the next video, we'll look at what redundancy azure provides within a single region.