Home > CCS > Configuring Cloud Cruiser > 01 Collections > Microsoft Azure

Microsoft Azure

Cloud Cruiser's Microsoft Azure collection retrieves usage, cost, and performance data from Azure, Microsoft's public cloud platform.

Cloud Cruiser also collects your Azure tags, and for reporting purposes displays them in the Other group of the All Fields field package. The Azure collection automatically collects resource-level tags for resources deployed using the Azure Resource Manager (ARM) deployment model. If you add Azure subscriptions to your collection, Cloud Cruiser can also collect group-level tags. For more information about how Cloud Cruiser maps source provider data to Cloud Cruiser normalized fields, see Field mapping.

Cloud Cruiser collects Azure data through the following APIs:

  • Azure EA Billing: Usage charges, and resource tags
  • Azure Resource: Tags for resource groups
  • Azure Diagnostics: Performance metrics

Are you provisioning Cloud Cruiser from the Azure Marketplace? If so, check out this video or this written tutorial to help you navigate the choices on the Marketplace and log in to Cloud Cruiser for the first time.

Video example

The following video shows you how to configure collection from a Microsoft Azure cloud, so you can see your Azure cost and usage data in Cloud Cruiser charts and reports:

Before you begin

Before creating an Azure collection, complete the following tasks

  • Assemble your Azure credentials, as described in Credential information.
  • If you want to collect subscription information, ensure that your Azure account is assigned the right administrator roles for the subscriptions associated with your Enterprise account. For more information, see Account roles for your subscriptions.
  • If you want to collect performance data, you must ensure that one or more Azure VMs have diagnostics enabled, as described in Enabling diagnostics for Azure VMs. Cloud Cruiser retrieves performance data only for VMs with diagnostics enabled.

Credential information

Before creating an Azure collection, assemble the following credential information, which you will need when creating an Azure collection in Cloud Cruiser:

  • Enrollment Number: Your Microsoft Enterprise Agreement enrollment ID. You can locate this at the top of the Microsoft Azure Enterprise Portal (EA portal).
  • Access Key: A string of characters (approximately 700 in number) used to authenticate access to the Microsoft Azure API. To obtain this key, in the EA portal go to Reports > 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 EA portal to the Cloud Cruiser Access Key field. If you do this, use the Expand Key button in the EA portal to make sure you copy the entire key value.

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

You must be an administrator of your Azure enrollment to log in to the Microsoft Azure Enterprise Portal. If you are not an administrator, ask your Azure enrollment administrator to grant you administrator rights (on the Manage page of the Azure Enterprise Portal).

Understanding connection to your subscriptions

To supplement the usage and billing data Cloud Cruiser collects using your Enterprise Agreement credentials, Cloud Cruiser can also collect resource details (such as metrics, tags, and resource group names) available through your Azure subscriptions. Cloud Cruiser collects that data per resource, but the permission do so is set at the subscription level in Azure. For this reason, if you want to collect subscription-level data, when you create the collection in Cloud Cruiser you must use an Azure account to connect that collection to each of your Azure subscriptions.

The user account you use must have either the Service Administrator or Co-Administrator role for each subscription you want to connect to the collection. Cloud Cruiser uses this role to establish Reader-level access in the subscription to be used for data collection, and does not maintain Service Administrator or Co-Administrator access after the temporary login session ends.

If you have multiple subscriptions and multiple subscription administrators, use one of the following strategies to ensure that Cloud Cruiser can discover and collect from your subscriptions:

  • Centralize subscription administrator roles with a single Azure user account. With this strategy, you designate a single Azure user account to collect data in Cloud Cruiser. Subscription Service Administrators then add that centralized user as a Co-Administrator of each subscription. The benefit of this strategy is simplicity, since you need only only one user to administer the Azure collection in Cloud Cruiser. Note that as new subscriptions are added in Azure, the Service Administrators of those subscriptions must add the centralized user as a Co-Administrator before that user can discover the new subscriptions in Cloud Cruiser. For more information about Azure administrator roles and how to add them to subscriptions, see How to add or change Azure administrator roles in the Microsoft Azure documentation.
  • Allow multiple Azure users to manage the Azure collection in Cloud Cruiser. With this strategy, you spread responsibility for managing the Azure collection in Cloud Cruiser among several people (the Service Administrators of your subscriptions). After you create the Azure collection in Cloud Cruiser, each subscription Service Administrator must add his or her subscriptions to the collection, as described in Updating a collection with additional subscriptions. If you use this strategy, note that each subscription Service Administrator must have a Cloud Cruiser user account with the Manage Data capability. See Permissions for more information about assigning Cloud Cruiser permissions.

Connecting a subscription to a Cloud Cruiser collection creates a service principal user in Azure named Cloud Cruiser. That user represents the Cloud Cruiser application in that subscription, and has only the Reader role. This allows Cloud Cruiser to view data but not make any changes, as Service Administrator or Co-Administrator access ends with the login session used to connect the subscription. The following image shows an example of that Cloud Cruiser user in the Azure Preview Portal:

Enabling diagnostics for Azure VMs

Cloud Cruiser can collect performance and utilization metrics for VMs that have diagnostics enabled in Microsoft Azure. Diagnostics captures system data on the virtual machines and virtual machine instances that run a cloud service. For a list of the specific Cloud Cruiser metrics fields collected from Azure and other providers, see Performance and utilization metrics.

To enable diagnostics for an Azure VM

  1. In the Azure Preview portal (https://portal.azure.com) click Virtual Machines.
  2. Click the VM you want to modify.
  3. In the Monitoring area of the menu pane, click Diagnostics settings.
  4. In the Diagnostics pane, select the Basic metrics box, and then set the Status field to On.
  5. Click Save.
  6. Repeat this procedure as needed to enable diagnostics for other VMs.

Creating a Microsoft Azure collection

Creating a Microsoft Azure collection in Cloud Cruiser enables you to collect usage and cost data from your Microsoft Azure Enterprise Account. The Azure collection automatically collects resource-level tags for resources deployed using the Azure Resource Manager (ARM) deployment model. If you add Azure subscriptions to your collection, Cloud Cruiser can collect group-level tags, as well as performance metrics for resources that have diagnostics enabled in Microsoft Azure.

To create an Azure collection

  1. On the Data > Collections screen, click the Add icon .
    The New Data Collection screen appears.
  2. Click Azure.
    The Credentials screens appears.
  3. Enter your Microsoft Enterprise Account Enrollment Number and Access Key, and then click Next.
    The Subscriptions page appears.
  4. (optional) If you want to add the subscriptions associated with your account, complete the following sub-steps. Otherwise, click Next.
    1. Click the plus icon () to enter the name of your Azure Active Directory and sign in to Microsoft.
    2. In the Directory field, enter the name of the Active Directory with the subscriptions you want to add, and then click Sign In With Microsoft. The Active Directory you enter must be the full name. For example, mydirectory.onmicrosoft.com.
      A separate window opens, prompting you to sign in to your Microsoft account.
    3. Using your Personal or Work/School account, sign in to Microsoft with an account that is either a Service Administrator or Co-administrator for the subscriptions in the Active Directory you entered. (For more information about assigning administrator roles to Azure subscriptions, see How to ad or change Azure administrator roles in the Microsoft documentation.)

      Cloud Cruiser connects to the subscriptions in the Active Directory you entered, and adds them to the Subscriptions list. The Status column shows whether subscriptions are connected, connecting, or not connected. Subscriptions that are not connected are either canceled or disabled in the Azure Preview portal.
    4. By default, the Collect checkbox is checked for all subscriptions. Uncheck any subscriptions you don't want used in this collection (such as subscriptions with a status of non connected), and then click Next.
  5. On the Options page, enter the following information:
    • Name: Enter a unique name for the collection.
    • Comments: Optionally, enter additional information about the collection. For example, you might describe the types of data you are collecting.
    • Earliest Date to Collect: Select the first day's data you want to collect. Cloud Cruiser collects data from that date forward. For example, if you had your cloud in a pre-production mode for a short time while you fine-tuned the services you offer, consider setting the date to the first day your cloud was in production.
    • Source Currency: The currency in which your cloud provider reports your charges. If the Source Currency and your account's display currency do not match, the following choices appear. These affect your entire account, not just this collection. For information about them, see Currency and locale:
      • Display Currency
      • Locale
  6. Click Finish.
    The new collection appears in your list of collections. Any errors or warnings related to your collection appear on the Health Checks page. For more information, see Health checks.

Updating a collection with additional subscriptions

You can add subscriptions to an Azure collection you already created. For example, you might have added subscriptions in Azure and you want to collect their metrics in Cloud Cruiser. After adding subscriptions, run collection manually to retrieve historical data for the new subscriptions.

Microsoft stores utilization data for 14 days only. It is stored permanently in Cloud Cruiser once collected, but you will see only the most recent 14 days of data immediately after recollecting. From that point forward data will be collected and stored daily.

To add subscriptions to an Azure collection

  1. In the list of collections, open the collection you want to edit.
    The Editing Data Collection dialog box appears.
  2. Click Manage Subscriptions.
  3. Click the plus icon () to enter the name of your Azure Active Directory and sign in to Microsoft.
  4. In the Directory field, enter the name of the Active Directory with the subscriptions you want to add, and then click Sign In With Microsoft. The Active Directory you enter must be the full name. For example, mydirectory.onmicrosoft.com.
    A separate window opens, prompting you to sign in to your Microsoft account.
  5. Using your Personal or Work/School account, sign in to Microsoft with an account that is either a Service Administrator or Co-administrator for the subscriptions in the Active Directory you entered. (For more information about assigning administrator roles to Azure subscriptions, see How to ad or change Azure administrator roles in the Microsoft documentation.)

    Cloud Cruiser connects to the subscriptions in the Active Directory you entered, and adds them to the Subscriptions list. The Status column shows whether subscriptions are connected, connecting, or not connected. Subscriptions that are not connected are either canceled or disabled in the Azure Preview portal.
  6. In the Collect column uncheck any subscriptions you don't want used in this collection (such as subscriptions with a status of non connected), and then click Save.
    The collection is saved, and you are returned to the Collections list.
  7. Click the gear icon next to your collection, and select Recollect.
    The Recollect dialog box appears.
  8. Enter the span of time you want to collect, and then click Recollect.
You must to post a comment.
Last modified
17:02, 21 Feb 2017

Tags

Classifications

This page has no classifications.