Skip to Content
Information
Unsupported content 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.

Mapping tenant and user quota for the Azure Provider

Microsoft Azure allocates resources to you based on your Microsoft Azure subscription type. For each Microsoft Azure subscription, you can create up to 200 co-administrator accounts. See Manage Accounts, Subscriptions, and Administrative Roles, for details. You must add the account details in the Azure Provider. See Managing-multiple-user-accounts-for-an-Azure-Provider for details about adding an Azure user account.

In BMC Cloud Lifecycle Management, you must map your Microsoft Azure subscriptions or Azure administrative accounts as tenants, and define the resource limits as tenant quota.

The following topics describe how to manage the tenant quota for the Azure Provider:

Before you begin

You must define the tenant in BMC Cloud Lifecycle Management. See Creating-and-importing-tenants for details.

To set up the tenant and user quota

In BMC Cloud Lifecycle Management, you can determine the ability to allocate and monitor resources to the tenants or users. By default, unlimited quota is allocated to the tenants and maximum quota for the users.

  1. To allocate resources to the tenants by using the BMC Cloud Lifecycle Management - Tenant Management workspace, see Setting-tenant-quota for details.
  2. To allocate resources to the users by using the BMC Cloud Lifecycle Management - Tenant Management workspace, see Setting-user-quota for details.

To view the tenant and user quota

After you have allocated the resources for your tenant, you can view the tenant and user quota details.

  • Click the Tenants tab and select the tenant to view the resource consumption by the tenant, as shown in the figure below:
    TenDet.png
  • Click the Users tab and select the user to view the resource consumption by the tenant user, as shown in the figure below:
    TenUsrQutDet.png
Warning

Notes

  • An upgraded SOI is not covered under Quota calculations, as Quota management is supported only for the servers provisioned by Azure Provider 1.1.00 and above.
  • You may expect incorrect quota calculations for servers provisioned in an upgraded environment. Cloud Admin must ensure that the quota allocation is done properly. 

  • You may expect incorrect quota calculations after performing Add Server TRO operation on an onboarded VM, if the PDC entry specified in the service blueprint mismatches with the OS image of the onboarded VM or is not available in the Azure cloud.

Where to go from here

Managing-Logical-Data-Centers-for-the-Azure-Provider

Managing-Virtual-Networks-for-the-Azure-Provider

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Cloud Lifecycle Management 4.6