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
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ In this article, learn how to rotate the cloud admin credentials (vCenter Server
19
19
20
20
Consider and determine which services connect to vCenter Server as `[email protected]` or NSX as cloud admin before you rotate the password. Services can include VMware services like HCX, vRealize Orchestrator, vRealize Operations Manager, VMware Horizon, or other non-Microsoft tools that are used for monitoring or provisioning.
21
21
22
-
One way to determine which services authenticate to vCenter Server with the cloud admin user is to inspect vSphere events by using the vSphere Client for your private cloud. After you identify those services, you need to stop them before rotating the password. If you dont stop those services, they won't work after you rotate the password. You can also experience temporary locks on your vCenter Server cloud admin account. Locks occur because these services continuously attempt to authenticate by using a cached version of the old credentials.
22
+
One way to determine which services authenticate to vCenter Server with the cloud admin user is to inspect vSphere events by using the vSphere Client for your private cloud. After you identify those services, you need to stop them before rotating the password. If you don't stop those services, they won't work after you rotate the password. You can also experience temporary locks on your vCenter Server cloud admin account. Locks occur because these services continuously attempt to authenticate by using a cached version of the old credentials.
23
23
24
24
Instead of using the cloud admin user to connect services to vCenter Server or NSX, we recommend that you use individual accounts for each service. For more information about setting up separate accounts for connected services, see [Access and identity architecture](./architecture-identity.md).
0 commit comments