Merge pull request #312084 from suzuber/article-refresh-lines-29-40

Azure article refresh sheet lines 29-40

Author: prmerger-automator[bot]

articles/azure-vmware/azure-vmware-solution-citrix.md

@@ -3,7 +3,7 @@ title: Deploy Citrix on Azure VMware Solution
 description: Learn how to deploy VMware Citrix on Azure VMware Solution.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 11/27/2023
+ms.date: 3/04/2026
 ms.custom: engagement-fy23
 # Customer intent: "As an IT administrator, I want to deploy Citrix Virtual Apps and Desktops on Azure VMware Solution, so that I can leverage cloud infrastructure for provisioning my Virtual Delivery Agent workloads and ensure seamless migration or hybrid operation with existing on-premises environments."
 ---
@@ -29,7 +29,7 @@ Citrix Virtual Apps and Desktop service supports Azure VMware Solution. Azure VM
 
     A. Yes. You’re free to migrate, operate a hybrid environment, or deploy a standalone directly into Azure VMware Solution.
 
-- Q. Does Azure VMware Solution support both PVS and MCS?
+- Q. Does Azure VMware Solution support both Citrix Provisioning (PVS) and Machine Creation Services (MCS)?
 
     A. Yes.
 
@@ -51,4 +51,4 @@ Citrix Virtual Apps and Desktop service supports Azure VMware Solution. Azure VM
 
 - Q. How do I purchase Citrix Virtual Apps and Desktops service to use Azure VMware Solution?
 
-    A. You can purchase Citrix offerings via your Citrix partner or directly from the Azure Marketplace.
+    A. You can purchase Citrix offerings via your Citrix partner or directly from Azure Marketplace.

articles/azure-vmware/bitnami-appliances-deployment.md

@@ -3,7 +3,7 @@ title: Deploy Bitnami virtual appliances
 description: Learn about the virtual appliances packed by Bitnami to deploy in your Azure VMware Solution private cloud.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 12/24/2024
+ms.date: 3/04/2026
 ms.custom: engagement-fy23
 # Customer intent: "As a cloud administrator, I want to deploy Bitnami virtual appliances in my Azure VMware Solution private cloud, so that I can streamline the installation and configuration of essential applications for my development and production environments."
 ---
@@ -49,7 +49,7 @@ In this article, learn how to install and configure the following virtual applia
 
    - [RabbitMQ](https://marketplace.cloud.vmware.com/services/details/rabbitmq?slug=true)
 
-1. Select the version, select **Download**, and then accept the EULA license. 
+1. Select the version, select **Download**, and then accept the **EULA license**. 
 
    >[!NOTE]
    >Make sure the file is accessible from the virtual machine.
@@ -63,9 +63,9 @@ In this article, learn how to install and configure the following virtual applia
 
 1. Select your private cloud, and then **Manage** > **Identity**.
 
-1. Copy the vCenter Server URL, username, and password. You'll use them to access your virtual machine (VM). 
+1. Copy the vCenter Server URL, username, and password. Use them to access your virtual machine (VM). 
 
-1. Select **Overview**, select the VM, and then connect to it through RDP. If you need help with connecting, see [connect to a virtual machine](/azure/virtual-machines/windows/connect-logon#connect-to-the-virtual-machine) for details.
+1. Select **Overview**, select the VM, and then connect to it through remote desktop protocol(RDP). If you need help with connecting, see [connect to a virtual machine](/azure/virtual-machines/windows/connect-logon#connect-to-the-virtual-machine) for details.
 
 1. In the VM, open a browser and navigate to the vCenter URL. 
 
@@ -95,20 +95,20 @@ In this article, learn how to install and configure the following virtual applia
 
 1. Review the configuration settings and then select **Finish**.
 
-1. From the **Task Console**, verify that the status of the OVF template deployment has completed successfully.
+1. From the **Task Console**, verify that the status of the OVF template deployment completed successfully.
 
 1. After the installation finishes, under **Actions**, select **Power on** to turn on the appliance. 
 
 1. From the vCenter Server console, select **Launch Web Console** and sign in to the Bitnami virtual appliance. Check the [Bitnami virtual appliance support documentation](https://docs.bitnami.com/vmware-marketplace/faq/get-started/find-credentials/) for the default username and password.
 
    >[!NOTE]
-   >You can change the default password to a more secure one. For more information, see ...
+   >You can change the default password to a more secure one.
 
 
 
 ## Step 4: Assign a static IP to the virtual appliance
 
-In this step, you'll modify the *bootproto* and *onboot* parameters and assign a static IP address to the Bitnami virtual appliance. 
+In this step, modify the *bootproto* and *onboot* parameters and assign a static IP address to the Bitnami virtual appliance. 
 
 1. Search for the network configuration file. 
 
@@ -147,7 +147,7 @@ In this step, you'll modify the *bootproto* and *onboot* parameters and assign a
 
 ## Step 5: Enable SSH access to the virtual appliance
 
-In this step, you'll enable SSH on your virtual appliance for remote access control. The SSH service is disabled by default. You'll also use an OpenSSH client to connect to the host console.
+In this step, enable SSH on your virtual appliance for remote access control. The SSH service is disabled by default. You use an OpenSSH client to connect to the host console.
 
 1. Enable and start the SSH service.
 

articles/azure-vmware/configure-hcx-network-extension.md

@@ -3,7 +3,7 @@ title: Create an HCX network extension
 description: Learn how to extend any networks from your on-premises environment to Azure VMware Solution.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 12/06/2023
+ms.date: 3/02/2026
 ms.custom: engagement-fy23
 # Customer intent: "As a network administrator, I want to extend my on-premises networks to Azure VMware Solution, so that I can ensure seamless connectivity and integration between my existing infrastructure and the cloud environment."
 ---

articles/azure-vmware/configure-vmware-syslogs.md

@@ -48,11 +48,11 @@ A Log Analytics workspace:
 
 * Is the workspace from which you can take desired actions, such as querying for logs.
 
-In this section, you’ll:
+In this section, you learn to:
 
-* Configure a Log Analytics workspace
+* Configure a Log Analytics workspace.
 
-* Create a diagnostic setting in your private cloud to send your logs to this workspace
+* Create a diagnostic setting in your private cloud to send your logs to this workspace.
 
 #### Create a resource
 

articles/azure-vmware/configure-vsan.md

@@ -3,7 +3,7 @@ title: Configure VMware vSAN
 description:  Learn how to configure VMware vSAN.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 12/07/2023
+ms.date: 2/20/2026
 ms.custom:
   - engagement-fy23
   - build-2025
@@ -50,15 +50,15 @@ To enable or disable the TRIM/UNMAP command, run the `Set-AVSVSANClusterUNMAPTRI
 
    | Field | Value |
    | --- | --- |
-   | **Name**  | The cluster name as defined in vCenter Server. Comma delimit to target only certain clusters. (Blank targets all clusters.) |
+   | **Name**  | The cluster name as defined in vCenter Server. Comma delimits to target only certain clusters. (Blank targets all clusters.) |
    | **Enable**  | `true` or `false`. |
    | **Retain up to**  | Retention period of the cmdlet output. The default value is `60`.  |
    | **Specify name for execution**  | Alphanumeric name. For example, *Disable vSAN TRIMUNMAP*.  |
    | **Timeout**  |  The period after which a cmdlet exits if it's taking too long to finish.  |
 
 1. Check **Notifications** to see the progress.
 
-After vSAN TRIM/UNMAP is enabled, you must meet certain prerequisites in order for the command to function as intended and successfully reclaim unused capacity. The VM-level prerequisites are:
+After vSAN TRIM/UNMAP is enabled, you must meet certain prerequisites in order for the command to function as intended and successfully reclaim unused capacity. The virtual machine (VM)-level prerequisites are:
 
 - Virtual machine hardware version 11 or later for Windows.
 - Virtual machine hardware version 13 or later for Linux.
@@ -88,7 +88,7 @@ To set your preferred space efficiency model, run the `Set-vSANCompressDedupe` c
    | --- | --- |
    | **Compression**  | `true` or `false`. |
    | **Deduplication**  | `true` or `false`. (When you enable deduplication, you enable both deduplication and compression.) |
-   | **ClustersToChange**  | The cluster name as defined in vCenter Server. Comma delimit to target multiple clusters. |
+   | **ClustersToChange**  | The cluster name as defined in vCenter Server. Comma delimits to target multiple clusters. |
    | **Retain up to**  | Retention period of the cmdlet output. The default value is `60`.  |
    | **Specify name for execution**  | Alphanumeric name. For example, *set cluster-1 to compress only*.  |
    | **Timeout**  |  The period after which a cmdlet exits if taking too long to finish.  |

articles/azure-vmware/connect-multiple-private-clouds-same-region.md

@@ -3,7 +3,7 @@ title: Connect multiple Azure VMware Solution private clouds in the same region
 description: Learn how to create a network connection between two or more Azure VMware Solution private clouds located in the same region.
 ms.topic: how-to 
 ms.service: azure-vmware
-ms.date: 1/8/2024
+ms.date: 2/20/2026
 ms.custom: engagement-fy23
 # Customer intent: As a cloud architect, I want to establish network connections between multiple Azure VMware Solution private clouds in the same region, so that I can enable communication and optimize resource management across these environments.
 ---
@@ -16,10 +16,10 @@ You can connect a private cloud to multiple private clouds, and the connections
 
 You can only connect private clouds in the same region. To connect private clouds in different regions, [use ExpressRoute Global Reach](tutorial-expressroute-global-reach-private-cloud.md) to connect them in the same way you connect your private cloud to your on-premises circuit.
 
-:::image type="content" source="media/networking/avs-interconnect.png" alt-text="Diagram of the AVS Interconnect Topology for 3 private clouds connected in one region." border="true" lightbox="media/networking/avs-interconnect.png":::
+:::image type="content" source="media/networking/avs-interconnect.png" alt-text="Diagram of the AVS Interconnect Topology for three private clouds connected in one region." border="true" lightbox="media/networking/avs-interconnect.png":::
 
 >[!NOTE]
->AVS Interconnect is based on Global Reach feature for both interconnection to same\different region. Please [check the Global Reach availability for your AVS deployment](../../articles/expressroute/expressroute-global-reach.md)
+>AVS Interconnect is based on Global Reach feature for both interconnection to same\different region. [Check the Global Reach availability for your AVS deployment](../../articles/expressroute/expressroute-global-reach.md)
 
 ## Supported regions
 
@@ -33,7 +33,7 @@ The Azure VMware Solution Interconnect feature is available in all regions.
 >[!NOTE]
 >The **AVS Interconnect** feature doesn't check for overlapping IP space the way native Azure vNet peering does before creating the peering. Therefore, it's your responsibility to ensure that there isn't overlap between the private clouds.
 >
->In Azure VMware Solution environments, it's possible to configure non-routed, overlapping IP deployments on NSX segments that aren't routed to Azure. These don't cause issues with the AVS Interconnect feature, as it only routes between the NSX-T Data Center T0 gateway on each private cloud.
+>In Azure VMware Solution environments, it's possible to configure nonrouted, overlapping IP deployments on NSX segments that aren't routed to Azure. These don't cause issues with the AVS Interconnect feature, as it only routes between the NSX-T Data Center T0 gateway on each private cloud.
 
 ## Add connection between private clouds
 
@@ -46,14 +46,14 @@ The Azure VMware Solution Interconnect feature is available in all regions.
 3. Select the information and Azure VMware Solution private cloud for the new connection.
 
    >[!NOTE]
-   >You can only connect to private clouds in the same region. To connect to private clouds that are in different regions, [use ExpressRoute Global Reach](tutorial-expressroute-global-reach-private-cloud.md) to connect your private clouds in the same way you connect your private cloud to your on-premises circuit. 
+   >You can only connect to private clouds in the same region. To connect to private clouds in different regions, [use ExpressRoute Global Reach](tutorial-expressroute-global-reach-private-cloud.md) to connect your private clouds in the same way you connect your private cloud to your on-premises circuit. 
 
    :::image type="content" source="media/networking/add-connection-to-other-private-cloud.png" alt-text="Screenshot showing the required information to add a connection to other private cloud." border="true":::
 
 
 4. Select the **I confirm** checkbox acknowledging that there are no overlapping routed IP spaces in the two private clouds. 
 
-5. Select **Create**.  You can check the status of the connection creation.
+5. Select **Create**. You can check the status of the connection creation.
 
    :::image type="content" source="media/networking/add-connection-to-other-private-cloud-notification.png" alt-text="Screenshot showing the Notification information for connection in progress and an existing connection." border="true":::