Unsupported content


This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Azure provider

BMC Cloud Lifecycle Management 4.6.03 and earlier versions integrate with the Azure Service Management (ASM) Portal, commonly known as the Azure Classic Portal to deploy Azure cloud applications as a service. With Microsoft Azure virtual machines (VMs), enterprise customers can deploy their own customized Microsoft Windows Server or Linux images into a multizone, commercially backed Service Level Agreement (SLA) production environment in minutes or get started with a preconfigured image from the Microsoft image gallery. Finally, with Microsoft Azure and virtual network technology, the cloud is a seamless extension of your data center, taking full advantage of Microsoft System Center, Active Directory, and Visual Studio.

The topics in this section provide information and instructions for installing, setting up, preparing, and initiating an Azure service offering instance:

With an Azure Provider integration with BMC Cloud Lifecycle Management, you can perform the following actions:

  • Provision VMs:Onboard existing Azure VMs using the QuickStart utility or REST API.
    • Provision VMs from an image gallery of prepopulated templates available from Microsoft Azure.
    • Provision VMs from custom-built virtual hard disk (VHD) images.
    • Attach or detach and use data disks for storage (each disk can be up to 1 TB in size).
  • Perform remote actions:
    • Log in remotely via Remote Desktop Procedure (RDP), PowerShell, Secure Socket Shell (SSH), or terminal server, to customize VMs.
    • Allocate and view tenant and user quota usage.
    • Start, stop, or shutdown VMs.
    • Modify the CPU count or memory size of provisioned VMs.
    • Add a server to an existing service.
    • Request an Azure cloud service on behalf of another user.
    • Share and transfer ownership of an existing Azure cloud service.
    • Install software on provisioned VMs (both pre- and post-provisioning) using BMC Server Automation.
    • Add local OS users to a provisioned VM.
    • Add a VM to an existing or new availability set created during provisioning.
  • Perform networking actions:
    • Onboard an Azure network with subnets.
    • Place VMs in specific networks or subnets.
    • Open or close VM endpoints by using network paths.
    • Add servers to load balancer pool.
    • Enable or disable external IP Address Management (IPAM) solution. 
  • Monitor server and tenant details of the Azure Provider by using the Value Dashboard. See Monitoring server and tenant usage for details.
  • Request and manage Azure services and servers using both legacy and new My Cloud Services Console.  

High-level tasks for setting up an Azure Provider

The cloud administrator is an IT professional who is responsible for the full life cycle of the cloud environment, including initial planning, deployment and configuration, continued administration, operation, and maintenance. As a cloud administrator, you can leverage Microsoft Azure in the IaaS provider capability for your development and testing teams. As a Microsoft Software Developer Network (MSDN) subscriber and an enterprise customer, you can have access to an image gallery that contains multiple versions of the Windows server operating system and additional server software, such as SQL Server, SharePoint Server, and BizTalk Server, enabling you to quickly develop and test components at discounted rates. You can use your own MSDN server software licenses and bits to create VMs tailored to your specific needs.

The following table lists the tasks of a cloud administrator, associated with the stages at which the tasks are required:


Install Azure Provider


Upgrade the Azure Provider

You must install or upgrade the Azure Provider first before using it.

Note: Before installing or upgrading an Azure Provider ensure that the prerequisites are met. See Prerequisites for installing the Azure Provider for details.

Enabling the Azure provider

Typically you perform the activities of the setup phase of your Azure Provider only once. These activities include configuring the Azure Provider and setting up the Azure account credentials.

Configuring resources for Azure services

After you have installed and enabled the Azure provided, you must onboard and configure the Azure Provider resources to provision an Azure service:

Create the service offering for Azure

In this final phase, you prepare and initiate the service offering request.

Administering the Azure provider

Once the provider is up and running, you can perform the following administrative tasks at any time:

Version 4.5.00 and the Azure Provider

This section provides the information about BMC Cloud Lifecycle Management 4.5.00 and the Azure Provider.

Release contents

This release contains the Azure Provider installer and the following enhancements:

Onboard existing Azure VMs

You can bring existing Microsoft Azure Virtual Machines into BMC Cloud Lifecycle Management by onboarding them using any of the following procedures:

Monitor server and tenant details of the Azure Provider

You can now monitor server and tenant details of the Azure Provider by using the Value Dashboard. See Monitoring server and tenant usage for details.

Using external IP Address Management (IPAM) solution for an Azure Provider

Edit a Virtual Network to enable or disable external IPAM for the Azure Provider

Note: Ensure that you have an external IPAM solution configured with your BMC Cloud Lifecycle Management application. See To use an external IPAM for a Virtual Network for details.

Request and manage Azure services and servers using the My Cloud Services Console or the legacy console.

You can now request and manage Azure services and servers using both legacy and new My Cloud Services Console. For detailed procedures see:

Where to go from here

Installing the Azure Provider

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.