Merge pull request #1340 from aljicamsft/patch-1

Update correct data storage location in data-residency.md

Author: v-dirichards

docs/fundamentals/data-residency.md

@@ -95,7 +95,7 @@ Learn more: [Microsoft Entra product overview](https://www.microsoft.com/cloud-p
 |---|---|---|
 |Microsoft Entra authentication Service|This service is stateless. The data for authentication is in the Microsoft Entra Core Store. It has no directory data. Microsoft Entra authentication Service generates log data in Azure Storage, and in the datacenter where the service instance runs. When users attempt to authenticate using Microsoft Entra ID, they're routed to an instance in the geographically nearest datacenter that is part of its Microsoft Entra logical region. |In geo location|
 |Microsoft Entra identity and Access Management (IAM) Services|**User and management experiences**: The Microsoft Entra management experience is stateless and has no directory data. It generates log and usage data stored in Azure Tables storage. The user experience is like the Azure portal. <br>**Identity management business logic and reporting services**: These services have locally cached data storage for groups and users. The services generate log and usage data that goes to Azure Tables storage, Azure SQL, and in Microsoft Elastic Search reporting services. |In geo location|
-|Microsoft Entra multifactor authentication|For details about multifactor authentication-operations data storage and retention, see [Data residency and customer data for Microsoft Entra multifactor authentication](~/identity/authentication/concept-mfa-data-residency.md). Microsoft Entra multifactor authentication logs the User Principal Name (UPN), voice-call telephone numbers, and SMS challenges. For challenges to mobile app modes, the service logs the UPN and a unique device token. Datacenters in the North America region store Microsoft Entra multifactor authentication, and the logs it creates.|North America|
+|Microsoft Entra multifactor authentication|For details about multifactor authentication-operations data storage and retention, see [Data residency and customer data for Microsoft Entra multifactor authentication](~/identity/authentication/concept-mfa-data-residency.md). Microsoft Entra multifactor authentication logs the User Principal Name (UPN), voice-call telephone numbers, and SMS challenges. For challenges to mobile app modes, the service logs the UPN and a unique device token.|North America and/or in geo location|
 |Microsoft Entra Domain Services|See regions where Microsoft Entra Domain Services is published on [Products available by region](https://azure.microsoft.com/regions/services/). The service holds system metadata globally in Azure Tables, and it contains no personal data.|In geo location|
 |Microsoft Entra Connect Health|Microsoft Entra Connect Health generates alerts and reports in Azure Tables storage and blob storage.|In geo location|
 |Microsoft Entra dynamic membership groups, Microsoft Entra self-service group management|Azure Tables storage holds rule definitions for dynamic membership groups.|In geo location|