7.3

4 Enter the location of the registered IPAM endpoint in the Address text box using the provider-specific
URL format, for example https:/host_name/name.
For example, you might create several IPAM endpoints, such as https://nsx62-scale-infoblox
and https://nsx62-scale-infoblox2, when you registered the IPAM endpoint type in
vRealize Orchestrator. Enter a primary registered endpoint type. To also specify one or more
secondary IPAM endpoints, you can use custom properties to emulate the extensible attributes that
are specific to the IPAM solution provider.
5 Enter the user name and password required to access the IPAM solution provider account.
The IPAM solution provider account credentials are required to create, configure, and edit the
endpoint when working in vRealize Automation. vRealize Automation uses the IPAM endpoint
credentials to communicate with the specified endpoint type, for example Infoblox, to allocate IP
addresses and perform other operations. This behavior is similar to how vRealize Automation uses
vSphere endpoint credentials.
6 (Optional) Click Properties and add endpoint properties that are meaningful to the specific IPAM
solution provider.
Each IPAM solution provider, for example Infoblox and Bluecat, use unique extensible attributes that
you can emulate by using vRealize Automation custom properties. For example, Infoblox uses
extensible attributes to differentiate primary and secondary endpoints.
7 Click OK.
What to do next
Add the compute resources from your endpoint to a fabric group. See Create a Fabric Group.
Create a Microsoft Azure Endpoint
You can create a Microsoft Azure endpoint to facilitate a credentialed connection between
vRealize Automation and an Azure deployment.
An endpoint establishes a connection to a resource, in this case an Azure instance, that you can use to
create virtual machine blueprints. You must have an Azure endpoint to use as the basis of blueprints for
provisioning Azure virtual machines. If you use multiple Azure subscriptions, you need endpoints for each
subscription ID.
As an alternative, you can create an Azure connection directly from vRealize Orchestrator using the Add
an Azure Connection command located under Library > Azure > Configuration in the
vRealize Orchestrator workflow tree. For most scenarios, creating a connection through the endpoint
configuration as described herein is the preferred option.
Azure endpoints are supported by vRealize Orchestrator and XaaS functionality. You can create, delete,
or edit an Azure endpoint. Note that if you make any changes to an existing endpoint and do not execute
any updates on the Azure portal through the updated connection for several hours, then you must restart
the vRealize Orchestrator service using the service vco-service restart command. Failure to
restart the service may result in errors.
Configuring vRealize Automation
VMware, Inc. 209