Skip to content

Commit e4bb3f4

Browse files
authored
Merge pull request #267660 from Lakshmisha-KS/lakshmisha-new-residency-update2
Update faq-energy-data-services.yml
2 parents 97e8111 + be7b415 commit e4bb3f4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/energy-data-services/faq-energy-data-services.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ sections:
2929
questions:
3030
- question: Where does Azure Data Manager for Energy store customer data?
3131
answer: >
32-
By default, Azure Data Manager for Energy replicates customer data to [Azure paired regions](/azure/reliability/cross-region-replication-azure#azure-paired-regions) for resiliency. The service doesn't replicate or move data outside the geography in which the customer created the instance. In regions that require data to remain within the sovereign geography (such as Brazil), the service always keeps customer data within the same region. For more information on the regions that support disaster recovery and cross-region data replication, see [Reliability in Azure Data Manager for Energy](reliability-energy-data-services.md).
32+
By default, Azure Data Manager for Energy replicates customer data to [Azure paired regions](/azure/reliability/cross-region-replication-azure#azure-paired-regions) for resiliency. The service doesn't replicate or move data outside the geography in which the customer created the instance. In some regions with requirements for data to remain within the single region, the service always keeps customer data within the same region. These regions are documented at [Data residency in Azure](https://azure.microsoft.com/explore/global-infrastructure/data-residency/). For more information on the regions that support disaster recovery and cross-region data replication, see [Reliability in Azure Data Manager for Energy](reliability-energy-data-services.md).
3333
3434
- name: Pricing and billing
3535
questions:

0 commit comments

Comments
 (0)