Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.

Abiquo 4.6

Skip to end of metadata
Go to start of metadata

Azure ARM Features table

See Azure ARM features table

Configure Microsoft Azure ARM in Abiquo

Creating a public cloud region for Microsoft Azure ARM in Abiquo is the same as for a standard public cloud provider. However, before you create the public cloud region, you can configure the provider in Abiquo.

Filter templates

Azure has a very large number of templates and template publishers, which means it may take a considerable amount of time to perform template operations, such as listing templates or taking snapshots.

To improve performance, Abiquo uses a set of predefined publishers.

To configure the predefined publishers, set the following jclouds property in the abiquo.properties file on the Remote Services server:

jclouds.azurecompute.arm.publishersPublishers to use for filtering Azure ARM templates as a comma-separated list. Display only templates from these publishers to improve performance
Default: Canonical,RedHat,MicrosoftWindowsServer
jclouds property in Remote Services

To add publishers, users can start typing the name and select from the pull-down list. Users can remove publishers by clicking on the x to the left of the publisher name.

After you select the publishers, you can search for templates as in other public cloud providers.

Optionally configure VSM

As for other public cloud providers, you can optionally configure the VSM polling frequency.

See Abiquo Configuration Properties#vsm

Obtain Microsoft Azure ARM credentials and add to Abiquo

To work with Azure ARM in Abiquo, you will need to add the following Azure credentials to your Abiquo enterprise:

  • Subscription Id
  • Application Id
  • Tenant Id
  • Application password

To obtain these credentials:

  1. Create an Azure subscription
  2. Create an ARM application and keep the details of the application to add to Abiquo.

Create an ARM application using Azure Portal

The following procedure describes how to create an ARM application using the Azure Portal.

  1. Log in to the Azure portal and go to the Active Directory > App Registrations menu.

  2. Create a new application registration.

  3. Set the type to Web app / API and give it a name and a URL. The URL will not be used, so it could be any URL

  4. Note the Application ID for the created application because you will need it to configure the credentials in Abiquo.

  5. Configure the password for the application.

    Once saved, the Azure portal will show only once, the encoded password. That is the one that must be used in Abiquo, so make sure to write it down, as it won't be shown again.

  6. In the Active Directory > Properties menu option, copy the Tenant ID as you will need it to configure the credentials in Abiquo.


  7. Go to the Subscriptions menu, select the subscription you want to associate the created application with, and add a new permission for it as follows. Also copy the Subscription ID as you will need it to configure the credentials in Abiquo.

  8. In the form that appears, select the Contributor role, and in the selection text box type the name of the created application.

  9. Save the new permission.

Add the Azure ARM credentials in Abiquo

Before you begin, your administrator must configure Abiquo to use the appropriate Azure ARM regions. 

To connect Abiquo to your Azure ARM account, add the Azure ARM credentials obtained in the above step to Abiquo.

To do so, edit the Enterprise credentials and enter the credentials for the Azure ARM provider in the following format:

  • Identity: Enter the Subscription Id, Application Id and Tenant Id, as a single string, separated by a '#'. For example: 566058dd-80bc-4ccc-8d6e-e9ac00c4b4a1#8927a710-4f4d-4d11-811c-94c36e9b2c3f#fbb96b71-f92c-4f78-acf7-cd88bdee36b1
  • Credential: Enter the password for the Application.

Or for CSP customers, enter the Identity as follows:

  • Identityuser#client-id#csp-authenticator-uri

And the appropriate credential.

Azure Pricing credentials

For Azure, the pricing credentials for standard accounts will differ from the credentials to manage virtual resources. The credentials will have the following formats, depending on the account type:

  • Standard account: subscription-id#app-id#tenant-id#offer-durable-id
  • CSPuser#client-id#csp-authenticator-uri

You can obtain the Offer-Durable-ID from the Azure portal under Administer. See Display Azure billing data  


How Abiquo works with Microsoft Azure ARM

Abiquo creates virtual datacenters and virtual networks in Azure ARM.

Diagram of correspondence between Abiquo entities and Azure ARM entities

In Azure ARM, users will be able to allocate and assign public IPs as in AWS.

Diagram of how Abiquo creates a VDC in Azure ARM