From 68c7c3c5116cb5ccb852687be4dae510d6005f21 Mon Sep 17 00:00:00 2001
From: Ljakka <133011158+Ljakka@users.noreply.github.com>
Date: Tue, 23 Sep 2025 22:08:14 +0530
Subject: [PATCH] Update simplified-node-communication-pool-no-public-ip.md

Updated outbound internet access retirement date from September 30 , 2025 to March 31, 2026
---
 .../batch/simplified-node-communication-pool-no-public-ip.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/batch/simplified-node-communication-pool-no-public-ip.md b/articles/batch/simplified-node-communication-pool-no-public-ip.md
index 6f07f54501f80..2a275871f380c 100644
--- a/articles/batch/simplified-node-communication-pool-no-public-ip.md
+++ b/articles/batch/simplified-node-communication-pool-no-public-ip.md
@@ -144,7 +144,7 @@ In a pool without public IP addresses, your virtual machines won't be able to ac
 Another way to provide outbound connectivity is to use a user-defined route (UDR). This method lets you route traffic to a proxy machine that has public internet access, for example [Azure Firewall](../firewall/overview.md).
 
 > [!IMPORTANT]
-> There is no extra network resource (load balancer, network security group) created for simplified node communication pools without public IP addresses. Since the compute nodes in the pool are not bound to any load balancer, Azure may provide [Default Outbound Access](../virtual-network/ip-services/default-outbound-access.md). However, Default Outbound Access is not suitable for production workloads, and will be retired on September 30, 2025 (see the [official announcement](https://azure.microsoft.com/updates/default-outbound-access-for-vms-in-azure-will-be-retired-transition-to-a-new-method-of-internet-access/)). So if your workloads do require internet outbound access, or your pool doesn't use private endpoint to access Batch node management endpoint, you must provide your own solution to enable internet outbound access.
+> There is no extra network resource (load balancer, network security group) created for simplified node communication pools without public IP addresses. Since the compute nodes in the pool are not bound to any load balancer, Azure may provide [Default Outbound Access](../virtual-network/ip-services/default-outbound-access.md). However, Default Outbound Access is not suitable for production workloads, and will be retired on March 31, 2026 (see the [official announcement](https://azure.microsoft.com/updates/default-outbound-access-for-vms-in-azure-will-be-retired-transition-to-a-new-method-of-internet-access/)). So if your workloads do require internet outbound access, or your pool doesn't use private endpoint to access Batch node management endpoint, you must provide your own solution to enable internet outbound access.
 
 ## Troubleshooting