Consumption Analytics Documentation

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

Collecting Microsoft Azure tags and data

Table of contents
No headers

This method of collecting tags from Microsoft Azure was deprecated in Cloud Cruiser 4.2.10. To collect Microsoft Azure tags, use the Microsoft Azure Tags collection with the Microsoft Azure data source introduced in Cloud Cruiser 4.2.10. For more information, see Creating Microsoft Azure data sources and Creating Microsoft Azure collections.

Cloud Cruiser can collect Microsoft Azure tags along with your Azure data. To support this optional capability, Cloud Cruiser includes a Microsoft Azure Tags workbook template that includes the flows necessary to collect tags with your usage data.

To set up regular collection and publishing of Microsoft Azure data and tags

  1. Create a Microsoft Azure data source as described in Data sources. You will need the following information that is specific to your Microsoft Azure Enterprise Agreement account:
    • Endpoint: The URL for the Microsoft Azure Enterprise Portal,
    • Enrollment Number: Your Microsoft Enterprise Agreement enrollment ID. You can locate this at the top of the Microsoft Azure Enterprise Portal.
    • Access Key: A 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.

  2. Create a Microsoft Azure Tags data source as described in Data sources. You will need the following information:
    • Username: Your Microsoft Active Directory account user name. This account must have the Reader role for your Microsoft Azure Enterprise subscription. You can set that permission in the Azure portal (
    • Password: The password for your Microsoft Active Directory user account.
    • Client ID: The Client ID of your Active Directory application in the portal.
  3. Create a new workbook from the Microsoft Azure Tags template, as described in Creating workbooks. This template is similar to the standard Microsoft Azure template, but with two additional flows to collect and process Azure tags.
    For detailed information about the purpose about each flow in the templates see Flows in the Microsoft Azure templates. You can add, modify, and delete flows as needed to meet your collection needs.
  4. Create a mapping between the collection named apc_collection and the Microsoft Azure data source you created earlier in this procedure.
    1. In the Collections section of the Workbook tab, click List.
      A table appears, showing an error for the apc_collection row.
    2. Select the apc_collection line, and then click Edit.
    3. In the Datasource not found dialog box, click OK.
    4. In the Datasource field of the Edit Collection dialog box, select the data source you created earlier in this procedure.
    5. Click Finish to save the mapping.
  5. Create mappings between the tags collections (named apc_tags_group_collection and apc_tags_both_collection) and the Microsoft Azure Tags data source you created earlier in this procedure.
  6. Click Save to save the workbook.
  7. Test your workbook, as described in Testing collection and deleting data loads. When you are done editing your workbook be sure to delete any test data loads before you proceed to the next step.
  8. Schedule regular collection for this workbook, starting when the next day's complete data is available, as described in Scheduling jobs to run.
  9. Collect and publish past data for this workbook to ensure that Cloud Cruiser has all available prior data, as described in Run a workbook for a range of dates.
Last modified



This page has no classifications.

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