AzureRM Configurations


AzureRM Access Endpoints to VMs

CloudCenter allows you to access/restrict AzureRM deployments via the Internet. Every tier has a value to Add Access End Point:

  • Yes: The SSH port and any other port that is opened as part of the application profile has Internet access.
  • No: All ports are restricted and will not have Internet access.

AzureRM Resource Preparation

Once you Configure the CCO (Required) for AzureRM, be sure to configure the following resources in preparation to launch a job:

  • Resource Group

  • Storage Account

  • Virtual Network

  • Additional Resource Groups

To configure the AzureRM resources in preparation to launch a job, follow this procedure.

Be aware that these screen captures may change based on the Azure portal changes. They are provided in this section as a point of reference.

  1. Using a valid Windows Azure Resource Manager account, access the new Microsoft Azure Portal.

    You may need to click Microsoft Azure dropdown at the top left corner to toggle between these interfaces.

    In the new Microsoft Azure Portal, search for each of the following items and add the corresponding information to each portal. 

Search forClick ...Configure ...
Resource groupResource group to access this portal

Select and add the same region as your CCO to the Resource group location.

Additional resource groups

You can create additional resource groups to place different VM types. At deployment time, you can select the resource group to deploy the VM.

Storage accountStorage Account to access this portal

Configure the following fields:

  1. Resource group – select the group created in the first row.
  2. Location – provide your CCO location.
  3. Type – create two storage accounts:


    The reason to create two storage accounts is that, some instance types (for example, Standard_DS1, Standard_GS1) can use the premium storage account to enhance performance and use standard storage account. The other instance type can use the standard storage account only.

    1. One with Premium Locally Re...  (if premium is not available for some regions, one account is enough
    2. One with Standard-RAGS (the default).

Virtual networkVirtual Network to access this portal

Configure the following fields:

  1. Resource group – select the group created in the first row.
  2. Location – provide your CCO location.

AzureRM Diagnostics

CloudCenter users can view diagnostics provided by Azure Resource Manager from multiple places in the Azure console.

  1. Access the Azure console from the target VM and open the Monitoring page.

    • If you see a graph displayed in the Monitoring page, then diagnostics is enabled.

    • If you do not see any data displayed in the Monitoring page, then diagnostics is disabled.

  2. Go to the resource, click the Settings command, and select Diagnostics. Verify the following settings:

    1. The status is On

    2. The Basic Metric and Boot Diagnostics are checked.

  3. Navigate to the Boot diagnostics tab (at the same menu level as Diagnostics, but on the top). Verify that boot diagnostics are available.

  4. Enable AzureRM diagnostics in CloudCenter as this feature is disabled by default. 

    1. Deploy the application that uses the AzureRM diagnostics feature.

    2. Scroll down to the Advanced section for this deployment version.

    3. Click the Diagnostics dropdown list and select the applicable file for this deployment.

      The metrics and logs are stored in the related storage account.

      Be aware that this change in settings may incur an extra billing amount.

Microsoft has multiple settings to determine how metrics are collected (time interval) and to specify the metrics to be collected. CloudCenter uses the default Microsoft settings. Users can specify their own settings by providing the corresponding XML file.

  • Linux: /usr/local/osmosix/etc/azure/LinuxDiagnosticsSetting.xml

  • Windows: /usr/local/osmosix/etc/azure/WindowsDiagnosticsSetting.xml

If the file exists in this location, CloudCenter use the settings identified in this file to collect AzureRM metrics.

These settings apply to the entire CCO server and the file is loaded when the CCO initiates. If users change the file and want the file and want the new changes to take effect, you must restart the CCO.

Availability Zones and Sets

  • API
    • Description: While launching a job from the CloudCenter platform, you have the option to create an Availability Set at the tier level. All VMs within a cluster are placed in the same subnet. So all VMs inside the same Availability Set are placed in the same subnet. If you do not enable the Availability Set, an availability set is NOT created. To ensure high availability, the VM(s) placement in fault/update domains are not guaranteed to be in different domains. See Availability Sets and Zones or Submit Job (v2) for additional context.
    • Type: Boolean
      • true = The VM is launched into the same Availability Set.
      • false = The Availability Set is not created.
    • Example:

      "cloudProperties": [
                  "name": "provisionInAvailabilitySet",
                  "value": "true"
Terms & Conditions Privacy Statement Cookies Trademarks