Merge pull request #200254 from rvandenbedem/patch-11

Stacyrch140 · web-flow · commit 59569d7e8694 · 2022-08-19T13:07:38.000-04:00
Update faq.yml
diff --git a/articles/azure-vmware/faq.yml b/articles/azure-vmware/faq.yml
@@ -100,20 +100,20 @@ sections:
 
 
 
-  - name: VMware software
+  - name: VMware solution software
     questions:
 
       - question: Can Azure VMware Solution VMs be managed by VMRC?
-        answer: Yes. Provided the system it's installed on can access the private cloud vCenter and is using public DNS to resolve ESXi hostnames.
+        answer: Yes. Provided the system it's installed on can access the private cloud vCenter Server and is using public DNS to resolve ESXi hostnames.
 
       - question: Are there special instructions for installing and using VMRC with Azure VMware Solution VMs?
         answer: No. To meet the VM prerequisites, follow the [instructions provided by VMware](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-89E7E8F0-DB2B-437F-8F70-BA34C505053F.html). 
 
       - question: Can I use vRealize Suite running on-premises? 
-        answer: vRealize Automation, vRealize Operations Manager, and vRealize Network Insight are certified for use with Azure VMware Solution when those products are installed in an on-premises datacenter. The cloud-based versions of these products--vRealize Automation Cloud, vRealize Operations Cloud, and vRealize Network Insight Cloud--are also certified for use. Installing these products within an Azure VMware Solution private cloud is not supported.
+        answer: vRealize Automation, vRealize Operations Manager, and vRealize Network Insight are certified for use with Azure VMware Solution when those products are installed in an on-premises data center. The cloud-based versions of these products--vRealize Automation Cloud, vRealize Operations Cloud, and vRealize Network Insight Cloud--are also certified for use. Installing these products within an Azure VMware Solution private cloud is not supported.
 
       - question: Can I migrate vSphere VMs from on-premises environments to Azure VMware Solution private clouds?
-        answer: Yes. VM migration and vMotion can be used to move VMs to a private cloud if standard cross vCenter [vMotion requirements](https://kb.vmware.com/s/article/2106952?lang=en_US&queryTerm=2106952) are met.
+        answer: Yes. VM migration and vMotion can be used to move VMs to a private cloud if standard cross vCenter Server [vMotion requirements](https://kb.vmware.com/s/article/2106952?lang=en_US&queryTerm=2106952) are met.
           
       - question: Is a specific version of vSphere required in on-premises environments?
         answer: The on-premises environment must be running vSphere 6.0 or later if VMware HCX will be used to migrate VMs.
@@ -125,27 +125,27 @@ sections:
         answer: |
           [!INCLUDE [vmware-software-versions](includes/vmware-software-versions.md)]
           
-      - question: How often is the VMware software (ESXi, vCenter, PSC, and NXS) patched, updated, or upgraded in the Azure VMware Solution private cloud?
+      - question: How often is the VMware solution software (ESXi, vCenter Server, NSX-T Data Center) patched, updated, or upgraded in the Azure VMware Solution private cloud?
         answer: |
           [!INCLUDE [vmware-software-update-frequency](includes/vmware-software-update-frequency.md)]
 
-      - question: Do private clouds use VMware NSX? If so, which version is supported?
+      - question: Do private clouds use VMware NSX Data Center? If so, which version is supported?
         answer: |
-          Yes, NSX-T is the only supported version of NSX.   
+          Yes, NSX-T Data Center is the only supported version of NSX Data Center.   
           
           NSX-T [!INCLUDE [nsxt-version](includes/nsxt-version.md)] is used for the software-defined networking in Azure VMware Solution private clouds.
 
-      - question: Is NSX required in on-premises environments or networks that connect to a private cloud?
-        answer: No, you aren't required to use NSX on-premises.
+      - question: Is NSX-T Data Center required in on-premises environments or networks that connect to a private cloud?
+        answer: No, you aren't required to use NSX-T Data Center on-premises. VMware HCX provides the necessary connectivity between on-premises vSphere and Azure VMware Solution.
 
-      - question: Is NSX-T Identity Firewall supported with Azure VMware Solution?
-        answer: Yes, NSX-T Identity Firewall is supported with Azure VMware Solution.
+      - question: Is NSX-T Data Center Identity Firewall supported with Azure VMware Solution?
+        answer: Yes, NSX-T Data Center Identity Firewall is supported with Azure VMware Solution.
         
       - question: Is VMware Horizon 8 2012 compatible with Azure VMware Solution?
         answer: Yes.
 
-      - question: Can I change the default vSphere Web Client timeout value?
-        answer: Yes. For information on changing the timeout value, see [Configure the vSphere Web Client Timeout Value](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-975412DE-CDCB-49A1-8E2A-0965325D33A5.html).
+      - question: Can I change the default vSphere Client timeout value?
+        answer: Yes. For information on changing the timeout value, see [Configure the vSphere Client Timeout Value](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-975412DE-CDCB-49A1-8E2A-0965325D33A5.html).
 
 
 
@@ -170,7 +170,7 @@ sections:
       - question: How much memory is in each host?
         answer: The servers have 576 GB of RAM.
 
-      - question: Does Azure VMware Solution support running ESXi/ESX as a nested virtualization solution?
+      - question: Does Azure VMware Solution support running ESXi as a nested virtualization solution?
         answer: No. VMware does not officially support nested virtualization. 
 
 
@@ -237,17 +237,17 @@ sections:
 
       - question: How do I connect a workload VM to the internet or an Azure service endpoint?
         answer: |
-          In the Azure portal, enable internet connectivity for a private cloud. With NSX-T manager, create an NSX-T T1 router and a logical switch. You then use vCenter to deploy a VM on the network segment defined by the logical switch. That VM has network access to the internet and Azure services.
+          In the Azure portal, enable internet connectivity for a private cloud. With NSX-T Manager, create an NSX-T Data Center T1 gateway and a logical switch. You then use vCenter Server to deploy a VM on the network segment defined by the logical switch. That VM has network access to the internet and Azure services.
           
           > [!NOTE]
-          > A T0 router is created and configured as part of a private cloud deployment.
-          > Any modification to that logical router or the NSX-T edge node VMs could affect connectivity to your private cloud.
+          > A T0 gateway is created and configured as part of a private cloud deployment.
+          > 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.
           
       - 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.
+        answer: Yes. You'll need to use NSX-T Manager to create a firewall to restrict VM access to the internet.
 
       - question: Which IP range can be used for DNS service IP and DHCP server IP?
         answer: The IP address range shouldn't overlap with the IP range used in other virtual networks in your subscription and on-premises networks.
@@ -258,12 +258,12 @@ sections:
       - question: Can transit connectivity be established between on-premises and Azure VMware Solution through Azure Virtual WAN over ExpressRoute Global Reach?
         answer: Azure Virtual WAN doesn't provide transitive routing between two connected ExpressRoute circuits and non-virtual WAN ExpressRoute Gateway. ExpressRoute Global Reach allows connectivity between on-premises and Azure VMware Solution but goes through Microsoft's global network instead of the Virtual WAN Hub.
 
-      - question: Is Windows 2008 supported as an Active Directory (AD) server or Remote Desktop Session Host (RDSH) OS in NSX-T?
+      - question: Is Windows 2008 supported as an Active Directory (AD) server or Remote Desktop Session Host (RDSH) OS in NSX-T Data Center?
         answer: No.
 
       - question: Why can't I reach the Azure VMware Solution vCenter Server Appliance and NSX-T Manager from on-premises or Azure Virtual Network?
         answer: |
-          By design, you won't be able to reach NSX-T Manager and vCenter Server Appliance (VCSA) from on-premises when only 0.0.0.0/0 (default route) is being advertised over ExpressRoute Global Reach between Azure VMware Solution and your on-premises ExpressRoute or through Azure Virtual Network to Azure VMware Solution. You'll need to advertise specific networking routes/subnets to access NSX-T Manager and VCSA. 
+          By design, you won't be able to reach NSX-T Manager and vCenter Server Appliance (vCSA) from on-premises when only 0.0.0.0/0 (default route) is being advertised over ExpressRoute Global Reach between Azure VMware Solution and your on-premises ExpressRoute or through Azure Virtual Network to Azure VMware Solution. You'll need to advertise specific networking routes/subnets to access NSX-T Manager and vCSA. 
 
 
 
@@ -273,27 +273,26 @@ sections:
   - name: Storage
     questions:
 
-      - question: What is the correct storage policy for the dedup setup?
+      - question: What is the correct storage policy for the deduplication setup?
         answer: Use the *thin_provision* storage policy for your VM template.
 
       - question: What is the storage capacity of each host?
         answer: Each ESXi host has two vSAN disk groups with a capacity tier of 15.2TB and a 3.2-TB NVMe cache tier (1.6 TB in each disk group).      
 
       - question: Is data stored on the vSAN datastores encrypted at rest?
-        answer: Yes, vSAN datastores use data-at-rest encryption by default using keys stored in Azure Key Vault. The encryption solution is KMS-based and supports vCenter operations for key management.  When a host is removed from a cluster, data on SSDs is invalidated immediately.
+        answer: Yes, vSAN datastores use data-at-rest encryption by default using keys stored in Azure Key Vault. The encryption solution is KMS-based and supports vCenter Server operations for key management.  When a host is removed from a vSphere cluster, data on SSDs is invalidated immediately.
 
       - question: Can I rename a datastore or cluster during creation?
         answer: No, you can't change the name of datastores or clusters. The cluster name is configurable through non-portal deployment mechanisms for non-primary clusters.
 
       - question: What is the Fault tolerance of hardware failure on the vSAN?
-        answer: |
-          RAID-1, FTT-1, with Object Space reservation set to Thin Provisioning is the Default Storage policy for the software-defined datacenters (SDDCs).
+        answer: RAID-1, FTT-1, with Object Space reservation set to Thin Provisioning is the Default Storage policy for the software-defined datacenters (SDDCs).
           
       - question: What is the difference between thick provisioning and thin provisioning? 
         answer: Thick provisioning is reserved or pre-allocated storage space.  Thick provisioning protects systems by allowing them to function even if the vSAN datastore is full because the space is already reserved. For example, suppose you create a 10GB virtual disk with thick provisioning. In that case, the full amount of virtual disk storage capacity is pre-allocated on the physical storage where the virtual disk is created and consumes all the space allocated to it in the datastore.  It won't allow other VMs to share the space from the datastore. A thin-provisioned virtual disk consumes the space that it needs initially and grows to the data space demand used in the datastore.
 
       - question: How many disks can fail on the vSAN before data loss occurs? 
-        answer: It depends on how you plan your application workloads to run inside the SDDC (private cloud). Microsoft governs these failures regularly and replaces the hardware when such events are detected from an infrastructure perspective. As a default, a setting of FFT-1 is used, which accommodates a single host's failure.
+        answer: It depends on how you plan your application workloads to run inside the SDDC (private cloud). Microsoft governs these failures regularly and replaces the hardware when such events are detected from an infrastructure perspective. As a default, a setting of FTT-1 is used, which accommodates a single host's failure.
 
       - question: What kind of alerts can I expect to see for vSAN? 
         answer: Microsoft provides alerts when capacity consumption exceeds 75%. Alternatively, you can also monitor capacity consumption metrics that are integrated into Azure Monitor.
@@ -316,10 +315,10 @@ sections:
         answer: No. There's only one type available.
 
       - question: Do I use the same tools that I use now to manage private cloud resources?
-        answer: Yes. The Azure portal is used for deployment and several management operations. vCenter and NSX Manager are used to manage vSphere and NSX-T resources.
+        answer: Yes. The Azure portal is used for deployment and several management operations. vCenter Server and NSX-T Manager are used to manage vSphere and NSX-T Data Center resources.
 
-      - question: Can I manage a private cloud with my on-premises vCenter?
-        answer: At launch, Azure VMware Solution won't support a single management experience across on-premises and private cloud environments. You manage private cloud clusters with vCenter and NSX Manager local to a private cloud.
+      - question: Can I manage a private cloud with my on-premises vCenter Server?
+        answer: At launch, Azure VMware Solution won't support a single management experience across on-premises and private cloud environments. You manage private cloud clusters with vCenter Server and NSX-T Manager local to a private cloud.
 
       - question: If a cluster is scaled up, and then workload demand falls, can it be scaled back down? 
         answer: Yes, as long as you have the quota allocated against your private cloud, you can scale out your clusters. When workload demand falls, you can delete hosts from the cluster to scale it down. You can do this through the Azure VMware Solution portal.
@@ -335,20 +334,20 @@ sections:
   - name: Identity management
     questions:
       - question: What accounts and privileges will I get with my new Azure VMware Solution private cloud?
-        answer: You're provided credentials for a cloudadmin user in vCenter and admin access on NSX-T Manager. You can also use a CloudAdmin group to incorporate Azure Active Directory. For more information, see [Access and identity Concepts](concepts-identity.md).
+        answer: You're provided credentials for a cloudadmin user in vCenter Server and admin access on NSX-T Manager. You can also use a CloudAdmin group to incorporate Azure Active Directory. For more information, see [Access and identity Concepts](concepts-identity.md).
           
       - question: Can have administrator access to ESXi hosts?
         answer: No, administrator access to ESXi is restricted to meet the security requirements of the solution.
 
-      - question: What privileges and permissions will I have in vCenter?
+      - question: What privileges and permissions will I have in vCenter Server?
         answer: You'll have CloudAdmin role privileges. For more information, see [Access and identity Concepts](concepts-identity.md).
           
-      - question: What privileges and permissions will I have on the NSX-T manager?
+      - question: What privileges and permissions will I have on the NSX-T Manager?
         answer: |
-          You'll have full administrator privileges on NSX-T and can manage vSphere role-based access control as you would with NSX-T Data Center on-premises. For more information, see [Access and Identity Concepts](concepts-identity.md).
+          You'll have full administrator privileges on NSX-T Data Center and can manage vSphere role-based access control as you would with NSX-T Data Center on-premises. For more information, see [Access and Identity Concepts](concepts-identity.md).
           
           > [!NOTE]
-          > A T0 router is created and configured as part of a private cloud deployment. Any modification to that logical router or the NSX-T edge node VMs could affect connectivity to your private cloud.
+          > A T0 gateway is created and configured as part of a private cloud deployment. Any modification to that logical router or the NSX-T Data Center edge node VMs could affect connectivity to your private cloud.
 
       - question: How can I change my credentials?
         answer: For information on resetting your credentials, see [Rotate the cloudadmin credentials for Azure VMware Solution](rotate-cloudadmin-credentials.md).
@@ -374,11 +373,11 @@ sections:
       - question: I use Azure VMware Solution to create end-user applications or workloads accessed on multiple VMs through public IP. Can I sell this solution to multiple tenants?
         answer: Customers can create multi-tenant environments in their Azure VMware Solution private cloud and sell to customers provided the product is not a standard VM and have added substantial intellectual property embedded in the VM as an application.
 
-      - question: As a hoster or customer, can I use my existing VMware Cloud Director (VCD) or new VCXD deployment in Azure VMware Solution?
+      - question: As a service provider or customer, can I use my existing VMware Cloud Director (VCD) or new VCD deployment in Azure VMware Solution?
         answer: VMware does not allow VCD in the cloud or from on-premises to be licensed with any Hyperscaler, including Microsoft.
 
       - question: Can I connect VMware Cloud Director Service (CDS) to my Azure VMware Solution instance in Azure?
-        answer: Although technically possible, Microsoft does not allow Azure VMware Solution to be used through the new CDS service from VMware running on VMC.
+        answer: Although technically possible, Microsoft does not allow Azure VMware Solution to be used through the new CDS service from VMware running on VMware Cloud.
 
       - question: Can Azure VMware Solution be purchased through a Microsoft CSP?
         answer: Yes, customers can deploy Azure VMware Solution within an Azure subscription managed by a CSP.
