changes

Author: GennadNY

articles/postgresql/flexible-server/concepts-data-encryption.md

@@ -158,7 +158,7 @@ Some of the reasons why server state can become *Inaccessible* are:
 
 
 > [!NOTE]  
-> CLI examples below are based on 2.43.0 version of Azure Database for PostgreSQL - Flexible Server CLI libraries, which are in preview and may be subject to changes.  
+> CLI examples below are based on 2.45.0 version of Azure Database for PostgreSQL - Flexible Server CLI libraries
 
 ## Setup Customer Managed Key during Server Creation
 
@@ -259,8 +259,6 @@ The following are current limitations for configuring the customer-managed key i
 
 - Once enabled, CMK encryption can't be removed. If customer desires to remove this feature, it can only be done via restore of the server to non-CMK server.
 
-- No support for Geo backup enabled servers
-
 - No support for Azure HSM Key Vault 
 
 ## Next steps

articles/postgresql/flexible-server/how-to-create-server-customer-managed-key-cli.md

@@ -13,7 +13,7 @@ ms.date: 12/10/2022
 [!INCLUDE [applies-to-postgresql-flexible-server](../includes/applies-to-postgresql-flexible-server.md)]
 
 > [!NOTE]  
-> CLI examples below are based on 2.43.0 version of Azure Database for PostgreSQL - Flexible Server CLI libraries, which are in preview and may be subject to changes.  
+> CLI examples below are based on 2.45.0 version of Azure Database for PostgreSQL - Flexible Server CLI libraries
 
 In this article, you learn how to create and manage Azure Database for PostgreSQL - Flexible Server with data  encrypted by Customer Managed Keys using the Azure CLI. To learn more about Customer Managed Keys (CMK) feature with Azure Database for PostgreSQL - Flexible Server, see the [overview](concepts-data-encryption.md).