Merge pull request #219949 from GennadNY/gennadyk897

changes

Author: prmerger-automator[bot]

articles/postgresql/flexible-server/concepts-pgbouncer.md

@@ -92,7 +92,7 @@ Utilizing an application side pool together with PgBouncer on the database serve
 * If you change the compute tier from General Purpose or Memory Optimized to Burstable tier, you will lose the PgBouncer capability.
 * Whenever the server is restarted during scale operations, HA failover, or a restart, the PgBouncer is also restarted along with the server virtual machine. Hence the existing connections have to be re-established.
 * Due to a known issue, the portal does not show all PgBouncer parameters. Once you enable PgBouncer and save the parameter, you have to exit Parameter screen (for example, click Overview) and then get back to Parameters page. 
-* [SCRAM authentication](how-to-connect-scram.md) is not supported with PgBouncer.
+
 
 ## Next steps
 

articles/postgresql/flexible-server/how-to-connect-scram.md

@@ -81,7 +81,7 @@ To access the PostgreSQL database server using SCRAM method of authentication, y
 8. You can then connect from the client that supports SCRAM authentication to your server.
 
 > [!Note] 
-> SCRAM authentication is not supported when connected to the built-in managed [PgBouncer](concepts-pgbouncer.md).
+> SCRAM authentication is also supported when connected to the built-in managed [PgBouncer](concepts-pgbouncer.md). Above tutorial is valid for setting up connectivity using SCRAM authentication via built-in PgBouncer feature. 
 
 ## Next steps
 - [Create and manage Azure Database for PostgreSQL - Flexible Server virtual network using Azure CLI](./how-to-manage-virtual-network-cli.md).

articles/postgresql/single-server/concepts-certificate-rotation.md

@@ -26,7 +26,7 @@ The new certificate is rolled out and in effect starting December, 2022 (12/2022
 
 ## What change will be performed starting December 2022 (12/2022)?
 
-Starting December 2022, the [BaltimoreCyberTrustRoot root certificate](https://www.digicert.com/CACerts/BaltimoreCyberTrustRoot.crt.pem) will be  replaced with a **compliant version** known as [DigiCertGlobalRootG2 root certificate ](https://www.digicert.com/CACerts/BaltimoreCyberTrustRoot.crt.pem). If your applications take advantage of **verify-ca** or **verify-full** as value of [**sslmode** parameter](https://www.postgresql.org/docs/current/libpq-ssl.html) in the database client connectivity will need to follow directions below to add new certificates to certificate store to maintain connectivity.
+Starting December 2022, the [BaltimoreCyberTrustRoot root certificate](https://www.digicert.com/CACerts/BaltimoreCyberTrustRoot.crt.pem) will be  replaced with a **compliant version** known as [DigiCertGlobalRootG2 root certificate ](https://cacerts.digicert.com/DigiCertGlobalRootG2.crt.pem). If your applications take advantage of **verify-ca** or **verify-full** as value of [**sslmode** parameter](https://www.postgresql.org/docs/current/libpq-ssl.html) in the database client connectivity will need to follow directions below to add new certificates to certificate store to maintain connectivity.
 
 ## Do I need to make any changes on my client to maintain connectivity?