So you are a vROps user or a new adopter? Maybe you are just curious? In any case, this article will help you to understand the requirements to configure your AZURE management pack in vROps 8.2.
This will provide you a consolidated view of your On-Prem operations and your Azure public cloud.
This will provide visibility on the topology and dependencies between your AZURE components up-to-date in a couple of clicks.
But in addition to this, you can troubleshoot as well performance issues the same way you would do it on your VMware environment.
Before you can see these data, you need to setup the vROps management pack for AZURE. To do so, follow the steps described below.
1 – SETUP THE ACCESS IN YOUR AZURE TENANT
First, you have to provide vROps an access to your AZURE tenant.
Connect to your Azure portal and create the Azure AD application service principal to allow the resources access.
the official Microsoft documentation is here.
But as anyone knows, documentation with screenshots is even better to understand so here is the step by step procedure I used to create the application account.
1.1 – Register an application with Azure AD and create a service principal
Open your Azure portal and search for the Azure Active Directory service.
Use the search engine if you can’t find it in the menu.
In the Azure Active Directory Directory, locate the option « App Registration » and click on it.
Click on « New Registration »
Provide a name that makes it easy to identify the purpose of this account. The name will not be the user name, this is just an object label.
What you will have to provide in vROps will be an Application (client) ID and a Directory (tenant) ID. (next step)
Then click on register.
Here is an important step! Identify the info from the green area and save this in a notepad for later. When this is done, locate the « Certificates & secrets » option and click on it.
We are now generating the Authentication key for the application. In the « Client Secrets » section, click on the « + New Client secret »
Define the duration of this secret key. I’m a bit lazy as this is a lab and I will pick a never expire option ;o)
Then click on « Add »
Make sure you copy the key in your notepad with the previous info you saved for later as this key will be hidden. There is no way to retrieve it later so keep it safe.
Ultimately if you lose the key you will have to generate a new one following the previous step. As you can see below the key is hidden after.
we are done with the creation of the account, now we need to assign this account a role in the Azure subscription.
1.2 – Assign a role to the application
Locate the subscription service in Azure portal.
Identify the subscription for which you want to provide access. In a large environment, you may have a longer list. Make sure you know what you want to monitor in vROps. If you have a few subscriptions to include in vRops scope, you will have to perform the next steps for each subscription.
Take the « arrow 1 » data and save it in your notepad. You will require the « Subscription ID » later in the vROps management pack.
Then click on your subscription name (Arrow 2)
In your subscription locate the « Access control (IAM) and click on it.
Click « Add » to create a new role.
You will have to select the role and search the account we created in the previous section (1.1)
Select the Role « Contributor »
Assign access to « User, group, or service principal »
Select –> Type the account you created and click on it. Make sure it appears in the selected members’ section at the bottom.
Then click on « Save »
We are now ready to setup the vROps management pack.
2- vROps Management Pack Setup
The official documentation is here.
My underground documentation is bellow ^^
Connect to your vROps platform.
Go to the administration section.
In the « Solutions » section click on the « Cloud accounts » option.
Then click on the « Add Account » button.
As we are interested in this post on AZURE, click on the Microsoft Azure account type.
Now, this is the time to take your precious notepad notes and fill the fields!
When you click on the « + » to create the credential these are the data you will require (all in the notepad) :
The credential name is just a vROps internal Label.
Provide the Application ID and the client secret you saved in section 1.1 and click « OK »
Provide the Subscription ID and Directory ID generated in 1.1
you can filter the region to reduce the scope if you know your subscription is only attached to one, which is the case for mine.
Before clicking on the save button just check that the connectivity is working well between vROps and https://portal.azure.com
If your account is working as expected you will get the following result. Then and only then you can click on Save. Otherwise, troubleshooting is required until you get the success message.
After a few minutes (up to 15 minutes sometimes) you will get the status « OK ». You will require a few collection cycles before the dashboards and environments get populated so be patient.
Then you can go into the « Dashboard » section and you will find new out of the box dashboards!
I hope this post was helping you! Have fun.