As a cloud administrator, you can make vRealize Automation Cloud Assembly blueprints available in the vRealize Automation Service Broker catalog by adding a vRealize Automation Cloud Assembly content source and sharing the blueprints. The blueprints are the specifications for services or applications that you can deploy to your cloud providers.

After you import the blueprints, you share them with project members so that they can deploy the blueprints. At the request time, the blueprint is deployed to cloud zone account region or datastore that supports the blueprint requirements.
Prerequisites
- Verify that the blueprints that you are importing are deployable and released in vRealize Automation Cloud Assembly before you import them. See How to save different versions of a blueprint.
Procedure
Results
The released blueprints are imported into vRealize Automation Service Broker, shared in the catalog, and deployable.
What to do next
- If the deployment fails, click the deployment name and begin troubleshooting. See What can I do if a vRealize Automation Service Broker deployment fails. If you are a vRealize Automation Cloud Assembly cloud administrator, you can also do more extensive troubleshooting in vRealize Automation Cloud Assembly What can I do if a Cloud Assembly deployment fails.
- If you want to control how long a deployment can exist, create a lease. See Setting up vRealize Automation Service Broker policies.
- To provide more or fewer user inputs at request time, you can create a custom form. See Customize a vRealize Automation Service Broker icon and request form.