This post will go over the details on how to provision to Azure from vRA 7.2 by setting up Microsoft Azure and adding it as an endpointt to VMware vRealize Automation 7.2.
Part 2 will focus on setting up Fabric Groups, a reservation, blueprint and provisioning.
Obtaining Azure Subscription and Tenant ID
First step is to get our Azure Subscription ID, and Tenant ID. Open Powershell and run the Add-AzureAccount, after signing in you should be able to use the Get-AzureSubscription to get both your subscription ID and Tenant ID.
Set up authenticaiton for vRA
Then we need to set up a Client ID and Client secret. To do this we create an applicaiton in Azure AD.
Click on Azure AD, then on App Registrations
Enter a name for the app and enter anything in the URL it wont matter.
Then click Create, you then need to click on your app and take not oe the Applicaiton ID this will be used to fill the Client ID field in vRA.
From your app click All Settings, then Keys, and enter a name and expiry for the key, as soon as you click save you will ahve to copy the key to be used as our “client secret” in vRA.
Before our application can peform any actions in Azure we need to give it permissions to our subscription.
On subscriptions, click your subscription, click IAM, then click Add
Click on Select A Role and then choose one that is appropriate. I have used Owner but this is likely too great a role for a production subscription.
Click on Add users to the role and type in the name of the applicaiton and select it.
Choose Azure from the drop down menu
Enter a name and optional description for your Azure Subscription
Here you can see where all the fields get pasted from Azure
When done click Finish
And after a few moments you should see your new connection to Azure
I will add a future post to set up reservations, publish a blue print and finally provisioing to Azure from vRA 7.2.
See Part 2