Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 4 > Collecting, transforming, and publishing > Microsoft Azure

Microsoft Azure

Cloud Cruiser's Microsoft Azure solution retrieves usage and cost data from Azure, Microsoft's public cloud platform, through Microsoft Azure APIs.

Cloud Cruiser versions 4.1.0 to 4.1.2 included two collectors for Microsoft Azure, one named Microsoft Azure that collected by logging into the Microsoft Azure Enterprise Portal as a user, and a newer collector named Microsoft Azure (API) that collected via the Azure API. In November 2014 Microsoft made changes to the Microsoft Azure Enterprise Portal that prevented the older collector from working. If you are using a version of Cloud Cruiser between 4.1.0 and 4.1.2, use the collector named Microsoft Azure (API).

Cloud Cruiser version 4.1.3 removed the collector that logged into the Microsoft Azure Enterprise Portal as a user. The collector that used the Azure API to connect to your Microsoft Azure Enterprise Account was renamed as the Microsoft Azure collector. If you are using a version of Cloud Cruiser between versions 4.1.3 and 4.2.9, use the collector named Microsoft Azure.

Cloud Cruiser version 4.2.10 renamed the collector that connects to your Enterprise Account as the Microsoft Azure EA Billing collector, and added several new Azure collectors. If you are using Cloud Cruiser version 4.2.10, use the new Microsoft Azure collectors, as described in Creating Microsoft Azure collections.

For more detailed information about collecting Microsoft Azure data, see the following topics:

CloudSmart-Now prerequisites

If you want to use the CloudSmart-Now solution for Microsoft Azure, you must complete the following tasks:

Before you begin

Cloud Cruiser supports only Azure accounts linked to an Enterprise Agreement, and which use a Microsoft Account (not an Organizational Account) to connect to Azure. Before you begin you must already have a Microsoft Azure Enterprise Agreement account set up.

Configuring Cloud Cruiser to collect, transform, and publish Azure data

To collect, transform, and publish Azure data

  1. Modify the Microsoft Azure data source named Azure1 to work with your Microsoft Azure account:
    1. Navigate to Data > Setup > Sources.
    2. Click the Azure1 data source.
    3. In the Endpoint field, enter the URL for the Microsoft Azure Enterprise Portal,
    4. In the Enrollment Number field, enter your Microsoft Enterprise Agreement enrollment ID. You can locate this at the top of the Microsoft Azure Enterprise Portal.
    5. In the Access Key field, enter the string of characters (approximately 700 in number) used to authenticate access to the Microsoft Azure API. To obtain this key, on the Reports area of the Microsoft Azure Enterprise Portal go to Download Usage > API Access Key and see the value in the Primary Key field. Because the string is so long, you might find it easiest to copy and paste the string from the Microsoft Azure Enterprise Portal to the Cloud Cruiser Access Key field. If you do this, note that double-clicking the string does not select all of the characters. To be sure you have selected all of the characters place your cursor in the Primary Key field and then press Ctrl-A.

      Because keys expire (every 6 months by default), you will need to update your data source periodically. If data collection fails with an "HTTP/1.1 401 Unauthorized" error when connecting to the endpoint, investigate whether you need to generate a new API key in the Microsoft Azure Enterprise Portal.


    6. Click Save.
  2. Create an Azure workbook:
    1. Navigate to Data > Workbooks.
    2. In the list of workbooks, right-click and select Add New Workbook.
    3. Enter a Workbook Name and (optionally) a Workbook Description.
    4. Check the Create Workbook from Template box, and then select the Microsoft Azure template.
    5. Click OK.
      A new workbook opens, already containing the necessary collections and workflow.
    6. Click Save to save the workbook.
  3. Test your workbook:
    1. In the Workbook ribbon, click Run.
      The Run Workbook dialog box opens.
    2. In the Select Date field, enter the current date.
    3. Select all of the collections and flows, and then click Run.
    4. After the run finishes, click View Log at the bottom left of the dialog box to open the Monitoring window, where you can view the log for any specific collection or flow.
    5. If your workbook test run did not complete successfully, or if it did not provide the data you need, edit the workbook and then run another test.
  4. When you are done editing your workbook delete any test data loads:
    1. Navigate to Data > Processing > Published Loads.
    2. Select one or more entry rows and click Delete Load(s) at the top of the page.
    3. Click Yes to confirm the deletion.
  5. When you are ready to put your workbook into production, start the next procedure, Scheduling regular collection.

Scheduling regular collection

After configuring Cloud Cruiser to collect, transform, and publish your Microsoft Azure data, create a schedule that defines when and how often to run those processes.

To schedule regular collection

  1. Go to Data > Processing > Scheduling.
  2. In the Schedules section, click New.
    The New Schedule dialog box appears.
  3. In the Job Type field, select Workbook.
  4. In the Name field, enter Azure.
  5. (Optional) In the Description field, enter a description for this schedule, such as Daily schedule for Microsoft Azure data.
  6. Set Enabled to Yes so that the schedule will run.
  7. In the Frequency section, set the Start Date to the first date that you want the schedule to run, usually today's date.
  8. In the Recurrence field, select Daily.
  9. In the Start Time field enter the time of day the schedule will run, 02:15.
  10. In the Workbook field, select Azure.
  11. In the Select Date field, select Current Day Minus 2 Days.
  12. In the Workbook Components section, select all of the components and flows.
  13. Click OK.
    The new schedule is added to the list.
Last modified



This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP