You can configure LogicMonitor to import AWS and Azure billing data using the Billing configuration tool to streamline the process of exporting cloud billing data from each provider into LogicMonitor.

You can also configure billing data imports from the Resource Tree by applying billing export data to your existing cloud resources. For more information on AWS billing Resource Tree configuration, see AWS Billing Monitoring Setup

Requirements for Configuring Billing Data for Cost Optimization

To configure billing, your LogicMonitor portal must already be set up to monitor AWS and Azure resources. You must also have the necessary IAM and Azure Entra roles in place to access billing data. For more information, see AWS Monitoring Setup and Adding Microsoft Azure Cloud Monitoring.

To configure AWS billing data for Cost Optimization, you must create a new Cost and Usage Report (CUR) within the AWS console. You will need the following information from the CUR:

  • Name of your Amazon S3 bucket
    To obtain the name of your S3 bucket, you must set up an Amazon S3 bucket for your Cost and Usage Report.
    For more information, see Setting up an Amazon S3 bucket for cost and usage reports from AWS.
  • Report path prefix of your cost and usage report
    To obtain the report path prefix, you must create a Cost and Usage Report that is enabled to integrate with Amazon Redshift.
    For more information, see Creating Cost and Usage Reports from AWS.

Recommendations:

  • Use AWS Cost and Usage Reports 2.0 when setting up billing monitoring whenever possible. Version 2.0 provides the Account Name in the report sent to LogicMonitor, while version 1.0 does not. Using a combination of versions 1.0 and 2.0 may display two different names for the same account in LogicMonitor Billing.
  • Do not select Include resource IDs when configuring your report. LogicMonitor does not currently collect these IDs.
  • Select Daily granularity and Parquet compression to optimize your report and reduce your data egress costs from AWS.
  • Activate Cost Allocation Tags in the AWS console and mark the resources and property normalization aliases you want included in Recommendations. For more information, see Activating user-defined cost allocation tags from AWS.

To configure Azure billing data for Cost Optimization, you must create a new data Export within the Azure console. For more information, see Create and manage exported data from Azure. You will need the following information from your Azure data export:

  • Export Name
  • Storage Account Name
  • Storage Account Container Name
  • Storage Account Container Directory

You must also assign a role within Azure to your LogicMonitor resource group. This process requires the following details associated with your LogicMonitor resource group:

  • Azure Tenant ID
  • Azure Client ID
  • Azure Secret Key

For more information, see Assign Azure roles to external users using the Azure portal from Azure.

Recommendation: To avoid issues while importing data to LogicMonitor, do not use unsupported configurations. LogicMonitor supports the following export configurations:

  • Cost and usage details (actual) version 2024-08-01 or earlier
  • Cost and usage details (FOCUS) version 1.0 or earlier

Configuring AWS Billing Data for Cost Optimization

  1. In LogicMonitor, navigate to Cost Optimization > Billing and select manage billing iconManage Billing Configurations.
  2. In Manage Billing Configurations, select create billing iconCreate Billing Configuration.
  3. In the Provider field, select “AWS.”
  4. In the Display Name field, enter a name for your AWS configuration.
  5. (Optional) Enter a Description.
    aws billing configuration
  6. In Permissions settings, the AWS Account ID field populates automatically with the ID of an AWS account. LogicMonitor uses this account to collect billing data from your AWS account.
  7. (Optional) Enable Re-use External ID. This allows you to use the same External ID from an AWS account already connected to LogicMonitor.

Note: Leaving this option disabled automatically generates a new External ID for your Billing configuration.

  1. In the Select an existing AWS Account field, enter or search for an AWS account from which to collect billing data.

Note: If Re-use External ID is disabled, this field is hidden.

  1. The Create a new policy field comes pre-filled with a basic set of permissions to enable LogicMonitor access to your Cost and Usage Report

Recommendations:

  • If the External ID you selected does not already have an IAM Policy with these permissions applied, you can copy the JSON script provided and apply it to your role in the AWS console.
  • This field does not automatically apply a policy to your IAM role. For more information, see Policies and Permissions from AWS.
  1. In the Add role ARN to LogicMonitor field, enter the Amazon Resource Number (ARN) for LogicMonitor’s IAM role. For more information, see IAM Identifiers from AWS.
    aws billing permissions
  2. In the Billing info tab, enter the S3 Bucket Name and Report Path Prefix into the provided fields.
    aws billing info
  3. Select Verify and add export.

Configuring Azure Billing Data for Cost Optimization

  1. In LogicMonitor, navigate to Cost Optimization > Billing and select manage billing iconManage Billing Configurations.
  2. In Manage Billing Configurations, select create billing iconCreate Billing Configuration.
  3. In the Provider field, select Azure.
  4. In the Display Name field, enter a name for your AWS configuration.
  5. (Optional) Enter a Description.
    azure billing configuration
  6. In the Permissions tab, enter the Azure Tenant ID, Azure Client ID, and Azure Secret Key into the provided fields.
    azure billing info
  7. In the Billing tab, enter the Export Name for your Azure data export.
  8. Enter the Storage Account Name, Storage Account Container Name, and Storage Account Container Directory into the provided fields.
    azure billing permissions
  9. Select Verify and add export.

Configuring Azure Billing Using the Resource Tree

  1. In your Azure console, create a new data Export. For more information, see Create and manage exported data from Azure.
  2. Assign a role within Azure to your LogicMonitor resource group.
    • This process requires the Azure Client ID associated with your LogicMonitor resource group. For more information, see Assign Azure roles to external users using the Azure portal from Azure.
    • When editing the IAM config for the storage account to which you send exports, assign the Storage Blob Data Reader role to the AppRegistration used for LogicMonitor.
  3. In LogicMonitor, navigate to Resource Tree and select the Manage icon for your Azure resource group, then select Permissions to locate the Client ID.
  4. Select the report and copy the Subscriptionid assigned to it. The Subscription name provided by Azure in the cost export will appear as the Account Name in LogicMonitor Billing. If you want to enable enhanced billing features, copy the following details:
    • Export Name
    • Storage Account Name
    • Storage Account Container Name
    • Storage Account Container Directory
  5. In LogicMonitor, navigate to Resource Tree and select the resource group used to monitor your Azure environment.
  6. Select Manage > the Billing tab. Enter the information above into the provided fields,
  7. Select Verify Enhanced Billing to validate any changes.
monitor azure billing

Note: Note: Amortized Azure reports are not supported at this time. Only use one export configuration when importing data. Using both at once may lead to errors or duplicated report data.