Merge pull request #268481 from Farha-Bano/Doc_updates_Mar8

Doc updates

Author: PMEds28

articles/azure-arc/vmware-vsphere/enable-virtual-hardware.md

@@ -1,52 +1,105 @@
 ---
-title:  Enable virtual hardware and VM CRUD capabilities in a machine with Arc agent installed
-description: Enable virtual hardware and VM CRUD capabilities in a machine with Arc agent installed
+title:  Enable additional capabilities on Arc-enabled Server machines by linking to vCenter
+description: Enable additional capabilities on Arc-enabled Server machines by linking to vCenter.
 ms.topic: how-to 
-ms.date: 01/03/2024
+ms.date: 03/13/2024
 ms.service: azure-arc
 ms.subservice: azure-arc-vmware-vsphere
 author: Farha-Bano
 ms.author: v-farhabano
 manager: jsuri
 ---
 
-# Enable virtual hardware and VM CRUD capabilities in a machine with Arc agent installed
+# Enable additional capabilities on Arc-enabled Server machines by linking to vCenter
 
-In this article, you learn how to enable virtual hardware management and VM CRUD operational ability on a VMware VM that has Arc agents installed via the Arc-enabled Servers route.
+If you have VMware machines connected to Azure via Arc-enabled Servers route, you can seamlessly get additional capabilities by deploying resource bridge and connecting vCenter to Azure. The additional capabilities include the ability to perform virtual machine lifecycle operations, such as create, resize, and power cycle operations such as start, stop, and so on. You can get additional capabilities without any disruption, retaining the VM extensions configured on the Arc-enabled Server machines.   
+
+Follow these steps [here](./quick-start-connect-vcenter-to-arc-using-script.md) to deploy the Arc Resource Bridge and connect vCenter to Azure.
 
 >[!IMPORTANT]
-> This article is applicable only if you've installed Arc agents directly in VMware machines before onboarding to Azure Arc-enabled VMware vSphere by deploying Arc resource bridge. 
+> This article applies only if you've directly installed Arc agents on the VMware machines, and those machines are onboarded as *Microsoft.HybridCompute/machines* ARM resources before connecting vCenter to Azure by deploying Resource Bridge. 
 
 ## Prerequisites
 
 - An Azure subscription and resource group where you have *Azure Arc VMware Administrator role*. 
 - Your vCenter instance must be [onboarded](quick-start-connect-vcenter-to-arc-using-script.md) to Azure Arc.
+- Arc-enabled Servers machines and vCenter resource must be in the same Azure region.
 
-## Enable virtual hardware management and self-service access to vCenter VMs with Arc agent installed
+## Link Arc-enabled Servers machines to vCenter from Azure portal
 
-1. From your browser, go to [Azure portal](https://portal.azure.com/).
+1. Navigate to the Virtual machines inventory page of your vCenter in the Azure portal. 
 
-1. Navigate to the Virtual machines inventory page of your vCenter. The virtual machines that have Arc agent installed via the Arc-enabled Servers route will have **Link to vCenter** status under virtual hardware management.
+2. The Virtual machines that have Arc agent installed via Arc-enabled Servers route have **Link to vCenter** status under virtual hardware management.  
 
-1. Select **Link to vCenter** to view the pane with the list of all the machines under vCenter with Arc agent installed but not linked to the vCenter in Azure Arc.
+3. Select **Link to vCenter** to open a pane that lists all the machines under vCenter with Arc agent installed but not linked to vCenter in Azure Arc.  
 
-1. Choose all the machines that need to be enabled in Azure, and select **Link** to link the machines to vCenter.
+4. Choose all the machines and select the option to link machines to vCenter.
 
-1. After you link to vCenter, the virtual hardware status will reflect as **Enabled** for all the VMs, and you can perform [virtual hardware operations](perform-vm-ops-through-azure.md). 
+    :::image type="content" source="media/enable-virtual-hardware/link-machine-to-vcenter.png" alt-text="Screenshot that shows the Link to vCenter page." lightbox="media/enable-virtual-hardware/link-machine-to-vcenter.png":::
 
-### Known issue
- 
-During the first scan of the vCenter inventory after onboarding to Azure Arc-enabled VMware vSphere, Arc-enabled Servers machines will be discovered under vCenter inventory. If the Arc-enabled Server machines aren't discovered and you try to perform the **Enable in Azure** operation, you'll encounter the following error:<br>
+5.	After linking to vCenter, the virtual hardware status reflects as **Enabled** for all the VMs, and you can perform [virtual hardware operations](./perform-vm-ops-through-azure.md). 
 
-*A machine '/subscriptions/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXXX/resourceGroups/rg-contoso/providers/Microsoft.HybridCompute/machines/testVM1' already exists with the specified virtual machine MoRefId: 'vm-4441'. The existing machine resource can be extended with private cloud capabilities by creating the VirtualMachineInstance resource under it.*
+    :::image type="content" source="media/enable-virtual-hardware/perform-virtual-hardware-operations.png" alt-text="Screenshot that shows the page for performing virtual hardware operations." lightbox="media/enable-virtual-hardware/perform-virtual-hardware-operations.png":::
+
+    After linking to vCenter, virtual lifecycle operations and power cycle operations are enabled on the machines, and the kind property of Hybrid Compute Machine is updated as VMware.
 
-When you encounter this error message, try performing the **Link to vCenter** operation again after a few minutes (5-10 minutes). Alternatively, you can use the following Azure CLI command to link an existing Arc-enabled Server machine to vCenter:<br>
+## Link Arc-enabled Server machines to vCenter using Azure CLI
 
+Use the following az commands to link Arc-enabled Server machines to vCenter at scale.  
+
+**Create VMware resources from the specified Arc for Server machines in the vCenter** 
 
 ```azurecli-interactive
-az connectedvmware vm create --subscription <subscription-id> --location <Azure region of the machine> --resource-group <resource-group-name> --custom-location /providers/microsoft.extendedlocation/customlocations/<custom-location-name> --name <machine-name> --inventory-item /subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.ConnectedVMwarevSphere/VCenters/<vcenter-name>/InventoryItems/<machine-name>
+az connectedvmware vm create-from-machines --resource-group contoso-rg --name contoso-vm --vcenter-id /subscriptions/fedcba98-7654-3210-0123-456789abcdef/resourceGroups/contoso-rg-2/providers/Microsoft.HybridCompute/vcenters/contoso-vcenter
 ```
 
+**Create VMware resources from all Arc for Server machines in the specified resource group belonging to that vCenter**
+
+```azurecli-interactive
+az connectedvmware vm create-from-machines --resource-group contoso-rg --vcenter-id /subscriptions/fedcba98-7654-3210-0123-456789abcdef/resourceGroups/contoso-rg-2/providers/Microsoft.HybridCompute/vcenters/contoso-vcenter
+```
+
+**Create VMware resources from all Arc for Server machines in the specified subscription belonging to that vCenter**
+
+```azurecli-interactive
+az connectedvmware vm create-from-machines --subscription contoso-sub --vcenter-id /subscriptions/fedcba98-7654-3210-0123-456789abcdef/resourceGroups/contoso-rg-2/providers/Microsoft.HybridCompute/vcenters/contoso-vcenter
+```
+
+### Required Parameters 
+
+**--vcenter-id -v**
+
+ARM ID of the vCenter to which the machines will be linked. 
+
+### Optional Parameters 
+
+**--ids**
+
+One or more resource IDs (space-delimited). It must be a complete resource ID containing all the information of *Resource Id* arguments. You must provide either *--ids* or other *Resource Id* arguments. 
+
+**--name -n**
+
+Name of the Microsoft.HybridCompute Machine resource. Provide this parameter if you want to convert a single machine to a VMware VM. 
+
+**--resource-group -g**
+
+Name of the resource group that will be scanned for HCRP machines. 
+
+>[!NOTE]
+>The default group configured using `az configure --defaults group=` is not used, and it must be specified explicitly.
+
+**--subscription**
+
+Name or ID of subscription. You can configure the default subscription using `az account set -s NAME_OR_ID`. 
+
+#### Known issue
+ 
+During the first scan of the vCenter inventory after onboarding to Azure Arc-enabled VMware vSphere, Arc-enabled Servers machines will be discovered under vCenter inventory. If the Arc-enabled Server machines aren't discovered and you try to perform the **Enable in Azure** operation, you'll encounter the following error:<br>
+
+*A machine '/subscriptions/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXXX/resourceGroups/rg-contoso/providers/Microsoft.HybridCompute/machines/testVM1' already exists with the specified virtual machine MoRefId: 'vm-4441'. The existing machine resource can be extended with private cloud capabilities by creating the VirtualMachineInstance resource under it.*
+
+When you encounter this error message, you'll be able to perform the **Link to vCenter** operation in 10 minutes. Alternatively, you can use any of the Azure CLI commands listed above to link an existing Arc-enabled Server machine to vCenter.
+
 ## Next steps
 
 [Set up and manage self-service access to VMware resources through Azure RBAC](setup-and-manage-self-service-access.md).

articles/azure-arc/vmware-vsphere/media/enable-virtual-hardware/link-machine-to-vcenter.png

@@ -2,7 +2,7 @@
 title: What is Azure Arc-enabled VMware vSphere?
 description: Azure Arc-enabled VMware vSphere extends Azure governance and management capabilities to VMware vSphere infrastructure and delivers a consistent management experience across both platforms. 
 ms.topic: overview
-ms.date: 03/07/2024
+ms.date: 03/13/2024
 ms.custom: references_regions
 ms.service: azure-arc
 ms.subservice: azure-arc-vmware-vsphere
@@ -73,6 +73,8 @@ Azure Arc-enabled VMware vSphere currently works with vCenter Server versions 7
 > [!NOTE]
 > Azure Arc-enabled VMware vSphere supports vCenters with a maximum of 9500 VMs. If your vCenter has more than 9500 VMs, we don't recommend you to use Arc-enabled VMware vSphere with it at this point.
 
+>If you're trying to enable Arc for Azure VMware Solution (AVS) private cloud, see [Deploy Arc-enabled VMware vSphere for Azure VMware Solution private cloud](../../azure-vmware/deploy-arc-for-azure-vmware-solution.md).
+
 ## Supported regions
 
 You can use Azure Arc-enabled VMware vSphere in these supported regions:

articles/azure-arc/vmware-vsphere/media/enable-virtual-hardware/perform-virtual-hardware-operations.png

@@ -3,7 +3,7 @@ title: Connect VMware vCenter Server to Azure Arc by using the helper script
 description: In this quickstart, you learn how to use the helper script to connect your VMware vCenter Server instance to Azure Arc.
 ms.topic: quickstart 
 ms.custom: references_regions
-ms.date: 02/22/2024
+ms.date: 03/13/2024
 ms.service: azure-arc
 ms.subservice: azure-arc-vmware-vsphere
 author: Farha-Bano
@@ -20,7 +20,7 @@ To start using the Azure Arc-enabled VMware vSphere features, you need to connec
 First, the script deploys a virtual appliance called [Azure Arc resource bridge](../resource-bridge/overview.md) in your vCenter environment. Then, it installs a VMware cluster extension to provide a continuous connection between vCenter Server and Azure Arc.
 
 > [!IMPORTANT]
-> This article describes a way to connect a generic vCenter Server to Azure Arc. If you're trying to enable Arc for Azure VMware Solution (AVS) private cloud, please follow this guide instead - [Deploy Arc for Azure VMware Solution](../../azure-vmware/deploy-arc-for-azure-vmware-solution.md). With the Arc for AVS onboarding process you need to provide fewer inputs and Arc capabilities are better integrated into the AVS private cloud portal experience. 
+> This article describes a way to connect a generic vCenter Server to Azure Arc. If you're trying to enable Arc for Azure VMware Solution (AVS) private cloud, follow this guide instead - [Deploy Arc-enabled VMware vSphere for Azure VMware Solution private cloud](../../azure-vmware/deploy-arc-for-azure-vmware-solution.md). With the Arc for AVS onboarding process you need to provide fewer inputs and Arc capabilities are better integrated into the AVS private cloud portal experience. 
 
 ## Prerequisites
 

articles/azure-arc/vmware-vsphere/overview.md

@@ -2,7 +2,7 @@
 title: Switch to the new version
 description: Learn how to switch to the new version of Azure Arc-enabled VMware vSphere and use its capabilities.
 ms.topic: how-to 
-ms.date: 02/28/2024
+ms.date: 03/13/2024
 ms.service: azure-arc
 ms.subservice: azure-arc-vmware-vsphere
 author: Farha-Bano
@@ -19,7 +19,7 @@ On August 21, 2023, we rolled out major changes to **Azure Arc-enabled VMware vS
 If you onboarded to Azure Arc-enabled VMware vSphere before **August 21, 2023**, and your VMs were Azure-enabled, you'll encounter the following breaking changes:
 
 - For the VMs with Arc agents, starting from **February 27, 2024**, you'll no longer be able to perform any Azure management service-related operations.  
-- From **March 15, 2024**, you'll no longer be able to perform any operations on the VMs, except the **Remove from Azure** operation. 
+- From **April 1, 2024**, you'll no longer be able to perform any operations on the VMs, except the **Remove from Azure** operation. 
 
 To continue using these machines, follow these instructions to switch to the new version.
 

articles/azure-arc/vmware-vsphere/quick-start-connect-vcenter-to-arc-using-script.md

@@ -26,7 +26,7 @@
       href: support-matrix-for-arc-enabled-vmware-vsphere.md
     - name: Enable VMware vCenter resources in Azure
       href: browse-and-enable-vcenter-resources-in-azure.md
-    - name: Enable virtual hardware and VM CRUD capabilities in a machine with Arc agent installed
+    - name: Enable additional capabilities on Arc-enabled Server machines by linking to vCenter
       href: enable-virtual-hardware.md
   - name: Use Azure Management services for VMware VMs
     items: