Merge pull request #248384 from Rodrigossz/main

AS x data residency

Author: prmerger-automator[bot]

articles/cosmos-db/data-residency.md

@@ -25,6 +25,11 @@ In Azure Cosmos DB, you must explicitly configure the cross-region data replicat
 
 **Periodic mode Backups**: By default, periodic mode account backups will be stored in geo-redundant storage. For periodic backup modes, you can configure data redundancy at the account level. There are three redundancy options for the backup storage. They are local redundancy, zone redundancy, or geo redundancy. For more information, see [periodic backup/restore](periodic-backup-restore-introduction.md).
 
+## Residency requirements for analytical store
+
+Analytical store is resident by default as it is stored in either locally redundant or zone redundant storage. To learn more, see the [analytical store](analytical-store-introduction.md) article.
+
+
 ## Use Azure Policy to enforce the residency requirements
 
 If you have data residency requirements that require you to keep all your data in a single Azure region, you can enforce zone-redundant or locally redundant backups for your account by using an Azure Policy.  You can also enforce a policy that the Azure Cosmos DB accounts are not geo-replicated to other regions.

articles/cosmos-db/synapse-link-frequently-asked-questions.yml

@@ -26,14 +26,13 @@ sections:
       - question: |
           Is Azure Synapse Link supported for multi-region Azure Cosmos DB accounts?
         answer: |
-          Yes, for multi-region Azure Cosmos DB accounts, the data stored in the analytical store is also globally distributed. Regardless of single write region or multiple write regions, analytical queries performed from Azure Synapse Analytics can be served from the closest local region.
-          
-          When planning to configure a multi-region Azure Cosmos DB account with analytical store support, it's recommended to have all the necessary regions added at time of account creation.
-          
+          Yes, for multi-region Azure Cosmos DB accounts, the data stored in the analytical store is also globally distributed. Analytical store will exists in all regions where you also have transactional store. Regardless of single write region or multiple write regions, analytical queries performed from Azure Synapse Analytics can be served from the closest local region.
+      
+        
       - question: |
           Can I choose to enable Azure Synapse Link for only certain region and not all regions in a multi-region account set-up?
         answer: |
-          When Azure Synapse Link is enabled for a multi-region account, the analytical store is created in all regions. The underlying data is optimized for throughput and transactional consistency in the transactional store.
+          When Azure Synapse Link is enabled for a multi-region account, analytical store is created in all regions chosen by customers for transactional geo-replication. The underlying data is optimized for throughput and transactional consistency in the transactional store.
 
       - question: |
           Is analytical store supported in all Azure Cosmos DB regions?