Skip to content

Commit 7e1c342

Browse files
committed
refresh updates
1 parent d89c659 commit 7e1c342

2 files changed

Lines changed: 6 additions & 6 deletions

File tree

articles/azure-vmware/integrate-azure-native-services.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Monitor and protect VMs with Azure native services
33
description: Learn how to integrate and deploy Microsoft Azure native tools to monitor and manage your Azure VMware Solution workloads.
44
ms.topic: how-to
55
ms.service: azure-vmware
6-
ms.date: 3/21/2024
6+
ms.date: 3/13/2026
77
ms.custom: engagement-fy23
88
# Customer intent: As an IT administrator managing hybrid cloud environments, I want to integrate Azure native services with Azure VMware Solution, so that I can effectively monitor, manage, and protect my virtual machines throughout their lifecycle.
99
---
@@ -47,14 +47,14 @@ The diagram shows the integrated monitoring architecture for Azure VMware Soluti
4747
The guest management must be enabled on the VMware vSphere virtual machine (VM) before you can install an extension. Use the following prerequisite steps to enable guest management.
4848
### Prerequisites
4949
- Navigate to Azure portal.
50-
- Locate the VMware vSphere VM you want to check for guest management and install extensions on, select the name of the VM.
50+
- Locate the VMware vSphere VM you want to check for guest management and install extensions on.Select the name of the VM.
5151
- Select **Configuration** from the left navigation for a VMware VM.
5252
- Verify **Enable guest management** is checked.
5353

5454
The following conditions are necessary to enable guest management on a VM.
5555
- The machine must be running a supported operating system.
5656
- The machine needs to connect through the firewall to communicate over the internet. Make sure the URLs listed aren't blocked.
57-
- The machine can't be behind a proxy, it isn't currently supported.
57+
- The machine can't be behind a proxy. It isn't currently supported.
5858
- If you're using Linux VM, the account must not prompt to sign in on pseudo commands.
5959
- To avoid pseudo commands, follow these steps:
6060
1. Sign in to Linux VM.

articles/azure-vmware/manage-arc-enabled-azure-vmware-solution.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Manage Arc-enabled Azure VMware private cloud
33
description: Learn how to manage your Arc-enabled Azure VMware private cloud.
44
ms.topic: how-to
55
ms.service: azure-vmware
6-
ms.date: 2/6/2024
6+
ms.date: 3/13/2026
77
ms.custom: references_regions, engagement-fy23
88
# Customer intent: As a cloud administrator, I want to manage the Arc-enabled Azure VMware private cloud, so that I can ensure the system is secure, well-maintained, and efficiently connected to Azure services.
99
---
@@ -17,7 +17,7 @@ In this article, learn how to update the Arc appliance credentials, upgrade the
1717

1818
When **cloud admin** credentials are updated, use the following steps to update the credentials in the appliance store.
1919

20-
1. Sign in to the Management VM from where the onboard process was performed. Change the directory to **onboarding directory**.
20+
1. Sign in to the Management virtual machine (VM) from where the onboard process was performed. Change the directory to **onboarding directory**.
2121
1. Run the following command:
2222
For Windows-based Management VM.
2323

@@ -36,7 +36,7 @@ When **cloud admin** credentials are updated, use the following steps to upd
3636
`az connectedvmware vcenter connect --debug --resource-group {resource-group} --name {vcenter-name-in-azure} --location {vcenter-location-in-azure} --custom-location {custom-location-name} --fqdn {vcenter-ip} --port {vcenter-port} --username [email protected] --password {vcenter-password}`
3737

3838
> [!NOTE]
39-
> Customers need to ensure kubeconfig and SSH keys remain available as they will be required for log collection, appliance Upgrade, and credential rotation. These parameters will be required at the time of upgrade, log collection, and credential update scenarios.
39+
> Customers need to ensure kubeconfig and SSH keys remain available as they're required for log collection, appliance Upgrade, and credential rotation. These parameters are required at the time of upgrade, log collection, and credential update scenarios.
4040
4141
**Parameters**
4242

0 commit comments

Comments
 (0)