Skip to content

Commit f467592

Browse files
Merge pull request #253091 from akashraokm/main
Customer Manage Keys GA changes
2 parents d15f677 + 02e8fad commit f467592

File tree

3 files changed

+7
-4
lines changed

3 files changed

+7
-4
lines changed

articles/cosmos-db/postgresql/concepts-customer-managed-keys.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.subservice: postgresql
88
ms.topic: conceptual
99
ms.date: 04/06/2023
1010
---
11-
# Data Encryption with Customer Managed Keys Preview
11+
# Data Encryption with Customer Managed Keys
1212

1313
[!INCLUDE [PostgreSQL](../includes/appliesto-postgresql.md)]
1414

articles/cosmos-db/postgresql/how-to-customer-managed-keys.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.subservice: postgresql
88
ms.topic: how-to
99
ms.date: 05/16/2023
1010
---
11-
# Enable data encryption with customer-managed keys (preview) in Azure Cosmos DB for PostgreSQL
11+
# Enable data encryption with customer-managed keys in Azure Cosmos DB for PostgreSQL
1212

1313
[!INCLUDE [PostgreSQL](../includes/appliesto-postgresql.md)]
1414

@@ -116,7 +116,7 @@ Make sure <b>Vault access policy</b> is selected under Permission model and then
116116

117117
1. Select the Key created in the previous step, and then select Review+create.
118118

119-
1. Verify that CMK is encryption is enabled by Navigating to the Data Encryption(preview) blade of the Cosmos DB for PostgreSQL cluster in the Azure portal.
119+
1. Verify that CMK is encryption is enabled by Navigating to the Data Encryption blade of the Cosmos DB for PostgreSQL cluster in the Azure portal.
120120
![Screenshot of data encryption tab.](media/how-to-customer-managed-keys/data-encryption-tab-note.png)
121121

122122
> [!NOTE]
@@ -257,7 +257,7 @@ Encryption configuration can be changed from service managed encryption to CMK e
257257
1. Navigate to the Data Encryption blade, and select Initiate restore operation. Alternatively, you can perform PITR by selecting the Restore option in the overview blade.
258258
[ ![Screenshot of PITR.](media/how-to-customer-managed-keys/point-in-time-restore.png)](media/how-to-customer-managed-keys/point-in-time-restore.png#lightbox)
259259

260-
1. You can change/configure the Data Encryption from the Encryption(preview) Tab.
260+
1. You can change/configure the Data Encryption from the Encryption Tab.
261261

262262
# [ARM Template](#tab/arm)
263263

articles/cosmos-db/postgresql/product-updates.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,9 @@ Updates that don’t directly affect the internals of a cluster are rolled out g
2323
Updates that change cluster internals, such as installing a [new minor PostgreSQL version](https://www.postgresql.org/developer/roadmap/), are delivered to existing clusters as part of the next [scheduled maintenance](concepts-maintenance.md) event. Such updates are available immediately to newly created clusters.
2424

2525
### September 2023
26+
27+
* General availability: Data Encryption at rest using [Customer Managed Keys](./concepts-customer-managed-keys.md) is now supported for all available regions.
28+
* See [this guide](./how-to-customer-managed-keys.md) for the steps to enable data encryption using customer managed keys.
2629
* Preview: Geo-redundant backup and restore
2730
* Learn more about [backup and restore Azure Cosmos DB for PostgreSQL](./concepts-backup.md)
2831
* Preview: [32 TiB storage per node for multi-node configurations](./resources-compute.md#multi-node-cluster) is now available in all supported regions.

0 commit comments

Comments
 (0)