Merge pull request #286657 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/load-balancer/ipv6-add-to-existing-vnet-cli.md

@@ -1,7 +1,7 @@
 ---
 title: Add IPv6 to an IPv4 application in Azure virtual network - Azure CLI
 titlesuffix: Azure Load Balancer
-description: This article shows how to deploy IPv6 addresses to an existing application in Azure virtual network using Azure CLI.
+description: This article shows how to deploy IPv6 addresses to an existing application in an Azure virtual network for a Standard Load Balancer using Azure CLI.
 author: mbender-ms
 ms.service: azure-load-balancer
 ms.topic: how-to

articles/virtual-network/ip-services/ipv6-overview.md

@@ -109,6 +109,8 @@ The current IPv6 for Azure Virtual Network release has the following limitations
 
 - Azure Firewall doesn't currently support IPv6. It can operate in a dual stack virtual network using only IPv4, but the firewall subnet must be IPv4-only.
 
+- Azure Database for PostgreSQL - Flexible Server doesn't currently support IPv6. Even if the subnet for the Postgres Flexible Server doesn't have any IPv6 addresses assigned, it cannot be deployed if there are IPv6 addresses in the VNet.
+
 ## Pricing
 
 There's no charge to use Public IPv6 Addresses or Public IPv6 Prefixes. Associated resources and bandwidth are charged at the same rates as IPv4. You can find details about pricing for [public IP addresses](https://azure.microsoft.com/pricing/details/ip-addresses/), [network bandwidth](https://azure.microsoft.com/pricing/details/bandwidth/), or [Load Balancer](https://azure.microsoft.com/pricing/details/load-balancer/).