Merge pull request #269976 from rvandenbedem/patch-2

ToC structure change

Author: American-Dipper

.openpublishing.redirection.azure-vmware.json

@@ -179,6 +179,66 @@
             "source_path_from_root": "/articles/azure-vmware/vrealize-operations-for-avs.md",
             "redirect_url": "/azure/azure-vmware/vrealize-operations-for-azure-vmware-solution",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-vmware/concepts-api-management.md",
+            "redirect_url": "/azure/azure-vmware/architecture-api-management",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-vmware/concepts-design-public-internet-access.md",
+            "redirect_url": "/azure/azure-vmware/architecture-design-public-internet-access",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-vmware/concepts-hub-and-spoke.md",
+            "redirect_url": "/azure/azure-vmware/architecture-hub-and-spoke",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-vmware/concepts-identity.md",
+            "redirect_url": "/azure/azure-vmware/architecture-identity",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-vmware/concepts-migrate.md",
+            "redirect_url": "/azure/azure-vmware/architecture-migrate",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-vmware/concepts-network-design-considerations.md",
+            "redirect_url": "/azure/azure-vmware/architecture-network-design-considerations",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-vmware/concepts-networking.md",
+            "redirect_url": "/azure/azure-vmware/architecture-networking",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-vmware/concepts-private-clouds-clusters.md",
+            "redirect_url": "/azure/azure-vmware/architecture-private-clouds",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-vmware/concepts-run-command.md",
+            "redirect_url": "/azure/azure-vmware/using-run-command",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-vmware/concepts-security-recommendations.md",
+            "redirect_url": "/azure/azure-vmware/security-recommendations",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-vmware/concepts-storage.md",
+            "redirect_url": "/azure/azure-vmware/architecture-storage",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-vmware/concepts-vulnerability-management.md",
+            "redirect_url": "/azure/azure-vmware/vulnerability-management",
+            "redirect_document_id": false
         }
     ]
 }

articles/advisor/advisor-reference-performance-recommendations.md

@@ -4,7 +4,7 @@ description: Full list of available performance recommendations in Advisor.
 ms.topic: article
 author: mabrahms
 ms.author: v-mabrahms
-ms.date: 10/15/2023
+ms.date: 3/22/2024
 ---
 
 # Performance recommendations
@@ -167,9 +167,9 @@ Learn more about [Synapse workspace - UpgradeSynapseManagementClientSDK (Update
 
 ### vSAN capacity utilization has crossed critical threshold
 
-Your vSAN capacity utilization has reached 75%. The cluster utilization is required to remain below the 75% critical threshold for SLA compliance. Add new nodes to VSphere cluster to increase capacity or delete VMs to reduce consumption or adjust VM workloads
+Your vSAN capacity utilization has reached 75%. The cluster utilization is required to remain below the 75% critical threshold for SLA compliance. Add new nodes to the vSphere cluster to increase capacity or delete VMs to reduce consumption or adjust VM workloads
 
-Learn more about [AVS Private cloud - vSANCapacity (vSAN capacity utilization has crossed critical threshold)](../azure-vmware/concepts-private-clouds-clusters.md).
+Learn more about [Azure VMware Solution private cloud - vSANCapacity (vSAN capacity utilization has crossed critical threshold)](../azure-vmware/architecture-private-clouds.md).
 
 ### Update Automanage to the latest API Version
 

articles/azure-netapp-files/performance-azure-vmware-solution-datastore.md

@@ -1,9 +1,9 @@
 ---
-title: Concepts - API Management 
+title: Architecture - API Management 
 description: Learn how API Management protects APIs running on Azure VMware Solution virtual machines (VMs)
 ms.topic: conceptual
 ms.service: azure-vmware
-ms.date: 2/26/2024
+ms.date: 3/22/2024
 ms.custom: engagement-fy23
 ---
 

articles/azure-vmware/concepts-api-management.md renamed to articles/azure-vmware/architecture-api-management.md

@@ -1,9 +1,9 @@
 ---
-title: Concept - Internet connectivity design considerations
+title: Architecture - Internet connectivity design considerations
 description: Options for Azure VMware Solution Internet Connectivity. 
 ms.topic: conceptual
 ms.service: azure-vmware
-ms.date: 11/28/2023
+ms.date: 3/22/2024
 ms.custom: engagement-fy23
 ---
 
@@ -13,7 +13,7 @@ There are three primary patterns to create outbound access to the Internet from
 
 - [Internet Service hosted in Azure](#internet-service-hosted-in-azure) 
 - [Azure VMware Solution Managed SNAT](#azure-vmware-solution-managed-snat) 
-- [Azure Public IPv4 address to NSX-T Data Center Edge](#azure-public-ipv4-address-to-nsx-t-data-center-edge) 
+- [Azure Public IPv4 address to NSX Data Center Edge](#azure-public-ipv4-address-to-nsx-edge) 
 
 Your requirements for security controls, visibility, capacity, and operations drive the selection of the appropriate method for delivery of Internet access to the Azure VMware Solution private cloud.  
 
@@ -42,9 +42,9 @@ A Managed SNAT service provides a simple method for outbound internet access fro
 - Two Public IPs are used and rotated to support up to 128k simultaneous outbound connections.
 - No inbound DNAT capability is available with the  Azure VMware Solution Managed SNAT. 
 
-## Azure Public IPv4 address to NSX-T Data Center Edge  
+## Azure Public IPv4 address to NSX Edge  
 
-This option brings an allocated Azure Public IPv4 address directly to the NSX-T Data Center Edge for consumption. It allows the Azure VMware Solution private cloud to directly consume and apply public network addresses in NSX-T Data Center as required. These addresses are used for the following types of connections:
+This option brings an allocated Azure Public IPv4 address directly to the NSX Edge for consumption. It allows the Azure VMware Solution private cloud to directly consume and apply public network addresses in NSX as required. These addresses are used for the following types of connections:
 - Outbound SNAT
 - Inbound DNAT
 - Load balancing using VMware NSX Advanced Load Balancer and other third-party Network Virtual Appliances
@@ -55,20 +55,20 @@ This option also lets you configure the public address on a third-party Network
 Features include: 
 
    - Scale – you can request to increase the soft limit of 64 Azure Public IPv4 addresses to 1,000 s of Azure Public IPs allocated if an application requires it.
-   - Flexibility – an Azure Public IPv4 address can be applied anywhere in the NSX-T Data Center ecosystem. It can be used to provide SNAT or DNAT, on load balancers like VMware’s NSX Advanced Load Balancer, or third-party Network Virtual Appliances. It can also be used on third-party Network Virtual Security Appliances on VMware segments or directly on VMs. 
-   - Regionality – the Azure Public IPv4 address to NSX-T Data Center Edge is unique to the local SDDC. For “multi private cloud in distributed regions,” with local exit to Internet intentions, it’s easier to direct traffic locally versus trying to control default route propagation for a security or SNAT service hosted in Azure. If you have two or more Azure VMware Solution private clouds connected with a Public IP configured, they can both have a local exit.  
+   - Flexibility – an Azure Public IPv4 address can be applied anywhere in the NSX ecosystem. It can be used to provide SNAT or DNAT, on load balancers like VMware’s NSX Advanced Load Balancer, or third-party Network Virtual Appliances. It can also be used on third-party Network Virtual Security Appliances on VMware segments or directly on VMs. 
+   - Regionality – the Azure Public IPv4 address to NSX Edge is unique to the local SDDC. For “multi private cloud in distributed regions,” with local exit to Internet intentions, it’s easier to direct traffic locally versus trying to control default route propagation for a security or SNAT service hosted in Azure. If you have two or more Azure VMware Solution private clouds connected with a Public IP configured, they can both have a local exit.  
 
 ## Considerations for selecting an option 
 
 The option that you select depends on the following factors: 
 
 - To add an Azure VMware private cloud to a security inspection point provisioned in Azure native that inspects all Internet traffic from Azure native endpoints, use an Azure native construct and leak a default route from Azure to your Azure VMware Solution private cloud.
-- If you need to run a third-party Network Virtual Appliance to conform to existing standards for security inspection or streamlined operating expenses, you have two options. You can run your Azure Public IPv4 address in Azure native with the default route method or run it in Azure VMware Solution using Azure Public IPv4 address to NSX-T Data Center Edge. 
-- There are scale limits on how many Azure Public IPv4 addresses can be allocated to a Network Virtual Appliance running in native Azure or provisioned on Azure Firewall.  The Azure Public IPv4 address to NSX-T Data Center Edge option allows for higher allocations (1,000 s versus 100 s).
-- Use an Azure Public IPv4 address to the NSX-T Data Center Edge for a localized exit to the internet from each private cloud in its local region. Using multiple Azure VMware Solution private clouds in several Azure regions that need to communicate with each other and the internet, it can be challenging to match an Azure VMware Solution private cloud with a security service in Azure. The difficulty is due to the way a default route from Azure works.
+- If you need to run a third-party Network Virtual Appliance to conform to existing standards for security inspection or streamlined operating expenses, you have two options. You can run your Azure Public IPv4 address in Azure native with the default route method or run it in Azure VMware Solution using Azure Public IPv4 address to NSX Edge. 
+- There are scale limits on how many Azure Public IPv4 addresses can be allocated to a Network Virtual Appliance running in native Azure or provisioned on Azure Firewall.  The Azure Public IPv4 address to NSX Edge option allows for higher allocations (1,000 s versus 100 s).
+- Use an Azure Public IPv4 address to the NSX Edge for a localized exit to the internet from each private cloud in its local region. Using multiple Azure VMware Solution private clouds in several Azure regions that need to communicate with each other and the internet, it can be challenging to match an Azure VMware Solution private cloud with a security service in Azure. The difficulty is due to the way a default route from Azure works.
 
 > [!IMPORTANT]
-> By design, Public IPv4 Address with NSX-T Data Center does not allow the exchange of Azure/Microsoft owned Public IP Addresses over ExpressRoute Private Peering connections. This means you cannot advertise the Public IPv4 addresses to your customer vNET or on-premises network via ExpressRoute.  All Public IPv4 Addresses with NSX-T Data Center traffic must take the internet path even if the Azure VMware Solution private cloud is connected via ExpressRoute. For more information, visit [ExpressRoute Circuit Peering](../expressroute/expressroute-circuit-peerings.md).
+> By design, Public IPv4 Address with NSX does not allow the exchange of Azure/Microsoft owned Public IP Addresses over ExpressRoute Private Peering connections. This means you cannot advertise the Public IPv4 addresses to your customer VNet or on-premises network via ExpressRoute.  All Public IPv4 Addresses with NSX traffic must take the internet path even if the Azure VMware Solution private cloud is connected via ExpressRoute. For more information, visit [ExpressRoute Circuit Peering](../expressroute/expressroute-circuit-peerings.md).
 
 ## Next Steps
 

articles/azure-vmware/concepts-design-public-internet-access.md renamed to articles/azure-vmware/architecture-design-public-internet-access.md

@@ -1,9 +1,9 @@
 ---
-title: Concept - Integrate an Azure VMware Solution deployment in a hub and spoke architecture
+title: Architecture - Integrate an Azure VMware Solution deployment in a hub and spoke architecture
 description: Learn about integrating an Azure VMware Solution deployment in a hub and spoke architecture on Azure.
 ms.topic: conceptual
 ms.service: azure-vmware
-ms.date: 12/21/2023
+ms.date: 3/22/2024
 ms.custom: engagement-fy23
 ---
 
@@ -68,7 +68,7 @@ Because an ExpressRoute gateway doesn't provide transitive routing between its c
 
   :::image type="content" source="./media/hub-spoke/azure-vmware-solution-hub-vnet-traffic-flow.png" alt-text="Diagram showing the Azure VMware Solution to Hub virtual network traffic flow." border="false" lightbox="./media/hub-spoke/azure-vmware-solution-hub-vnet-traffic-flow.png":::
 
-For more information on Azure VMware Solution networking and connectivity concepts, see the [Azure VMware Solution product documentation](./concepts-networking.md).
+For more information on Azure VMware Solution networking and connectivity concepts, see the [Azure VMware Solution product documentation](./architecture-networking.md).
 
 ### Traffic segmentation