Azure has been available since vRA 7.2 release with OOTB support for building, delivering and lifecycle management of Azure-based workloads. Some features to take note of:
- Adds native Azure support for hybrid cloud and provisioning use cases
- First Endpoint to be built on top of extensibility platform (XaaS vs .NET)
- Incorporate key vRA functionality, such as approvals, extensibility, and CBP
- Azure services built in CBP, provides config granularity per component
- Supports Azure Networking (subnets, load balancers)
- OTB Day2 lifecycle operations include start, stop, restart, delete
- Leverages new Azure vRO plugin (included OOTB)
As mentioned in bullet point 2 the Azure endpoint is not configured from the traditional Infrastructure tab location because it is not managed by the IaaS engine of vRA but presented via vRO and XaaS.
So how do get this all of this to install and configured? Let’s start with vRA.
Azure installation steps for vRA 7.2 with external vRO
When using an external vRealize Orchestrator server with vRealize Automation, Microsoft Azure integration is not available so in order to make that work we need to export the Azure plug-in from the internal vRO, that resides on your vRA server, and then import the plugin to the external vRO server. It sound complicate but not that bad.
- Log in to the vRO Control Center for the internal vRealize Orchestrator on your vRealize Automation virtual appliance.
- Under Plug-Ins -> click Manage Plug-Ins.
- Find the Azure plug-in
- Right-click Download plug-in in DAR file.
- Save the file to your desktop.
- Log in to the vRO Control Center for your external vRealize Orchestrator.
- Follow same steps as in step 1, except point http address to external vRO server.
- Under Plug-Ins -> click Manage Plug-Ins.
- Under Install plug-in -> click Browse
- Point to DAR file downloaded from internal vRO
- Click Install.
- If prompted to confirm
- Click Install again.
- In the Control Center under Startup-Options, click Restart to finish installing the new plugin.
- Reboot all your vRealize Automation virtual appliances at the same time.
Microsoft Azure integration functionality should be restored.
Verify Azure plugin: (Remember this will not be under your regular Infrastructure endpoint)
- Login to vRA.
- Administration -> vRO configuration -> Endpoints
- Select New
- Open Plug-in drop down box
- Verify that you can see “Azure”

- Good to go!
If the integration does not function properly after the reboot, verify that the Azure package, com.vmware.vra.endpoint.azure, is present in the external vRO. If the Azure package is not present, complete these steps.
- Log in to your internal vRO client on your vRA virtual appliance.
- Export the Azure package, com.vmware.vra.endpoint.azure. For instructions, see, Export a Package.
- Log in to the vRO client for your external vRO.
- Import the Azure package, com.vmware.vra.endpoint.azure, to your external vRO. For instructions, see Import a Package.
Create Azure Endpoint:
- Login to vRA.
- Administration -> vRO configuration -> Endpoints
- Click New
- Select Azure from Plug-in drop down box
- Click Next
- Give the Endpoint a name
- Click Next
- If you get an error “Service Workflow cannot be found”, then make sure the package is present with steps provide above.
- Fill in the detail settings
- You need to Azure Subscription ID, Tenant ID, Client ID as well as client secret.
- This information is available under https://account.windowsazure.com/Subscriptions
Before continuing with vRA configuration you have to prep your Azure environment, which is out of scope for this article, and make sure have the following information available:
- Subscription ID
- Tenant ID
- Resource Group name
- Storage account name
- Location
- Virtual Network name
- Client application ID
- Client application secret key
- Virtual Machine image URN
Create Azure resource reservation:
- Administration -> Users and Groups -< Business Groups
- Create Business Group if required or use existing
- Infrastructure -> Reservations -> Reservations
- Create Reservation
- Provide Name
- Select Business Group
- Optionally set Reservation Policy
- Set priority
- Very check on Enabled
- Click Next
- Enter Subscription ID
- Set Location
- Click New on Resource Group
- Enter Resource group name
- Click New on Storage Accounts
- Enter Storage account name
- Click Next
- Click New on Networks
- Enter Network name
- If required enter the name for the Load Balancers and Security Groups as well.
- Set alerts
- Finish
Create Azure Blueprint:
- Design -> BluePrint
- Create new
- Under machine types categories select Azure Machine
- Drag it to design canvas
- Select Azure Machine
- Set ID
- Under Build information tab
- Set Location

- Set Naming Prefix
- This can be based on Business group default or Custom
- Windows computer name cannot be more than 15 characters long, be entirely numeric, or contain the following characters: ` ~ ! @ # $ % ^ & * ( ) = + _ [ ] { } \ | ; : . ‘ ” , < > / ?
- Set Image type
- Enter Virtual Machine image name
- Set Authentication with username and password
- Cannot use the username “admin”, yes I tried that first.
- Password requires a minimum of 12 characters
- Set Instance size
- Set series
- Set size

- Under Machine resources tab
- Set Resources group by either creating a new or use an existing.
- Enter existing resource group name
- Set availability set

- Under Storage tab
- Set storage account name, if nothing is set the storage account will be picked from reservation.

- Under network tab
- Enter load balancer name
- Set IP address type
- I have Dynamic selected
- Set networking configuration
- I have specify Azure network selected
- Optionally, can fill out rest of network names

In part 2 I will discuss adding Microsoft Azure to vRealize Business for Cloud