From 9c38a8029b2b4feea841f63a9d147443d77c7487 Mon Sep 17 00:00:00 2001
From: Christian12cc <100135606+Christian12cc@users.noreply.github.com>
Date: Thu, 11 Jun 2026 10:11:29 +0200
Subject: [PATCH] Correct public_network_access_enabled setting in migration
 guide

Updated the documentation to reflect that 'public_network_access_enabled' should be set to false after migration.
validated after a test
---
 .../how-to-migrate-vnet-private-endpoint-capable-server.md      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/postgresql/network/how-to-migrate-vnet-private-endpoint-capable-server.md b/articles/postgresql/network/how-to-migrate-vnet-private-endpoint-capable-server.md
index 040631b139..a247425e65 100644
--- a/articles/postgresql/network/how-to-migrate-vnet-private-endpoint-capable-server.md
+++ b/articles/postgresql/network/how-to-migrate-vnet-private-endpoint-capable-server.md
@@ -87,7 +87,7 @@ For more information, see [Add private endpoint connections to Azure Database fo
 After the VNet to PE-capable network migration, the server is no longer VNet-integrated. If you have Terraform configurations, update them accordingly:
 
 - Remove `delegated_subnet_id` from the PostgreSQL server resource.
-- Ensure `public_network_access_enabled` remains `true` (this value is the post-migration default).
+- Ensure `public_network_access_enabled` remains `false` (this value is the post-migration default).
 
 ## Related content