Merge pull request #78584 from cherylmc/retire2

Retire2

Author: v-shils

.openpublishing.redirection.json

@@ -20,6 +20,26 @@
       "redirect_url": "https://docs.microsoft.com/previous-versions/azure/batch-ai/how-to-migrate",
       "redirect_document_id": true
     },
+    {
+      "source_path": "articles/best-practices-network-security.md",
+      "redirect_url": "https://docs.microsoft.com/azure/architecture/vdc/networking-virtual-datacenter",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/virtual-network/virtual-networks-dmz-nsg-asm.md",
+      "redirect_url": "https://docs.microsoft.com/azure/architecture/vdc/networking-virtual-datacenter",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/virtual-network/virtual-networks-dmz-nsg-fw-asm.md",
+      "redirect_url": "https://docs.microsoft.com/azure/architecture/vdc/networking-virtual-datacenter",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/virtual-network/virtual-networks-dmz-nsg-fw-udr-asm.md",
+      "redirect_url": "https://docs.microsoft.com/azure/architecture/vdc/networking-virtual-datacenter",
+      "redirect_document_id": true
+    },
     {
       "source_path": "articles/batch-ai/migrate-to-new-api.md",
       "redirect_url": "https://docs.microsoft.com/previous-versions/azure/batch-ai/how-to-migrate",

articles/app-service/overview-security.md

@@ -109,7 +109,6 @@ Alternatively, you can integrate your App Service app with [Azure Key Vault](/az
 
 Except for the **Isolated** pricing tier, all tiers run your apps on the shared network infrastructure in App Service. For example, the public IP addresses and front-end load balancers are shared with other tenants. The **Isolated** tier gives you complete network isolation by running your apps inside a dedicated [App Service environment](environment/intro.md). An App Service environment runs in your own instance of [Azure Virtual Network](/azure/virtual-network/). It lets you: 
 
-- Restrict network access with [network security groups](../virtual-network/virtual-networks-dmz-nsg.md). 
 - Serve your apps through a dedicated public endpoint, with dedicated front ends.
 - Serve internal application using an internal load balancer (ILB), which allows access only from inside your Azure Virtual Network. The ILB has an IP address from your private subnet, which provides total isolation of your apps from the internet.
 - [Use an ILB behind a web application firewall (WAF)](environment/integrate-with-application-gateway.md). The WAF offers enterprise-level protection to your public-facing applications, such as DDoS protection, URI filtering, and SQL injection prevention.

articles/best-practices-network-security.md

@@ -205,8 +205,6 @@
         href: virtual-network-scenario-udr-gw-nva.md
       - name: DMZ between Azure and the Internet
         href: ../guidance/guidance-iaas-ra-secure-vnet-dmz.md?toc=%2fazure%2fvirtual-network%2ftoc.json
-      - name: Create a DMZ with NSGs
-        href: virtual-networks-dmz-nsg.md
   - name: Configure
     items:
     - name: Name resolution for VMs and cloud services
@@ -331,14 +329,8 @@
         - name: Move VM to a different subnet
           href: virtual-networks-move-vm-role-to-subnet.md
     - name: Cloud service and network security
-      href: ../best-practices-network-security.md?toc=%2fazure%2fvirtual-network%2ftoc.json
+      href: https://docs.microsoft.com/azure/architecture/vdc/networking-virtual-datacenter
       items:
-      - name: Create a DMZ with NSGs
-        href: virtual-networks-dmz-nsg-asm.md
-      - name: Create a DMZ with firewall and NSGs
-        href: virtual-networks-dmz-nsg-fw-asm.md
-      - name: DMZ with firewall, UDR, and NSGs
-        href: virtual-networks-dmz-nsg-fw-udr-asm.md
       - name: Sample application
         href: virtual-networks-sample-app.md
 - name: Reference

articles/virtual-network/toc.yml

@@ -73,7 +73,7 @@ You can filter network traffic to and from resources in a virtual network using
 - If different VMs within a subnet need different security rules applied to them, you can associate the network interface in the VM to one or more application security groups. A security rule can specify an application security group in its source, destination, or both. That rule then only applies to the network interfaces that are members of the application security group. Learn more about [network security groups](security-overview.md) and [application security groups](security-overview.md#application-security-groups).
 - Azure creates several default security rules within each network security group. One default rule allows all traffic to flow between all resources in a virtual network. To override this behavior, use network security groups, custom routing to route traffic to an NVA, or both. It's recommended that you familiarize yourself with all of Azure's [default security rules](security-overview.md#default-security-rules) and understand how network security group rules are applied to a resource.
 
-You can view sample designs for implementing a perimeter network (also known as a DMZ) between Azure and the internet using an [NVA](/azure/architecture/reference-architectures/dmz/secure-vnet-dmz?toc=%2Fazure%2Fvirtual-network%2Ftoc.json) or [network security groups](virtual-networks-dmz-nsg.md).
+You can view sample designs for implementing a perimeter network (also known as a DMZ) between Azure and the internet using an [NVA](/azure/architecture/reference-architectures/dmz/secure-vnet-dmz?toc=%2Fazure%2Fvirtual-network%2Ftoc.json).
 
 ### Traffic routing