Finalizing the changes for publishing

Author: niklarin

articles/cosmos-db/postgresql/concepts-row-level-security.md

@@ -6,7 +6,7 @@ author: jonels-msft
 ms.service: cosmos-db
 ms.subservice: postgresql
 ms.topic: conceptual
-ms.date: 01/30/2023
+ms.date: 10/02/2023
 ---
 
 # Row-level security in Azure Cosmos DB for PostgreSQL
@@ -30,7 +30,7 @@ security policies can compare the role name to values in the `tenant_id`
 distribution column to decide whether to allow access.
 
 Here's how to apply the approach on a simplified events table distributed by
-`tenant_id`. First [create the roles](howto-create-users.md) `tenant1` and
+`tenant_id`. First [create the roles](./how-to-configure-authentication.md#configure-native-postgresql-authentication) `tenant1` and
 `tenant2`. Then run the following SQL commands as the `citus` administrator
 user:
 
@@ -113,5 +113,5 @@ ERROR:  new row violates row-level security policy for table "events_102055"
 
 ## Next steps
 
-Learn how to [create roles](howto-create-users.md) in a
-cluster.
+- Learn how to [create roles](./how-to-configure-authentication.md#configure-native-postgresql-authentication) in a cluster.
+- Check out [security concepts in Azure Cosmos DB for PostgreSQL](./concepts-security-overview.md)

articles/cosmos-db/postgresql/how-to-connect-with-managed-identity.md

@@ -1,13 +1,13 @@
 ---
 title: Restore - Azure Cosmos DB for PostgreSQL - Azure portal
 description: See how to perform restore operations in Azure Cosmos DB for PostgreSQL through the Azure portal.
-ms.author: jonels
-author: jonels-msft
+ms.author: nlarin
+author: niklarin
 ms.service: cosmos-db
 ms.subservice: postgresql
 ms.custom: ignite-2022
 ms.topic: how-to
-ms.date: 06/12/2023
+ms.date: 10/02/2023
 ---
 
 # Point-in-time restore of a cluster in Azure Cosmos DB for PostgreSQL
@@ -58,7 +58,7 @@ back up and running:
   and client applications to the new server
 * Ensure appropriate [networking settings for private or public access](./concepts-security-overview.md#network-security) are in place for
   users to connect. These settings aren't copied from the original cluster.
-* Ensure appropriate [logins](./howto-create-users.md) and database level permissions are in place.
+* Ensure appropriate [logins](./how-to-configure-authentication.md#configure-native-postgresql-authentication) and database level permissions are in place.
 * Configure [alerts](./howto-alert-on-metric.md#suggested-alerts), as appropriate.
 
 ## Next steps

articles/cosmos-db/postgresql/howto-restore-portal.md

@@ -8,7 +8,7 @@ ms.service: cosmos-db
 ms.subservice: postgresql
 ms.custom: mvc, mode-ui, ignite-2022
 ms.topic: quickstart
-ms.date: 06/07/2023
+ms.date: 10/02/2023
 ---
 
 # Connect to a cluster with psql - Azure Cosmos DB for PostgreSQL
@@ -30,7 +30,7 @@ Your cluster has a default database named `citus`. To connect to the database, y
 
    :::image type="content" source="media/quickstart-connect-psql/get-connection-string.png" alt-text="Screenshot that shows copying the psql connection string.":::
 
-   The **psql** string is of the form `psql "host=c-<cluster>.<uniqueID>.postgres.cosmos.azure.com port=5432 dbname=citus user=citus password={your_password} sslmode=require"`. Notice that the host name starts with a `c.`, for example `c-mycluster.12345678901234.postgres.cosmos.azure.com`. This prefix indicates the coordinator node of the cluster. The default `dbname` is `citus` and can be changed only at cluster provisioning time. The `user` can be any valid [Postgres role](./howto-create-users.md) on your cluster.
+   The **psql** string is of the form `psql "host=c-<cluster>.<uniqueID>.postgres.cosmos.azure.com port=5432 dbname=citus user=citus password={your_password} sslmode=require"`. Notice that the host name starts with a `c.`, for example `c-mycluster.12345678901234.postgres.cosmos.azure.com`. This prefix indicates the coordinator node of the cluster. The default `dbname` is `citus` and can be changed only at cluster provisioning time. The `user` can be any valid [Postgres role](./how-to-configure-authentication.md#configure-native-postgresql-authentication) on your cluster.
 
 1. Open Azure Cloud Shell by selecting the **Cloud Shell** icon on the top menu bar.