Merge pull request #219476 from v-edmckillop/patch-22

Update azure-ad-data-residency.md

Author: prmerger-automator[bot]

articles/active-directory/fundamentals/azure-ad-data-residency.md

@@ -8,13 +8,13 @@ ms.service: active-directory
 ms.workload: identity
 ms.subservice: fundamentals
 ms.topic: conceptual
-ms.date: 11/23/2022
+ms.date: 12/5/2022
 ms.author: jricketts
 ms.reviewer: jricketts
 ms.custom: "it-pro"
 ms.collection:
 ---
-# Azure Active Directory and data residency
+# Azure Active Directory and data residency 
 
 Azure AD is an Identity as a Service (IDaaS) solution that stores and manages identity and access data in the cloud. You can use the data to enable and manage access to cloud services, achieve mobility scenarios, and secure your organization. An instance of the Azure AD service, called a [tenant](/azure/active-directory/develop/developer-glossary#tenant), is an isolated set of directory object data that the customer provisions and owns. 
 
@@ -34,15 +34,15 @@ Currently Azure AD has the following regions:
 * [United States government](https://azure.microsoft.com/global-infrastructure/government/)
 * Worldwide
 
-Azure AD handles directory data based on usability, performance, residency and/or other requirements based on region. The term residency indicates Microsoft provides assurance the data isn’t persisted outside the geographic region. 
+Azure AD handles directory data based on usability, performance, residency and/or other requirements based on geography. The term residency indicates Microsoft provides assurance the data isn’t persisted outside the geography. 
 
 Azure AD replicates each tenant through its scale unit, across data centers, based on the following criteria:
 
-* Directory data stored in data centers closest to the user-residency location, to reduce latency and provide fast user sign-in times
-* Directory data stored in geographically isolated data centers to assure availability during unforeseen geological events 
-* Compliance with data residency, or other requirements, for specific customers and countries or regions
+* Directory data stored in data centers closest to the tenant-residency location, to reduce latency and provide fast user sign-in times
+* Directory data stored in geographically isolated data centers to assure availability during unforeseen single-datacenter, catastrophic events 
+* Compliance with data residency, or other requirements, for specific customers and countries or geographies
 
-During tenant creation (for example, signing up for Office 365 or Azure, or creating more Azure AD instances through the Azure portal) you select a country or region as the primary location. Azure AD maps the selection to a logical region and a single scale unit in it. Tenant location can’t be changed after it’s set.
+During tenant creation (for example, signing up for Office 365 or Azure, or creating more Azure AD instances through the Azure portal) you select a country as the primary location. Azure AD maps the selection to a logical region and a single scale unit in it. Tenant location can’t be changed after it’s set.
 
 ## Azure AD cloud solution models