Several considerations exist for vCloud Air and vCloud Director vApps in vRealize Automation.
As you prepare to provision vApps in vRealize Automation, be mindful of the following considerations.
If you import a vApp with multiple component virtual machines into vRealize Automation but the import process fails for one or more component machines, you cannot import any of the virtual machines that failed the import process.
When you configure vRealize Automation for vCloud Director, if you have users who are configured in the vCloud Director identity store as LDAP users, configure these users for LDAP in the vRealize Automation identity store so that the same set of users are available in both products.
The following actions are not supported in vRealize Automation:
Creating vApp templates
Defining vApp (vCloud) and vApp Component (vCloud) blueprints without specifying a vApp template
Moving vApps between virtual datacenters
Moving virtual machines between reservations
Adding or removing components from a vApp
Creating or using vApp snapshots
Using a static IP address