Skip to content

Commit b943a7b

Browse files
authored
Merge pull request #1 from rvandenbedem/rvandenbedem-patch-1
Corrected VMware product naming
2 parents 8eee902 + e778110 commit b943a7b

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/azure-vmware/rotate-cloudadmin-credentials.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ description: Learn how to rotate the vCenter Server credentials for your Azure V
44
ms.topic: how-to
55
ms.service: azure-vmware
66
ms.custom: devx-track-azurecli
7-
ms.date: 8/15/2023
8-
#Customer intent: As an Azure service administrator, I want to rotate my cloudadmin credentials so that the HCX Connector has the latest vCenter Server CloudAdmin credentials.
7+
ms.date: 8/16/2023
8+
# Customer intent: As an Azure service administrator, I want to rotate my cloudadmin credentials so that the HCX Connector has the latest vCenter Server CloudAdmin credentials.
99
---
1010

1111
# Rotate the cloudadmin credentials for Azure VMware Solution
@@ -22,13 +22,13 @@ Consider and determine which services connect to vCenter Server as *cloudadmin@v
2222

2323
One way to determine which services authenticate to vCenter Server with the cloudadmin user is to inspect vSphere events using the vSphere Client for your private cloud. After you identify such services, and before rotating the password, you must stop these services. Otherwise, the services won't work after you rotate the password. You'll also experience temporary locks on your vCenter Server CloudAdmin account, as these services continuously attempt to authenticate using a cached version of the old credentials.
2424

25-
Instead of using the cloudadmin user to connect services to vCenter Server or NSX-T, we recommend individual accounts for each service. For more information about setting up separate accounts for connected services, see [Access and Identity Concepts](./concepts-identity.md).
25+
Instead of using the cloudadmin user to connect services to vCenter Server or NSX-T Data Center, we recommend individual accounts for each service. For more information about setting up separate accounts for connected services, see [Access and Identity Concepts](./concepts-identity.md).
2626

2727
## Reset your vCenter Server credentials
2828

2929
### [Portal](#tab/azure-portal)
3030

31-
1. In your Azure VMware Solution private cloud, select **VMWare credentials**.
31+
1. In your Azure VMware Solution private cloud, select **VMware credentials**.
3232
1. Select **Generate new password** under vCenter Server credentials.
3333
1. Select the confirmation checkbox and then select **Generate password**.
3434

@@ -65,15 +65,15 @@ To begin using Azure CLI:
6565

6666
4. Provide the new vCenter Server user credentials and select **Edit**, which saves the credentials. Save should show successful.
6767

68-
## Reset your NSX-T manager credentials
68+
## Reset your NSX-T Manager credentials
6969

70-
1. In your Azure VMware Solution private cloud, select **VMWare credentials**.
70+
1. In your Azure VMware Solution private cloud, select **VMware credentials**.
7171
1. Select **Generate new password** under NSX-T Manager credentials.
7272
1. Select the confirmation checkbox and then select **Generate password**.
7373

7474
## Next steps
7575

76-
Now that you've covered resetting your vCenter Server and NSX-T credentials for Azure VMware Solution, you may want to learn about:
76+
Now that you've covered resetting your vCenter Server and NSX-T Manager credentials for Azure VMware Solution, you may want to learn about:
7777

7878
- [Integrating Azure native services in Azure VMware Solution](integrate-azure-native-services.md)
7979
- [Deploying disaster recovery for Azure VMware Solution workloads using VMware HCX](deploy-disaster-recovery-using-vmware-hcx.md)

0 commit comments

Comments
 (0)