Merge pull request #206295 from Rodrigossz/main

Bkp updates

Author: PRMerger16

articles/cosmos-db/analytical-store-introduction.md

@@ -407,15 +407,15 @@ Analytical store relies on Azure Storage and offers the following protection aga
 Although analytical store has built-in protection against physical failures, backup can be necessary for accidental deletes or updates in transactional store. In those cases, you can restore a container and use the restored container to backfill the data in the original container, or fully rebuild analytical store if necessary. 
 
 > [!NOTE]
-> Currently analytical store isn't backuped and can't be restored, and your backup policy can't be planned relying on that. 
+> Currently analytical store isn't backuped and can't be restored, and your backup policy can't be planned relying on that.
 
 Synapse Link, and analytical store by consequence, has different compatibility levels with Azure Cosmos DB backup modes:
 
-* Periodic backup mode is fully compatible with Synapse Link and these 2 features can be used in the same database account without any restriction. 
+* Periodic backup mode is fully compatible with Synapse Link and these 2 features can be used in the same database account.
 * Continuous backup mode isn't fully supported yet:
- * Currently continuous backup mode can't be used in database accounts with Synapse Link enabled.
- * Currently database accounts with continuous backup mode enabled can enable Synapse Link through a support case.
- * Currently new database accounts can be created with continous backup mode and Synapse Link enabled, using Azure CLI or PowerShell. Those two features must be turned on at the same time, in the exact same command that creates the database account.
+  * Database accounts with Synapse Link enabled currently can't use continuous backup mode. 
+  * Database accounts with continuous backup mode enabled can enable Synapse Link through a support case. This capability is in preview now.
+  * Database accounts that have neither continuous backup nor Synapse Link enabled can use these two features together through a support case. This capability is in preview now.
 
 ### Backup Polices
 

articles/cosmos-db/continuous-backup-restore-introduction.md

@@ -132,9 +132,7 @@ Currently the point in time restore functionality has the following limitations:
 
 * Multi-regions write accounts aren't supported.
 
-* Azure Synapse Link and periodic backup mode can coexist in the same database account. However, analytical store data isn't included in backups and restores. When Azure Synapse Link is enabled, Azure Cosmos DB will continue to automatically take backups of your data in the transactional store at a scheduled backup interval.
-
-* Azure Synapse Link and continuous backup mode can't coexist in the same database account. Currently database accounts with Azure Synapse Link enabled can't use continuous backup mode and vice-versa.
+* Currently Synapse Link isn't fully compatible with continuous backup mode. Click [here](analytical-store-introduction.md#backup) for more information.
 
 * The restored account is created in the same region where your source account exists. You can't restore an account into a region where the source account didn't exist.
 

articles/cosmos-db/synapse-link.md

@@ -116,13 +116,9 @@ Synapse Link isn't recommended if you're looking for traditional data warehouse
 
 * Enabling Synapse Link on existing Cosmos DB containers is only supported for SQL API accounts. Synapse Link can be enabled on new containers for both SQL API and MongoDB API accounts.
 
-*  Backup and restore:
-   *  You can recreate your analytical store data in some scenarios as below. In this mode, your transactional store data will be automatically backed up.  If `transactional TTL` is equal or greater than your `analytical TTL` on your container, you can fully recreate your analytical store data by enabling analytical store on the restored container:
-         - Azure Synapse Link can be enabled on accounts configured with periodic backups. 
-         - If continuous backup (point-in-time restore) is enabled on your account, you can now restore your analytical data. To enable Synapse Link for such accounts, please reach out to [email protected]. This is applicable only for SQL API. 
-   *  Restoring analytical data is not supported in following scenarios, for SQL API and API for Mongo DB:
-         - If you already enabled Synapse Link on your database account, you cannot enable point-in-time restore on such accounts.
-         - If `analytical TTL` is greater than `transactional TTL`, data that only exists in analytical store cannot be restored. You can continue to access full data from analytical store in the parent region.
+* Although analytical store data is not backed up, and therefore cannot be restored, you can rebuild your analytical store by reenabling Synapse Link in the restored container. Click [here](analytical-store-introduction.md#backup) for more information.
+
+* Currently Synapse Link isn't fully compatible with continuous backup mode. Click [here](analytical-store-introduction.md#backup) for more information.
 
 * Granular Role-based Access (RBAC)s isn't supported when querying from Synapse. Users that have access to your Synapse workspace and have access to the Cosmos DB account can access all containers within that account. We currently don't support more granular access to the containers.