Skip to content

Commit e9031a4

Browse files
authored
Update synapse-link.md
1 parent cc3ff6a commit e9031a4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cosmos-db/synapse-link.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ Azure Synapse Link isn't recommended if you're looking for traditional data ware
114114

115115
* Although analytical store data isn't backed up, and therefore can't be restored, you can rebuild your analytical store by reenabling Azure Synapse Link in the restored container. Check the [analytical store documentation](analytical-store-introduction.md) for more information.
116116

117-
* The capability to turn on Synapse Link in database accounts with continuous backup enabled is available now. But the opposite situation, to turn on continuous backup in Synapse Link enabled database accounts, is still not supported yet.
117+
* The capability to use Synapse Link and continuous backup in the same database account is available now. It's possible to turn on Synapse Link for accounts using continuous backup, and vice-versa. But currently database accounts that had Synapse Link disabled on containers level can't migrate to continuous backup.
118118

119119
* Granular role-based access control isn't supported when querying from Synapse. Users that have access to your Synapse workspace and have access to the Azure Cosmos DB account can access all containers within that account. We currently don't support more granular access to the containers.
120120

0 commit comments

Comments
 (0)