Merge pull request #215567 from jjaygbay1/deprecate-public-internet-access

Delete enable public IP access

Author: Court72

.openpublishing.redirection.json

@@ -9568,6 +9568,11 @@
             "redirect_url": "/azure/azure-toolkit-for-intelliJ",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/azure-vmware/enable-public-internet-access.md",
+            "redirect_url": "/azure/azure-vmware/enable-public-ip-nsx-edge",
+            "redirect_document_id": false
+          },
         {
             "source_path_from_root": "/articles/azure-vmware/concepts-monitor-protection.md",
             "redirect_url": "/azure/azure-vmware/integrate-azure-native-services",
@@ -9625,7 +9630,7 @@
         },
         {
             "source_path_from_root": "/articles/azure-vmware/public-ip-usage.md",
-            "redirect_url": "/azure/azure-vmware/enable-public-internet-access",
+            "redirect_url": "/azure/azure-vmware/enable-public-ip-nsx-edge",
             "redirect_document_id": false
         },
         {

articles/azure-vmware/enable-public-internet-access.md

@@ -244,7 +244,7 @@ sections:
           > Any modification to that logical router or the NSX-T Data Center edge node VMs could affect connectivity to your private cloud.
 
       - question: Do I need to restrict access from the internet to VMs on logical networks in a private cloud?
-        answer: No. Network traffic inbound from the internet directly to private clouds isn't allowed by default.  However, you're able to expose Azure VMware Solution VMs to the internet through the [Public IP](./enable-public-internet-access.md) option in your Azure portal for your Azure VMware Solution private cloud.
+        answer: No. Network traffic inbound from the internet directly to private clouds isn't allowed by default.  However, you're able to expose Azure VMware Solution VMs to the internet through the [Public IP](./enable-public-ip-nsx-edge.md) option in your Azure portal for your Azure VMware Solution private cloud.
 
       - question: Do I need to restrict internet access from VMs on logical networks to the internet?
         answer: Yes. You'll need to use NSX-T Manager to create a firewall to restrict VM access to the internet.

articles/azure-vmware/faq.yml

@@ -16,7 +16,7 @@ When deploying a private cloud, private networks for management, provisioning, a
 
 [!INCLUDE [expressroute-global-reach](expressroute-global-reach.md)]
 
-Virtual machines deployed on the private cloud are accessible to the internet through the [Azure Virtual WAN public IP](../enable-public-internet-access.md) functionality. For new private clouds, internet access is disabled by default. 
+Virtual machines deployed on the private cloud are accessible to the internet through the [Azure Virtual WAN public IP](../enable-public-ip-nsx-edge.md) functionality. For new private clouds, internet access is disabled by default. 
 
 
 

articles/azure-vmware/includes/azure-vmware-solution-networking-description.md

@@ -304,7 +304,7 @@ To this point, you've migrated the workloads to the target environment. These ap
 
 - Published through the public IP feature in vWAN.
 
-Public IP is typically the destination NAT translated into the Azure firewall. With DNAT rules, firewall policy would translate the public IP address request to a private address (webserver) with a port. For more information, see [How to use the public IP functionality in Azure Virtual WAN](./enable-public-internet-access.md).
+Public IP is typically the destination NAT translated into the Azure firewall. With DNAT rules, firewall policy would translate the public IP address request to a private address (webserver) with a port. For more information, see [How to use the public IP functionality in Azure Virtual WAN](./enable-public-ip-nsx-edge.md).
 
 >[!NOTE]
 >SNAT is by default configured in Azure VMware Solution, so you must enable SNAT from Azure VMware Solution private cloud connectivity settings under the Manage tab.