Merge pull request #214733 from rvandenbedem/patch-34

Updated index and TOC to match

Author: jborsecnik

articles/azure-vmware/configure-dhcp-azure-vmware-solution.md

@@ -4,7 +4,7 @@ description: Learn how to configure DHCP by using either NSX-T Manager to host a
 ms.topic: how-to
 ms.custom: contperf-fy21q2, contperf-fy22q1
 ms.service: azure-vmware
-ms.date: 10/04/2022
+ms.date: 10/17/2022
 
 # Customer intent: As an Azure service administrator, I want to configure DHCP by using either NSX-T Manager to host a DHCP server or use a third-party external DHCP server.
 
@@ -45,7 +45,7 @@ You can create a DHCP server or relay directly from Azure VMware Solution in the
 
    :::image type="content" source="media/networking/add-dhcp-server-relay.png" alt-text="Screenshot showing how to add a DHCP server or DHCP relay in Azure VMware Solutions.":::
 
-4. Complete the DHCP configuration by [providing DHCP ranges on the logical segments](tutorial-nsx-t-network-segment.md#use-azure-portal-to-add-an-nsx-t-data-center-segment) and then select **OK**.
+4. Complete the DHCP configuration by [providing DHCP ranges on the logical segments](tutorial-nsx-t-network-segment.md#use-azure-portal-to-add-an-nsx-t-data-center-network-segment) and then select **OK**.
 
 
 

articles/azure-vmware/configure-external-identity-source-nsx-t.md

@@ -1,14 +1,14 @@
 ---
-title: Configure external identity source for NSX-T
-description: Learn how to use the Azure VMware Solution to configure an external identity source for NSX-T.
+title: Configure external identity source for NSX-T Data Center
+description: Learn how to use the Azure VMware Solution to configure an external identity source for NSX-T Data Center.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 09/20/2022
+ms.date: 10/17/2022
 
 ---
-# Configure external identity source for NSX-T
+# Configure external identity source for NSX-T Data Center
 
-In this article, you'll learn how to configure an external identity source for NSX-T in an Azure VMware Solution. The NSX-T Data Center can be configured with external LDAP directory service to add remote directory users or groups. The users can be assigned an NSX-T Data Center Role-based access control (RBAC) role like you've on-premises. 
+In this article, you'll learn how to configure an external identity source for NSX-T Data Center in an Azure VMware Solution. The NSX-T Data Center can be configured with external LDAP directory service to add remote directory users or groups. The users can be assigned an NSX-T Data Center Role-based access control (RBAC) role like you've on-premises. 
 
 ## Prerequisites 
 
@@ -20,13 +20,13 @@ In this article, you'll learn how to configure an external identity source for N
     >[!Note] 
     > Self-sign certificates are not recommended for production environments.   
     
-- Ensure your Azure VMware Solution has DNS resolution configured to your on-premises AD. Enable DNS Forwarder from Azure portal. For more information, see [Configure NSX-T DNS for resolution to your Active Directory Domain and Configure DNS forwarder for Azure VMware Solution](configure-dns-azure-vmware-solution.md) .    
+- Ensure your Azure VMware Solution has DNS resolution configured to your on-premises AD. Enable DNS Forwarder from Azure portal. For more information, see [Configure NSX-T Data Center DNS for resolution to your Active Directory Domain and Configure DNS forwarder for Azure VMware Solution](configure-dns-azure-vmware-solution.md) .    
 >[!NOTE] 
 > For more information about LDAPS and certificate issuance, see with your security or identity management team.
 
 ## Add Active Directory as LDAPS identity source 
 
-1. Sign-in to NSX-T and Navigate to System > Users and Roles > LDAP. 
+1. Sign-in to NSX-T Manager and Navigate to System > Users and Roles > LDAP. 
 
 1. Select on the Add Identity Source. 
 
@@ -59,11 +59,11 @@ In this article, you'll learn how to configure an external identity source for N
 1. Select **Save** to complete the changes.
        :::image type="content" source="./media/nsxt/user-roles-ldap-server.png" alt-text="Screenshot showing user roles on an LDAP server." border="true" lightbox="./media/nsxt/user-roles-ldap-server.png":::
 
-## Assign other NSX-T roles to Active Directory identities 
+## Assign other NSX-T Data Center roles to Active Directory identities 
 
-After adding an external identity, you can assign NSX-T Roles to Active Directory security groups based on your organization's security controls. 
+After adding an external identity, you can assign NSX-T Data Center Roles to Active Directory security groups based on your organization's security controls. 
 
-1. Sign in to NSX-T and navigate to **System** > **Users and Roles**.
+1. Sign in to NSX-T Manager and navigate to **System** > **Users and Roles**.
 
 1. Select **Add** > **Role Assignment for LDAP**.  
 
@@ -76,7 +76,7 @@ After adding an external identity, you can assign NSX-T Roles to Active Director
 1. Verify the permission assignment is displayed under **Users and Roles**.
 :::image type="content" source="./media/nsxt/user-roles-ldap-verify.png" alt-text="Screenshot showing how to verify user roles on an LDAP server." border="true" lightbox="./media/nsxt/user-roles-ldap-verify.png":::
 
-1. Users should now be able to sign in to NSX-T using their Active Directory credentials. 
+1. Users should now be able to sign in to NSX-T Manager using their Active Directory credentials. 
 
 ## Next steps
 Now that you've configured the external source, you can also learn about:

articles/azure-vmware/configure-nsx-network-components-azure-portal.md

@@ -3,7 +3,7 @@ title: Configure NSX-T Data Center network components using Azure VMware Solutio
 description: Learn how to use the Azure VMware Solution to configure NSX-T Data Center network segments.
 ms.topic: reference
 ms.service: azure-vmware
-ms.date: 10/04/2022
+ms.date: 10/17/2022
 
 # Customer intent: As an Azure service administrator, I want to configure NSX-T Data Center network components using a simplified view of NSX-T Data Center operations a VMware administrator needs daily. The simplified view is targeted at users unfamiliar with NSX-T Manager.
 
@@ -17,7 +17,7 @@ After deploying Azure VMware Solution, you can configure the necessary NSX-T Dat
 
 You'll have four options to configure NSX-T Data Center components in the Azure VMware Solution console:
 
-- **Segments** - Create segments that display in NSX-T Manager and vCenter Server. For more information, see [Add an NSX-T Data Center segment using the Azure portal](tutorial-nsx-t-network-segment.md#use-azure-portal-to-add-an-nsx-t-data-center-segment).
+- **Segments** - Create segments that display in NSX-T Manager and vCenter Server. For more information, see [Add an NSX-T Data Center segment using the Azure portal](tutorial-nsx-t-network-segment.md#use-azure-portal-to-add-an-nsx-t-data-center-network-segment).
 
 - **DHCP** - Create a DHCP server or DHCP relay if you plan to use DHCP.  For more information, see [Use the Azure portal to create a DHCP server or relay](configure-dhcp-azure-vmware-solution.md#use-the-azure-portal-to-create-a-dhcp-server-or-relay).
 

articles/azure-vmware/enable-public-ip-nsx-edge.md

@@ -1,24 +1,24 @@
 ---
-title: Enable Public IP to the NSX Edge for Azure VMware Solution
+title: Enable Public IP to the NSX-T Data Center Edge for Azure VMware Solution
 description: This article shows how to enable internet access for your Azure VMware Solution.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 07/21/2022
+ms.date: 10/17/2022
 ---
 
-# Enable Public IP to the NSX Edge for Azure VMware Solution
+# Enable Public IP to the NSX-T Data Center Edge for Azure VMware Solution
 
-In this article, you'll learn how to enable Public IP to the NSX Edge for your Azure VMware Solution. 
+In this article, you'll learn how to enable Public IP to the NSX-T Data Center Edge for your Azure VMware Solution. 
 
 >[!TIP]
 >Before you enable Internet access to your Azure VMware Solution, review the [Internet connectivity design considerations](concepts-design-public-internet-access.md).
 
-Public IP to the NSX Edge is a feature in Azure VMware Solution that enables inbound and outbound internet access for your Azure VMware Solution environment. 
+Public IP to the NSX-T Data Center Edge is a feature in Azure VMware Solution that enables inbound and outbound internet access for your Azure VMware Solution environment. 
 
 >[!IMPORTANT]
 >The use of Public IPv4 addresses can be consumed directly in Azure VMware Solution and charged based on the Public IPv4 prefix shown on [Pricing - Virtual Machine IP Address Options.](https://azure.microsoft.com/pricing/details/ip-addresses/).
 
-The Public IP is configured in Azure VMware Solution through the Azure portal and the NSX-T Data center interface within your Azure VMware Solution private cloud.
+The Public IP is configured in Azure VMware Solution through the Azure portal and the NSX-T Data Center interface within your Azure VMware Solution private cloud.
 
 With this capability, you have the following features:
 - A cohesive and simplified experience for reserving and using a Public IP down to the NSX Edge.
@@ -32,14 +32,14 @@ With this capability, you have the following features:
 
 ## Prerequisites
 - Azure VMware Solution private cloud
-- DNS Server configured on the NSX-T Datacenter
+- DNS Server configured on the NSX-T Data Center
 
 ## Reference architecture    
-The architecture shows Internet access to and from your Azure VMware Solution private cloud using a Public IP directly to the NSX Edge.
+The architecture shows Internet access to and from your Azure VMware Solution private cloud using a Public IP directly to the NSX-T Data Center Edge.
 :::image type="content" source="media/public-ip-nsx-edge/architecture-internet-access-avs-public-ip.png" alt-text="Diagram that shows architecture of Internet access to and from your Azure VMware Solution Private Cloud using a Public IP directly to the NSX Edge." border="false" lightbox="media/public-ip-nsx-edge/architecture-internet-access-avs-public-ip-expanded.png":::
 
 >[!IMPORTANT]
->The use of Public IP down to the NSX Edge is not compatible with reverse DNS Lookup. 
+>The use of Public IP down to the NSX-T Data Center Edge is not compatible with reverse DNS Lookup. 
 
 ## Configure a Public IP in the Azure portal
 1. Log on to the Azure portal.
@@ -48,8 +48,8 @@ The architecture shows Internet access to and from your Azure VMware Solution pr
 1. In the left navigation, under **Workload Networking**, select **Internet connectivity**.   
 4.	Select the **Connect using Public IP down to the NSX-T Edge** button. 
 
->[!TIP]
->Before selecting a Public IP, ensure you understand the implications to your existing environment. For more information, see [Internet connectivity design considerations](concepts-design-public-internet-access.md).
+>[!IMPORTANT]
+>Before selecting a Public IP, ensure you understand the implications to your existing environment. For more information, see [Internet connectivity design considerations](concepts-design-public-internet-access.md). This should include a risk mitigation review with your relevant networking and security governance and compliance teams.
     
 5.	Select **Public IP**.
     :::image type="content" source="media/public-ip-nsx-edge/public-ip-internet-connectivity.png" alt-text="Diagram that shows how to select public IP to the NSX Edge":::
@@ -61,21 +61,21 @@ The architecture shows Internet access to and from your Azure VMware Solution pr
 9.	After configuring the Public IP, select the **Connect using the Public IP down to the NSX-T Edge** checkbox to disable all other Internet options. 
 10.	Select **Save**. 
 
-You have successfully enabled Internet connectivity for your Azure VMware Solution private cloud and reserved a Microsoft allocated Public IP. You can now configure this Public IP down to the NSX Edge for your workloads. The NSX-T Datacenter is used for all VM communication. There are several options for configuring your reserved Public IP down to the NSX Edge. 
+You have successfully enabled Internet connectivity for your Azure VMware Solution private cloud and reserved a Microsoft allocated Public IP. You can now configure this Public IP down to the NSX-T Data Center Edge for your workloads. The NSX-T Data Center is used for all VM communication. There are several options for configuring your reserved Public IP down to the NSX-T Data Center Edge. 
 
-There are three options for configuring your reserved Public IP down to the NSX Edge: Outbound Internet Access for VMs, Inbound Internet Access for VMs, and Gateway Firewall used to Filter Traffic to VMs at T1 Gateways.
+There are three options for configuring your reserved Public IP down to the NSX-T Data Center Edge: Outbound Internet Access for VMs, Inbound Internet Access for VMs, and Gateway Firewall used to Filter Traffic to VMs at T1 Gateways.
 
 ### Outbound Internet access for VMs
 
 A Sourced Network Translation Service (SNAT) with Port Address Translation (PAT) is used to allow many VMs to one SNAT service. This connection means you can provide Internet connectivity for many VMs.
 
 >[!IMPORTANT]
-> To enable SNAT for your specified address ranges, you must [configure a gateway firewall rule](#gateway-firewall-used-to-filter-traffic-to-vms-at-t1-gateways) and SNAT for the specific address ranges you desire. If you don't want SNAT enabled for specific address ranges, you must create a [No-NAT rule](#no-network-address-tranlation-rule-for-specific-address-ranges) for the address ranges to exclude. For your SNAT service to work as expected, the No-NAT rule should be a lower priority than the SNAT rule.
+> To enable SNAT for your specified address ranges, you must [configure a gateway firewall rule](#gateway-firewall-used-to-filter-traffic-to-vms-at-t1-gateways) and SNAT for the specific address ranges you desire. If you don't want SNAT enabled for specific address ranges, you must create a [No-NAT rule](#no-network-address-translation-rule-for-specific-address-ranges) for the address ranges to exclude. For your SNAT service to work as expected, the No-NAT rule should be a lower priority than the SNAT rule.
 
 **Add rule**
-1.	From your Azure VMware Solution private cloud, select **vCenter Credentials**
-2.	Locate your NSX-T URL and credentials.
-3.	Log in to **VMWare NSX-T**.   
+1.	From your Azure VMware Solution private cloud, select **vCenter Server Credentials**
+2.	Locate your NSX-T Manager URL and credentials.
+3.	Log in to **VMware NSX-T Manager**.   
 4.	Navigate to **NAT Rules**.
 5.	Select the T1 Router.
 1.  Select **ADD NAT RULE**.
@@ -89,15 +89,15 @@ A Sourced Network Translation Service (SNAT) with Port Address Translation (PAT)
 1. Optionally, give the rule a higher priority number. This prioritization will move the rule further down the rule list to ensure more specific rules are matched first.
 1. Click **SAVE**.
 
-Logging can be enabled by way of the logging slider. For more information on NSX-T NAT configuration and options, see the 
-[NSX-T NAT Administration Guide](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-7AD2C384-4303-4D6C-A44A-DEF45AA18A92.html)
+Logging can be enabled by way of the logging slider. For more information on NSX-T Data Center NAT configuration and options, see the 
+[NSX-T Data Center NAT Administration Guide](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-7AD2C384-4303-4D6C-A44A-DEF45AA18A92.html)
 
-### No Network Address Tranlation rule for specific address ranges
+### No Network Address Translation rule for specific address ranges
 
-A No SNAT rule in NSX manager can be used to exclude certain matches from performing Network Address Translation. This policy can be used to allow private IP traffic to bypass existing network translation rules.
-1. From your Azure VMware Solution private cloud, select **vCenter Credentials**.
-1. Locate your NSX-T URL and credentials.
-1. Log in to **VMWare NSX-T** and then select **NAT Rules**. 
+A No SNAT rule in NSX-T Manager can be used to exclude certain matches from performing Network Address Translation. This policy can be used to allow private IP traffic to bypass existing network translation rules.
+1. From your Azure VMware Solution private cloud, select **vCenter Server Credentials**.
+1. Locate your NSX-T Manager URL and credentials.
+1. Log in to **VMware NSX-T Manager** and then select **NAT Rules**. 
 1. Select the T1 Router and then select **ADD NAT RULE**.
 1. Select **NO SNAT** rule as the type of NAT rule.
 1. Select the **Source IP** as the range of addresses you do not want to be translated. The **Destination IP** should be any internal addresses you are reaching from the range of Source IP ranges.
@@ -106,10 +106,10 @@ A No SNAT rule in NSX manager can be used to exclude certain matches from perfor
 ### Inbound Internet Access for VMs
 A Destination Network Translation Service (DNAT) is used to expose a VM on a specific Public IP address and/or a specific port. This service provides inbound internet access to your workload VMs.
 
-**Log in to VMware NSX-T**
+**Log in to VMware NSX-T Manager**
 1.	From your Azure VMware Solution private cloud, select **VMware credentials**.
-2.	Locate your NSX-T URL and credentials.
-3.	Log in to **VMware NSX-T**.
+2.	Locate your NSX-T Manager URL and credentials.
+3.	Log in to **VMware NSX-T Manager**.
 
 **Configure the DNAT rule**
 1. Name the rule.
@@ -125,8 +125,8 @@ The VM is now exposed to the internet on the specific Public IP and/or specific
 
 You can provide security protection for your network traffic in and out of the public internet through your Gateway Firewall. 
 1.	From your Azure VMware Solution Private Cloud, select **VMware credentials**.
-2.	Locate your NSX-T URL and credentials.
-3.	Log in to **VMware NSX-T**.   
+2.	Locate your NSX-T Manager URL and credentials.
+3.	Log in to **VMware NSX-T Manager**.   
 4.	From the NSX-T home screen, select **Gateway Policies**.     
 5.	Select **Gateway Specific Rules**, choose the T1 Gateway and select **ADD POLICY**. 
 6.	Select **New Policy** and enter a policy name. 
@@ -143,8 +143,8 @@ For example, the following rule is set to Match External Address, and this setti
     :::image type="content" source="media/public-ip-nsx-edge/gateway-specific-rules-match-external-connectivity.png" alt-text="Screenshot Internet connectivity inbound Public IP." lightbox="media/public-ip-nsx-edge/gateway-specific-rules-match-external-connectivity-expanded.png":::
 
 If **Match Internal Address** was specified, the destination would be the internal or private IP address of the VM. 
-For more information on the NSX-T Gateway Firewall see the [NSX-T Gateway Firewall Administration Guide]( https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-A52E1A6F-F27D-41D9-9493-E3A75EC35481.html)
-The Distributed Firewall could be used to filter traffic to VMs. This feature is outside the scope of this document. For more information, see [NSX-T Distributed Firewall Administration Guide]( https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-6AB240DB-949C-4E95-A9A7-4AC6EF5E3036.html).
+For more information on the NSX-T Data Center Gateway Firewall see the [NSX-T Data Center Gateway Firewall Administration Guide]( https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-A52E1A6F-F27D-41D9-9493-E3A75EC35481.html)
+The Distributed Firewall could be used to filter traffic to VMs. This feature is outside the scope of this document. For more information, see [NSX-T Data Center Distributed Firewall Administration Guide]( https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-6AB240DB-949C-4E95-A9A7-4AC6EF5E3036.html).
 
 ## Next steps 
 [Internet connectivity design considerations (Preview)](concepts-design-public-internet-access.md)