Doc updates

Author: Farha-Bano

articles/azure-arc/vmware-vsphere/enable-guest-management-at-scale.md

@@ -2,7 +2,7 @@
 title: Install Arc agent at scale for your VMware VMs
 description: Learn how to enable guest management at scale for Arc enabled VMware vSphere VMs. 
 ms.topic: how-to
-ms.date: 04/22/2024
+ms.date: 04/23/2024
 ms.service: azure-arc
 ms.subservice: azure-arc-vmware-vsphere
 author: Farha-Bano
@@ -34,7 +34,7 @@ Ensure the following before you install Arc agents at scale for VMware VMs:
       > [!NOTE]
       > If you're using a Linux VM, the account must not prompt for login on sudo commands. To override the prompt, from a terminal, run `sudo visudo`, and add `<username> ALL=(ALL) NOPASSWD:ALL` at the end of the file. Ensure you replace `<username>`. <br> <br>If your VM template has these changes incorporated, you won't need to do this for the VM created from that template.
 
-## Approach A: Install Arc agents at scale from portal
+### Approach A: Install Arc agents at scale from portal
 
 An admin can install agents for multiple machines from the Azure portal if the machines share the same administrator credentials.
 
@@ -56,7 +56,7 @@ An admin can install agents for multiple machines from the Azure portal if the m
 > [!NOTE]
 > For Windows VMs, the account must be part of local administrator group; and for Linux VM, it must be a root account.
 
-## Approach B: Install Arc agents using AzCLI commands
+### Approach B: Install Arc agents using AzCLI commands
 
 The following Azure CLI commands can be used to install Arc agents.  
 
@@ -74,17 +74,17 @@ az connectedvmware vm guest-agent enable --password
                                          [--no-wait]
 ```
 
-## Approach C: Install Arc agents at scale using helper script
+### Approach C: Install Arc agents at scale using helper script
 
 Arc agent installation can be automated using the helper script built using the AzCLI command provided [here](./enable-guest-management-at-scale.md#approach-b-install-arc-agents-using-azcli-commands). Download this [helper script](https://aka.ms/arcvmwarebatchenable) to enable VMs and install Arc agents at scale. In a single ARM deployment, the helper script can enable and install Arc agents on 200 VMs.  
 
-### Features of the script
+#### Features of the script
 
 - Creates a log file (vmware-batch.log) for tracking its operations.
 
-- Generates a list of Azure portal links to all the deployments created (all-deployments-<timestamp>.txt). 
+- Generates a list of Azure portal links to all the deployments created `(all-deployments-<timestamp>.txt)`. 
 
-- Creates ARM deployment files (vmw-dep-<timestamp>-<batch>.json). 
+- Creates ARM deployment files `(vmw-dep-<timestamp>-<batch>.json)`.
 
 - Can enable up to 200 VMs in a single ARM deployment if guest management is enabled, else enables 400 VMs. 
 
@@ -94,15 +94,15 @@ Arc agent installation can be automated using the helper script built using the
 
 Before running this script, install az cli and the connectedvmware extension. 
 
-### Prerequisites 
+#### Prerequisites 
 
 Before running this script, install: 
 
 - Azure CLI from [here](/cli/azure/install-azure-cli).
 
 - The `connectedvmware` extension for Azure CLI: Install it by running `az extension add --name connectedvmware`. 
 
-# Usage 
+## Usage 
 
 1. Download the script to your local machine. 
 
@@ -112,7 +112,7 @@ Before running this script, install:
 
 4. Run the script with the required parameters. For example, `.\arcvmware-batch-enablement.ps1 -VCenterId "<vCenterId>" -EnableGuestManagement -VMCountPerDeployment 3 -DryRun`. Replace `<vCenterId>` with the ARM ID of your vCenter. 
 
-# Parameters
+## Parameters
 
 - `VCenterId`: The ARM ID of the vCenter where the VMs are located. 
 
@@ -122,15 +122,13 @@ Before running this script, install:
 
 - `DryRun`: If this switch is specified, the script will only create the ARM deployment files. Else, the script will also deploy the ARM deployments. 
 
-# Running as a Cron Job 
+## Running as a Cron Job 
 
 You can set up this script to run as a cron job using the Windows Task Scheduler. Here's a sample script to create a scheduled task: 
 
 ```azurecli
 $action = New-ScheduledTaskAction -Execute 'powershell.exe' -Argument '-File "C:\Path\To\vmware-batch-enable.ps1" -VCenterId "<vCenterId>" -EnableGuestManagement -VMCountPerDeployment 3 -DryRun' 
-
 $trigger = New-ScheduledTaskTrigger -Daily -At 3am 
-
 Register-ScheduledTask -Action $action -Trigger $trigger -TaskName "EnableVMs" 
 ```
 
@@ -142,7 +140,7 @@ To unregister the task, run the following command:
 Unregister-ScheduledTask -TaskName "EnableVMs"
 ```
 
-## Approach D: Install Arc agents at scale using out-of-band approach 
+### Approach D: Install Arc agents at scale using out-of-band approach 
 
 Arc agents can be installed directly on machines without relying on VMware tools or APIs. By following the out-of-band approach, initially onboard the machines as Arc-enabled Server resources with Resource type as Microsoft.HybridCompute/machines. After that, perform **Link to vCenter** operation to update the machine's Kind property as VMware, enabling virtual lifecycle operations.  
 
@@ -160,21 +158,21 @@ b. **Link Arc-enabled Server resources to the vCenter:** The following commands
 
    - The following command scans all the Arc for Server machines that belong to the vCenter in the specified subscription and links the machines with that vCenter. 
 
-    ```azurecli
-    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
-    ```
+   ```azurecli
+   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
+   ```
 
    - The following command scans all the Arc for Server machines that belong to the vCenter in the specified Resource Group and links the machines with that vCenter. 
 
-    ```azurecli
-    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.
-    ```
+   ```azurecli
+   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.
+   ```
 
    - The following command can be used to link an individual Arc for Server resource to vCenter. 
 
-    ```azurecli
-    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
-    ```
+   ```azurecli
+   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
+   ```
 
 ## Next steps
 

articles/azure-arc/vmware-vsphere/support-matrix-for-arc-enabled-vmware-vsphere.md

@@ -2,7 +2,7 @@
 title: Plan for deployment
 description: Learn about the support matrix for Arc-enabled VMware vSphere including vCenter Server versions supported, network requirements, and more.
 ms.topic: how-to 
-ms.date: 04/22/2024
+ms.date: 04/23/2024
 ms.service: azure-arc
 ms.subservice: azure-arc-vmware-vsphere
 author: Farha-Bano
@@ -62,11 +62,11 @@ In addition, VMware VSphere requires the following exception:
 | **Service** | **Port** | **URL** | **Direction** | **Notes**|
 | --- | --- | --- | --- | --- |
 | vCenter Server | 443 | URL of the vCenter server  | Appliance VM IP and control plane endpoint need outbound connection. | Used to by the vCenter server to communicate with the Appliance VM and the control plane.|
-| VMware Cluster Extension | 443 | azureprivatecloud.azurecr.io | Appliance VM IPs need outbound connection. | Pull container images for Microsoft.VMWare and Microsoft.AVS Cluster Extension.|
-| Azure CLI and Azure CLI Extensions | 443 | *.blob.core.windows.net | Management machine needs outbound connection. | Download Azure CLI Installer and Azure CLI extensions.|
-| Azure Resource Manager | 443 | management.azure.com | Management machine needs outbound connection. | Required to create/update resources in Azure using ARM.|
-| Helm Chart for Azure Arc Agents | 443 | *.dp.kubernetesconfiguration.azure.com | Management machine needs outbound connection. | Data plane endpoint for downloading the configuration information of Arc agents.|
-| Azure CLI | 443 | - login.microsoftonline.com <br> <br> - aka.ms | Management machine needs outbound connection. | Required to fetch and update Azure Resource Manager tokens.|
+| VMware Cluster Extension | 443 | `azureprivatecloud.azurecr.io` | Appliance VM IPs need outbound connection. | Pull container images for Microsoft.VMWare and Microsoft.AVS Cluster Extension.|
+| Azure CLI and Azure CLI Extensions | 443 | `*.blob.core.windows.net` | Management machine needs outbound connection. | Download Azure CLI Installer and Azure CLI extensions.|
+| Azure Resource Manager | 443 | `management.azure.com` | Management machine needs outbound connection. | Required to create/update resources in Azure using ARM.|
+| Helm Chart for Azure Arc Agents | 443 | `*.dp.kubernetesconfiguration.azure.com` | Management machine needs outbound connection. | Data plane endpoint for downloading the configuration information of Arc agents.|
+| Azure CLI | 443 | - `login.microsoftonline.com` <br> <br> - `aka.ms` | Management machine needs outbound connection. | Required to fetch and update Azure Resource Manager tokens.|
 
 For a complete list of network requirements for Azure Arc features and Azure Arc-enabled services, see [Azure Arc network requirements (Consolidated)](../network-requirements-consolidated.md).