Azure ARM features table

Abiquo offers these features in the public cloud integration with Microsoft Azure RM (ARM) Compute.

The platform supports basic SKUs for load balancer and public IP resources. It does not support standard SKU resources.

Azure RM requires separate credentials for regions in China.

Azure does not let you change the Name and ResourceGroup of a VM. It uses the Name and the ResourceGroup to identify the VM. For Azure, the platform also uses the Name to identify the VM. The VM Name in Azure is always in the ABQ_uuid format.

When the user creates a VM in the platform, by default the friendly name of the VM is the name of the VM template. The user can then edit this label to identify their VM. In Azure, the friendly name is stored as a VM tag. You can easily display these tags in the Azure portal, simply follow the instructions in the Azure documentation.

Azure ARM Feature	Support	Comments
Configure and remove VMs		When you deploy, you’ll select the hardware profile. To search for templates in Azure ARM, the format for a template ID is {region}/{provider}/{name}/{version}. The Name of the VM in Azure is in the format ABQ_uuid and you cannot change it.
Reconfigure VMs		You can edit deployed VMs to: attach and detach firewalls and load balancers, change hardware profiles, and reconfigure NICs The platform may require you to power off a VM to make changes to Multi-NIC configurations that were created in the Azure portal You cannot change the order of NICs on Azure after you deploy a VM
Power on VM
Power off VM
Reset VM
Pause and resume VM
Storage		Azure does not support premium storage for some hardware profiles. The platform does not enable you to configure VMs with premium storage.
Take a VM snapshot		To create a VM snapshot (instance) you must first log in to the VM and generalize it using Sysprep. See https://docs.microsoft.com/en-us/azure/virtual-machines/windows/capture-image-resource. Then you should power it off and create the snapshot in the usual way. Note: after you generalize the VM, you cannot power it on again.
Remote access		Depending on template type, for example: RedHat: template user/password Ubuntu: Using your SSH key registered in Abiquo, or template user/password
Create and delete networks		Each Abiquo VDC will map to an Azure ARM virtual network An Abiquo private network will map to a subnet in the VDC network Users can allocate and assign public IPs (as in AWS) The platform will onboard and synchronize dynamic public IPs The platform supports basic SKU public IPs. It does not support standard SKU public IPs
Create and delete VPNs		Site-to-site VPNs, for example, from private cloud (NSX) to Azure, and from Azure to Azure
Create and delete VDCs		Abiquo will not be locked to a single resource group and will be able to manage and onboard existing resources regardless of the resource group they belong to Each Abiquo VDC will map to an Azure ARM virtual network
Create and manage firewall policies		The platform supports one firewall per VM When onboarding VMs, if the VM and firewall are not in the same VDC, the platform will not assign the firewall to the VM
Use Chef		Enterprise Chef or your own server
Use Chef attributes
VM bootstrap scripts
VM variables		Stored as node metadata.
Load balancing		See Azure load balancers table
Import and synchronize VMs		To onboard VMs, the enterprise must have credentials registered.
VM monitoring and metrics		Abiquo supports monitoring with Azure built-in metrics You can also use the Abiquo monitoring server and Abiquo collectd plugin, which can be installed using the Abiquo Chef cookbook. See Use collectd plugin for custom metrics
Dashboard billing widgets		The Hybrid tab of the Home dashboard view can display public cloud billing information, including the latest bills and estimated bill. See Hybrid and for configuration instructions see Display cloud provider billing data.