Home > Cloud Cruiser 4 > Collecting, transforming, and publishing > Microsoft Azure > Creating Microsoft Azure data sources

Creating Microsoft Azure data sources

Cloud Cruiser includes the following data sources you can use to connect to Microsoft Azure:

  • Microsoft Azure: Connects to the Microsoft Azure using your Microsoft Active Directory account. Use this data source to collect Microsoft Azure diagnostics data, tags, device usage, services, and rates, as described in Creating Microsoft Azure collections.
  • Microsoft Azure EA Billing: Collects to the Microsoft Azure using your Microsoft Azure Enterprise Account. Use this data source to collect cost and usage data, as described in Creating Microsoft Azure collections.

Creating a Microsoft Azure data source

Before you begin

Before you create a Microsoft Azure data source in Cloud Cruiser, ensure that you have an Active Directory account configured in the Classic Azure portal, and that your Active Directory includes a Web application with access to your Cloud Cruiser URL. Microsoft uses this application to authenticate your connection between the Cloud Cruiser portal and the Azure portal.

Creating an Azure Active Directory

To create an Azure Active Directory

  1. Log in to the Azure Classic Portal (https://manage.windowsazure.com).
  2. In the Navigation pane, click Active Directory.
  3. At the bottom of the screen, click New, and then select Directory > Custom Create.
  4. In the Add Directory dialog box, enter information about your new Active Directory. In the Domain Name field, enter a subdomain for your tenant.
  5. Click the checkmark to save your Active Directory.

Creating a Web application in your Active Directory

To create a Web application in your Active Directory

  1. In the Azure Classic Portal (https://manage.windowsazure.com), open your Active Directory, and then select Applications.
  2. At the bottom of the window, click Add, and then select Add an application my organization is developing.
  3. Enter a Name for this application, select Web Application and/or Web API, and then click the Arrow icon.
  4. On the second screen, enter information for accessing your application, and then click the Checkmark icon.
    • Sign-On URL: The URL where users will access your application. This is where Azure Active Directory will return an authentication token. For example, http://cloudcruiser.com.
    • App ID URI: Azure Active Directory uses this URI to identify your application when users request access to it. It must be a valid URI and unique in your directory. Use the following format: http://<directoryDomainName>. For example, http://ccruiser.onmicrosoft.com.
  5. After your application has been created, click Configure to open the Configuration Screen.
  6. In the Application is Multi-Tenant field, select Yes to allow users from other Azure Active Directories to use this web application.
    appMultiTenant.png
  7. In the Keys section, select a duration to generate new keys for the application.
  8. In the Reply URL field, enter the following URL, where <ccServer> is the hostname or IP address of your Cloud Cruiser server:
    http://<ccServer>/azureauth/msLanding.html?
  9. In the Permissions to Other Applications section, modify the permissions that enable the application (on behalf of users) to access Azure Resource Manager to query subscriptions and configure role-based access when connecting and disconnecting subscriptions:
    1. Leave the default Enable single sign-on and read user’s profile delegated permission selection for Windows Azure Active Directory in place.
    2. Click Add Application.
    3. Select the Windows Azure Service Management API row, and then click the Checkmark icon at the bottom of the dialog box.
    4. For the new permission, open the Delegated Permissions menu and select Access Azure Service Management.
      appPermissions.png
  10. At the bottom of the window, click Save.
  11. Immediately after saving the configuration changes, note the key value that is now visible in the Keys section of the Configuration page. You will need this key when creating a Microsoft Azure data source in Cloud Cruiser, and the key will be obscured in the Azure Portal after you exit the Configuration page.
    appKeys.png 

Creating the data source

To create a Microsoft Azure data source

  1. Navigate to Data > Setup > Sources.
  2. In the list of data sources, right-click Microsoft Azure and select Add data source.
  3. Enter a Name for the data source, ensure that the Type is Microsoft Azure, and then click OK.
  4. In the Client ID field, enter the Client ID of your Active Directory application, which you can find in the Classic Azure Portal.
    If you are using the Azure Preview Portal, select Browse > Active Directory to open the Active Directory section in the Classic Azure Portal. In the Active Directory section, open the Applications list for your directory, select your web application, and then click Configure
    idKey.png
  5. In the Client Secret field, enter the key value for your application, generated in the Classic Azure portal. After you generate the key, it is obscured in the Azure portal. If you did not store your key elsewhere, you might need to generate a new key.
  6. Click Add a new Tenant to begin the process of adding Azure subscriptions to this data source.
    A connection dialog box appears.
  7. In the Sign in to your MS Account section, select the type of your Microsoft Azure account, and then enter the name of your Active Directory.
    azureConnect.png
  8. Click Sign In.
    The Microsoft Sign in page opens in a new browser window.
    azureLogin.png
  9. Enter your Microsoft credentials, and then click Sign in.
    A Microsoft confirmation page opens, prompting you to accept the connection between Cloud Cruiser and your Active Directory Web application.
  10. Click Accept.
    A Success message appears.
    azureSuccess.png
  11. Click Close to close the message and the browser window.
  12. In Cloud Cruiser click OK to close the Success dialog box.
    Now that Cloud Cruiser is authenticated with your Active Directory account, your subscriptions appear in the connection dialog box.
    azureConnectWithSubs.png
  13. Select one or more subscriptions, and then click OK. Cloud Cruiser will collect data for all selected subscriptions.
  14. If you want to add another tenant to this data source, click Add a new Tenant, and proceed through the steps for adding that tenant and its subscriptions.
  15. (Optional) In the Comments field, enter notes about this data source.
  16. Click Test Connection to test the data source parameters. If the test fails, make corrections until the test is successful.
  17. Click Save.

Creating a Microsoft Azure EA Billing data source

This collector 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.

To create a Microsoft Azure EA Billing data source

  1. Navigate to Data > Setup > Sources.
  2. In the list of data sources, right-click Microsoft Azure EA Billing and select Add data source.
  3. Enter a Name for the data source, ensure that the Type is Microsoft Azure EA Billing, and then click OK.
  4. In the Endpoint field, enter the URL for the Microsoft Azure Enterprise Portal, https://ea.azure.com.
  5. 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.
  6. 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 https://ea.azure.com endpoint, investigate whether you need to generate a new API key in the Microsoft Azure Enterprise Portal.

    AzureEABillingDataSource.png

  7. (Optional) If you want Cloud Cruiser to connect to your data source through a proxy server, use the Proxy fields to specify the proxy information.
  8. (Optional) In the Comments field, enter notes about this data source. For example, you might note when the Access Key is set to expire.
  9. Click Test Connection to test the data source parameters. If the test fails, make corrections until the test is successful.
  10. Click Save.
Last modified

Tags

Classifications

This page has no classifications.
© Copyright 2018 Hewlett Packard Enterprise Development LP