You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-vmware/rotate-cloudadmin-credentials.md
+16-21Lines changed: 16 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,34 +4,35 @@ description: Learn how to rotate the vCenter Server credentials for your Azure V
4
4
ms.topic: how-to
5
5
ms.service: azure-vmware
6
6
ms.custom: devx-track-azurecli
7
-
ms.date: 12/22/2022
7
+
ms.date: 8/15/2023
8
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.
9
9
---
10
10
11
+
12
+
13
+
11
14
# Rotate the cloudadmin credentials for Azure VMware Solution
12
15
13
-
>[!IMPORTANT]
14
-
>Currently, rotating your NSX-T Manager *cloudadmin* credentials isn't supported. To rotate your NSX-T Manager password, submit a [support request](https://rc.portal.azure.com/#create/Microsoft.Support). This process might impact running HCX services.
15
16
16
-
In this article, you'll rotate the cloudadmin credentials (vCenter Server *CloudAdmin* credentials) for your Azure VMware Solution private cloud. Although the password for this account doesn't expire, you can generate a new one at any time.
17
+
In this article, you'll rotate the cloudadmin credentials (vCenter Server and NSX-T *CloudAdmin* credentials) for your Azure VMware Solution private cloud. Although the password for this account doesn't expire, you can generate a new one at any time.
17
18
18
19
>[!CAUTION]
19
-
>If you use your cloudadmin credentials to connect services to vCenter Server in your private cloud, those connections will stop working once you rotate your password. Those connections will also lock out the cloudadmin account unless you stop those services before rotating the password.
20
+
>If you use your cloudadmin credentials to connect services to vCenter Server or NSX-T in your private cloud, those connections will stop working once you rotate your password. Those connections will also lock out the cloudadmin account unless you stop those services before rotating the password.
20
21
21
22
## Prerequisites
22
23
23
-
Consider and determine which services connect to vCenter Server as *[email protected]* before you rotate the password. These services may include VMware services such as HCX, vRealize Orchestrator, vRealize Operations Manager, VMware Horizon, or other third-party tools used for monitoring or provisioning.
24
+
Consider and determine which services connect to vCenter Server as *[email protected]*or NSX-T as cloudadmin before you rotate the password. These services may include VMware services such as HCX, vRealize Orchestrator, vRealize Operations Manager, VMware Horizon, or other third-party tools used for monitoring or provisioning.
24
25
25
26
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.
26
27
27
-
Instead of using the cloudadmin user to connect services to vCenter Server, 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).
28
+
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).
28
29
29
30
## Reset your vCenter Server credentials
30
31
31
32
### [Portal](#tab/azure-portal)
32
33
33
34
1. In your Azure VMware Solution private cloud, select **VMWare credentials**.
34
-
1. Select **Generate new password**.
35
+
1. Select **Generate new password** under vCenter Server credentials.
35
36
1. Select the confirmation checkbox and then select **Generate password**.
36
37
37
38
@@ -52,17 +53,7 @@ To begin using Azure CLI:
52
53
53
54
---
54
55
55
-
56
-
57
-
58
-
59
-
60
-
61
-
62
-
63
-
64
-
65
-
## Update HCX Connector
56
+
### Update HCX Connector
66
57
67
58
1. Go to the on-premises HCX Connector at https://{ip of the HCX connector appliance}:443 and sign in using the new credentials.
68
59
@@ -76,11 +67,15 @@ To begin using Azure CLI:
76
67
77
68
4. Provide the new vCenter Server user credentials and select **Edit**, which saves the credentials. Save should show successful.
78
69
70
+
## Reset your NSX-T manager credentials
71
+
72
+
1. In your Azure VMware Solution private cloud, select **VMWare credentials**.
73
+
1. Select **Generate new password** under NSX-T Manager credentials.
74
+
1. Select the confirmation checkbox and then select **Generate password**.
75
+
79
76
## Next steps
80
77
81
78
Now that you've covered resetting your vCenter Server credentials for Azure VMware Solution, you may want to learn about:
82
79
83
80
-[Integrating Azure native services in Azure VMware Solution](integrate-azure-native-services.md)
84
81
-[Deploying disaster recovery for Azure VMware Solution workloads using VMware HCX](deploy-disaster-recovery-using-vmware-hcx.md)
0 commit comments