Merge pull request #207029 from Rodrigossz/main

Update analytical-store-introduction.md

Author: PRMerger13

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

@@ -467,6 +467,8 @@ Analytical store partitioning is completely independent of partitioning in
 
 * **Network isolation using private endpoints** - You can control network access to the data in the transactional and analytical stores independently. Network isolation is done using separate managed private endpoints for each store, within managed virtual networks in Azure Synapse workspaces. To learn more, see how to [Configure private endpoints for analytical store](analytical-store-private-endpoints.md) article.
 
+* **Data encryption at rest** - Your analytical store encryption is enabled by default.
+
 * **Data encryption with customer-managed keys** - You can seamlessly encrypt the data across transactional and analytical stores using the same customer-managed keys in an automatic and transparent manner. Azure Synapse Link only supports configuring customer-managed keys using your Azure Cosmos DB account's managed identity. You must configure your account's managed identity in your Azure Key Vault access policy before [enabling Azure Synapse Link](configure-synapse-link.md#enable-synapse-link) on your account. To learn more, see how to [Configure customer-managed keys using Azure Cosmos DB accounts' managed identities](how-to-setup-cmk.md#using-managed-identity) article.
 
 ## Support for multiple Azure Synapse Analytics runtimes