Update 3-configure-public-ip-services.md

Author: staleycyn

learn-pr/wwl-azure/introduction-to-azure-virtual-networks/includes/3-configure-public-ip-services.md

@@ -1,7 +1,3 @@
-
-
-
-
 Public networks like the Internet communicate by using public IP addresses. Private networks like your Azure Virtual Network use private IP addresses, which aren't routable on public networks. To support a network that exists both in Azure and on-premises, you must configure IP addressing for both types of networks.
 
 Public IP addresses enable Internet resources to communicate with Azure resources and enable Azure resources to communicate outbound with Internet and public-facing Azure services. A public IP address in Azure is dedicated to a specific resource. A resource without a public IP assigned can communicate outbound through network address translation services, where Azure dynamically assigns an available IP address that isn't dedicated to the resource.
@@ -31,16 +27,16 @@ Public IP addresses are created with an IPv4 or IPv6 address, which can be eithe
 ## Choose the appropriate SKU for a public IP address
 
 > [!IMPORTANT]
->
-> On September 30, 2025, Basic SKU public IPs will be retired. If you are currently using Basic SKU public IPs, make sure to upgrade to Standard SKU public IPs prior to the retirement date. For guidance on upgrading, visit [Upgrading a basic public IP address to Standard SKU](/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance).
-
-| Public IP address | **Standard** | **Basic**|
-| --- | --- |--- |
-| Allocation method | Static |  For IPv4: Dynamic or Static; For IPv6: Dynamic. |
-| Idle time-out | Have an adjustable inbound originated flow idle time out of 4-30 minutes, with a default of 4 minutes, and fixed outbound originated flow idle time out of 4 minutes. |  Have an adjustable inbound originated flow idle time out of 4-30 minutes, with a default of 4 minutes, and fixed outbound originated flow idle time out of 4 minutes. |
-|Security | Secure by default model and be closed to inbound traffic when used as a frontend. Allow traffic with network security group (NSG) is required (for example, on the NIC of a virtual machine with a Standard SKU Public IP attached). |Open by default. Network security groups are recommended but optional for restricting inbound or outbound traffic|
-|Availability zones | Supported. Standard IPs can be nonzonal, zonal, or zone-redundant. Zone redundant IPs can only be created in regions where there are three availability zones.| Not supported.|
-|Routing preference | Supported to enable more granular control of how traffic is routed between Azure and the Internet.| Not supported.|
-|Global tier | Supported via cross-region load balancers.| Not supported.|
-
-Choose the best response for each question.
+> On September 30, 2025, Basic SKU public IPs were retired. If you're currently using Basic SKU public IPs, upgrade to Standard SKU public IPs as soon as possible. Basic IPs remain operational post-retirement but are unsupported and not covered by SLA guarantees. For guidance on upgrading, visit [Upgrading a basic public IP address to Standard SKU](/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance).
+
+
+| Public IP address | **Standard SKU** | 
+| --- | --- |
+| Allocation method | Static | 
+| Idle time-out | Have an adjustable inbound originated flow idle time out of 4-30 minutes, with a default of 4 minutes, and fixed outbound originated flow idle time out of 4 minutes. |  
+| Security | Secure by default model and be closed to inbound traffic when used as a frontend. Allow traffic with network security group (NSG) is required (for example, on the NIC of a virtual machine with a Standard SKU Public IP attached). 
+| Availability zones | Supported. Standard IPs can be nonzonal, zonal, or zone-redundant. Zone redundant IPs can only be created in regions where there are three availability zones.|
+| Routing preference | Supported to enable more granular control of how traffic is routed between Azure and the Internet.| 
+| Global tier | Supported via cross-region load balancers.| 
+
+Choose the best response for each question.