Merge pull request #233716 from reemas-new/patch-5

Update considerations-for-deployment.md

Author: prmerger-automator[bot]

articles/public-multi-access-edge-compute-mec/considerations-for-deployment.md

@@ -83,10 +83,13 @@ A trade-off exists between availability and latency. Although failing over the a
 
 Architect your edge applications by utilizing the Azure Region for the  components that are less latency sensitive, need to be persistent or need to be shared between public MEC sites. This will allow for the applications to be more resilient and cost effective. The public MEC can host the latency sensitive components.
 
+## Data residency
+> [!IMPORTANT]
+Azure public MEC doesn't store or process customer data outside the region you deploy the service instance in.
 
 ## Next steps
 
 To deploy a virtual machine in Azure public MEC using an Azure Resource Manager (ARM) template, advance to the following article:
 
 > [!div class="nextstepaction"]
-> [Quickstart: Deploy a virtual machine in Azure public MEC using an ARM template](quickstart-create-vm-azure-resource-manager-template.md)
+> [Quickstart: Deploy a virtual machine in Azure public MEC using an ARM template](quickstart-create-vm-azure-resource-manager-template.md)