Merge pull request #279532 from varun-dhawan/varund-jul

[PostgreSQL]  updates PgBouncer limitation

Author: prmerger-automator[bot]

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

@@ -3,8 +3,7 @@ title: PgBouncer in Azure Database for PostgreSQL - Flexible Server
 description: This article provides an overview of the built-in PgBouncer feature.
 author: varun-dhawan
 ms.author: varundhawan
-ms.reviewer: maghan
-ms.date: 05/22/2024
+ms.date: 06/27/2024
 ms.service: postgresql
 ms.subservice: flexible-server
 ms.topic: conceptual
@@ -127,6 +126,8 @@ Using an application-side pool together with PgBouncer on the database server ca
 
 * If PgBouncer is deployed as a feature, it becomes a potential single point of failure. If the PgBouncer feature is down, it can disrupt the entire database connection pool and cause downtime for the application. To mitigate the single point of failure, you can set up multiple PgBouncer instances behind a load balancer for high availability on Azure VMs.
 
+* Token Size Restriction with AAD Authentication - Users with a large number of group memberships won’t be able to connect through PgBouncer due to a token size restriction. Applications, services, and users with a small number of groups work.
+
 * PgBouncer is a lightweight application that uses a single-threaded architecture. This design is great for most application workloads. But in applications that create a large number of short-lived connections, this design might affect pgBouncer performance and limit your ability to scale your application. You might need to try one of these approaches:
 
   * Distribute the connection load across multiple PgBouncer instances on Azure VMs.