To manage your vCenter Server instances in vRealize Operations, you must configure a cloud account for each vCenter Server instance. The cloud account requires the credentials that are used for communication with the target vCenter Server.

Note: Any cloud account credentials you add are shared with other cloud account administrators and vRealize Operations collector hosts. Other administrators might use these credentials to configure a new cloud account or to move a cloud account to a new host.


  • Verify that you know the vCenter Server credentials that have sufficient privileges to connect and collect data, see Privileges Required for Configuring a vCenter Adapter Instance. If the provided credentials have limited access to objects in vCenter Server, all users, regardless of their vCenter Server privileges see only the objects that the provided credentials can access. At a minimum, the user account must have Read privileges and the Read privileges must be assigned at the data center or vCenter Server level.


  1. From the left menu, click Data Sources > Integrations > Accounts tab.
  2. Click Add Accounts.
  3. On the Accounts Type page, click vCenter.
  4. Enter a display name and description for the cloud account.
    • Display name. Enter the name for the vCenter Server instance as you want it to appear in vRealize Operations. A common practice is to include the IP address so that you can readily identify and differentiate between instances.
    • Description. Enter any additional information that helps you manage your instances.
  5. In the vCenter Server text box, enter the FQDN or IP address of the vCenter Server instance to which you are connecting.
    The vCenter Server FQDN or IP address must be reachable from all nodes in the vRealize Operations cluster.
  6. To add credentials for the vCenter Server instance, click the Add icon, and enter the required credentials. The vCenter credential must have Performance > Modify intervals permission enabled in the target vCenter to collect VM guest metrics.

    Optionally, you can use alternate user credentials for actions. Enter an Action User Name and Password. If you do not enter an action user name and password, the default user specified is considered for actions.

    Note: Credentials are stored in vRealize Operations and can be used for one or more instances of the vCenter Server.
    Note: To monitor application services and operating systems, it is recommended that you enter action credentials with guest operations privileges such as guest operation alias modification, guest operation alias query, guest operation modifications, guest operation program execution, guest operation queries.
  7. Determine which vRealize Operations collector or collector group is used to manage the cloud account. If you have only one cloud account, select Default collector group. If you have multiple collectors or collector groups in your environment, and you want to distribute the workload to optimize performance, select the collector or collector group to manage the adapter processes for this instance.
  8. (Optional) The collector for vRealize Operations can also be the cloud proxy. Select the cloud proxy you just deployed as the collector for this vCenter cloud account.
  9. The cloud account is configured to run actions on objects in the vCenter Server from vRealize Operations. If you do not want to run actions, deselect Enable for Operational Actions.
  10. Click Validate Connection to validate the connection with your vCenter Server instance.
  11. In the Review and Accept Certificate dialog box, review the certificate information.
    • If the certificate presented in the dialog box matches the certificate for your target vCenter Server, click OK.
    • If you do not recognize the certificate as valid, click Cancel. The test fails and the connection to vCenter Server is not completed. You must provide a valid vCenter Server URL or verify the certificate on the vCenter Server is valid before completing the adapter configuration.
  12. To modify the advanced options regarding collectors, object discovery, or change events, expand the Advanced Settings.
    For information about these advanced settings, see Cloud Account Information - vSphere Account Options.
  13. Click Add to save the configurations.
    The vCenter Server adapter instance gets saved and the vRealize Operations Registration to the vCenter Server dialog box appears.
  14. Use the vRealize Operations Registration dialog box to review the registration information.
    • If the vCenter Server already has a vRealize Operations instance registered to it, you can override the existing registrations with your instance of vRealize Operations. Click Yes to replace the existing registration with your vRealize Operations instance.
    • To proceed with the configuration without registering your vRealize Operations, click No.
    You can register your vRealize Operations instance after the cloud account is configured.


The cloud account is added to the list. vRealize Operations begins collecting metrics, properties, and events from the vCenter Server instance. Depending on the number of managed objects, the initial collection can take more than one collection cycle. A standard collection cycle begins every five minutes.

What to do next

You can enable vSAN Configuration for your cloud account. For more information, see Configure a vSAN Adapter Instance .

You can use the vCenter Server for service discovery, see Configure Service and Application Discovery.

You can register your vRealize Operations instance to a vCenter Server instance if you have not done it while configuring the vCenter Server cloud account.
  1. Click the cloud account you just created and click Manage Registrations.

    The Register vCenter Server dialog box appears.

  2. Click the Use collection credentials check box.
    • Click Unregister to remove any existing registrations.
    • Click Register to register your instance of vRealize Operations to the vCenter Server. If the vCenter Server already has a vRealize Operations registered to it, click Unregister to remove the existing registration and then click Register.