Merge pull request #4719 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-08 06:00 UTC

Author: learn-build-service-prod[bot]

articles/documentdb/how-to-assess-plan-migration-readiness.md

@@ -16,8 +16,6 @@ Carry out up-front planning tasks and make critical decisions before migrating y
 
 ## Prerequisites
 
-[!INCLUDE[Prerequisite - Existing cluster](includes/prerequisite-existing-cluster.md)]
-
 - An existing MongoDB installation.
 
 ## Assess the compatibility and readiness of your resources for migration

articles/postgresql/configure-maintain/extended-support.md

@@ -4,7 +4,7 @@ description: Describes the extended support offering for Postgres major versions
 author: andtapia
 ms.author: andreatapia
 ms.reviewer: maghan
-ms.date: 03/09/2026
+ms.date: 03/26/2026
 ms.service: azure-database-postgresql
 ms.subservice: configuration
 ms.topic: concept-article
@@ -67,12 +67,16 @@ A: Your server is automatically enrolled in Extended Support one month after the
 
 **Q: Can I continue using my PostgreSQL instance without Extended Support?**
 
-A: Yes, but after the grace period, you're automatically enrolled in paid Extended Support unless you upgrade to a supported version. During the grace period, you assume full operational risk, and Microsoft support can't guarantee issue resolution.
+A: No, extended support is not optional. After the grace period, you're automatically enrolled in paid Extended Support unless you upgrade to a supported version. 
 
 **Q: Will I be charged for Extended Support if my server is stopped, failed, or not running??**
 
 A: No. Extended support billing charges apply only to servers that are in a Succeeded (running) state. If a server is stopped, deleted, or in a failed provisioning state, extended support charges will not be applied for that period. Billing automatically resumes once the server returns to a succeeded state and continues running an end‑of‑life engine version under extended support.
 
+**Q: What happens if I’m ready to upgrade to a supported PostgreSQL version, but capacity constraints in my region prevent me from upgrading before Extended Support billing begins?**
+
+A: If regional capacity constraints prevent you from upgrading, your server will be temporarily excluded from Extended Support billing until capacity becomes available and an upgrade path is offered, ensuring you’re not charged for factors outside your control.
+
 **Q: Can my applications break during a major version upgrade?**
 
 A: PostgreSQL major version upgrades can introduce changes that might affect your application - such as deprecated configuration parameters, incompatible extensions, or SQL behavior differences. Validate upgrades in a nonproduction environment before applying them in production. For more details, review the key considerations and limitations in [Major Version Upgrades](./concepts-major-version-upgrade.md) docs.

articles/postgresql/connectivity/includes/pgbouncer-parameters-table.md

@@ -2,19 +2,19 @@
 author: varun-dhawan
 ms.author: varundhawan
 ms.reviewer: maghan
-ms.date: 04/01/2026
+ms.date: 04/06/2026
 ms.service: azure-database-postgresql
 ms.topic: include
 ms.custom: automatically generated
 ---
 | Parameter name | Description | Default |
 | --- | --- | --- |
-| `pgbouncer.default_pool_size` | Set this parameter value to the number of connections per user/database pair. | 50 |
-| `pgbouncer.ignore_startup_parameters` | Enter a comma-separated list of parameters that PgBouncer can ignore. For example, you can let PgBouncer ignore the `extra_float_digits` parameter. Some parameters are allowed; all others raise an error. This ability is needed to tolerate overenthusiastic Java Database Connectivity (JDBC) wanting to unconditionally set `extra_float_digits=2` in startup packets. Use this option if the library that you use reports errors such as `pq: unsupported startup parameter: extra_float_digits`. | |
-| `pgbouncer.max_client_conn` | Set this parameter value to the highest number of client connections to PgBouncer that you want to support. | 5000 |
-| `pgbouncer.max_prepared_statements` | When this is set to a non-zero value, PgBouncer tracks protocol-level named prepared statements related commands sent by the client in transaction and statement pooling mode. | 0 |
+| `pgbouncer.default_pool_size` | How many server connections to allow per user/database pair. | 50 |
+| `pgbouncer.ignore_startup_parameters` | Comma-separated list of parameters that PgBouncer can ignore because they are going to be handled by the admin. | |
+| `pgbouncer.max_client_conn` | Maximum number of client connections allowed. | 5000 |
+| `pgbouncer.max_prepared_statements` | When this is set to a non-zero value PgBouncer tracks protocol-level named prepared statements related commands sent by the client in transaction and statement pooling mode. | 0 |
 | `pgbouncer.min_pool_size` | Add more server connections to pool if below this number. | 0 |
-| `pgbouncer.pool_mode` | Set this parameter value to TRANSACTION for transaction pooling (which is the recommended setting for most workloads). | transaction |
-| `pgbouncer.query_wait_timeout` | Maximum time (in seconds) queries are allowed to spend waiting for execution. If the query isn't assigned to a server during that time, the client is disconnected. | 120 |
+| `pgbouncer.pool_mode` | Specifies when a server connection can be reused by other clients. | transaction |
+| `pgbouncer.query_wait_timeout` | Maximum time (in seconds) queries are allowed to spend waiting for execution. If the query is not assigned to a server during that time, the client is disconnected. | 120 |
 | `pgbouncer.server_idle_timeout` | If a server connection has been idle more than this many seconds it will be dropped. If 0 then timeout is disabled. | 600 |
 | `pgbouncer.stats_users` | Comma-separated list of database users that are allowed to connect and run read-only queries on the pgBouncer console. | |

articles/postgresql/release-notes/release-notes.md

@@ -20,6 +20,7 @@ This article highlights the latest updates and enhancements for Azure Database f
 ## Release: April 2026
 - General availability
     - Support for latest [minor versions](../configure-maintain/concepts-supported-versions.md) 18.3, 17.9, 16.13, 15.17, and 14.22. <sup>$</sup>
+    - Support for [Premium SSD v2](../compute-storage/concepts-storage-premium-ssd-v2.md) now available in Azure portal for PostgreSQL
 
 ## Release: March 2026
 - General availability