Adding Microsoft Azure Cloud Monitoring

Last updated on 07 June, 2024

Monitoring your Microsoft Azure environment with LogicMonitor helps you to manage performance and identify potential faults. Add LogicMonitor to your Azure environment to monitor the state of your Azure deployment, underlying services, and license usage. For more information, see Register an application with the Microsoft identity platform from Microsoft Azure.

Requirements

You must register your LogicMonitor account as an app with Microsoft Azure Identity Access Management (IAM) before adding Azure to LogicMonitor. You need the following credentials from this process when finished:

  1. Azure Tenant ID–Directory (tenant) ID from Azure > App Registrations > Overview.
  2. Azure Client ID– Application (client) ID from Azure > App Registrations > Overview.
  3. Azure Secret Key–Value from Azure > App Registrations > Certificates & Secrets > Client Secrets.

Adding Your Azure Environment to LogicMonitor

After you register LogicMonitor in your Azure environment, you can add Azure to LogicMonitor for monitoring and logs. For more information, see Sending Azure Logs.

Use the following steps to add the required information about your Azure App Registration:

1. Navigate to Resources > Add > Cloud Account.

Note: If you’re using the New UI Preview toggle, go to Resources > Add [+] > Cloud and SaaS.

2. Select Azure > Add.

3. On the Name page, enter a Name and Description for your Azure account. These fields determine how your Azure resource is displayed throughout the LogicMonitor environment.



4. To place the new resource into an existing group, select the group from Parent Group field. You can type to search. The default value is root, or the first level of the Resources Tree.

5. (Optional) You can enter key-value pair properties by entering a Name and Value. Or, you can select from a list of existing properties. For more information, see Instance and Resource Properties.

6. Select Next: Permissions.

7. On the Permissions page, enter the Azure Tenant ID, Azure Client ID, and Azure Secret Key.


8. Select Get Subscriptions. All subscriptions available to LogicMonitor based on the permissions you’ve configured are listed. If you don’t see the subscriptions you expect, verify that the application you created in Azure has reader permissions for those subscriptions.

9. Select Next: Services.

10. On the Services page, enable or disable the Azure services listed to customize monitoring your environment.

Note: If you’re adding LogicMonitor services for Backup Protected Items or Recovery Protected Items, you need to make configuration changes to the Recovery Service Vault and Log Analytics Workspace in Microsoft Azure. For more information, see Forwarding Backup and Recovery Events.

11. Select Test Permissions to authenticate.

12. Select Next: Billing.

13. On the Billing page, enter the Subscriptions ID, Offer ID, and Monthly Billing Date.


Note: You have the option to provide Billing details using Azure Rate Card or Azure Cost Management. LogicMonitor recommends using Azure Cost Management whenever possible. For Azure Cost Management, enter the Subscription ID from Azure > Subscriptions > Overview. For Rate Card, go to Azure > Subscriptions > Settings > Billing Properties > Microsoft Azure Plan to view your plan’s Subscription ID, Offer ID, and Monthly Billing Date. For more information, see Monitoring Azure Billing.

14. Select Add Billing and then select View Azure Resources to finish.

Configuring Azure Services in LogicMonitor

  1. Navigate to Resources and select the Azure resource that you added.
  2. Select Manage and then select the Services tab.
  3. Select Default Settings.
  4. On the Global Settings tab:
    • NetScan Frequency: Select the preferred frequency for scheduling NetScans.
    • Automatically delete terminated Azure resources if they are no longer available in the cloud portal: Enable to automatically remove “dead” instances. You can also select whether this happens immediately or after a specified period during, where no data is received for the instance. This does not remove resources terminated prior to adjusting this setting. These resources must be deleted manually.
    • Automatically disable alerting for terminated Azure resources if they are no longer available in the cloud portal: Select this option to disable alerting for terminated instances. This ensures that you will not receive any alerts once instances are terminated if they are not scheduled to be automatically deleted.

Note: LogicMonitor intelligently and automatically stops Azure Monitor API data collection once instances are terminated. This option ensures that you do not receive alerts for traditional Collector DataSources like Ping.

  1. In the Monitored Regions section, you can enable or disable the regions that you want to monitor.
  2. Select the Tags tab. To monitor Azure instances for a particular service, you can tag those instances from your Azure portal and then apply a tag filter in LogicMonitor. If you specify a tag filter, only Azure resources that meet the filter criteria will be added to your LogicMonitor account. The criteria is as follows:
    • You can use glob expressions with the tag filter. For example: tag value = prod*
    • Resources are discovered when they contain one or more tags specified with an include operation, and not with any of the exclude tags.
    • The tag filter is case sensitive.
  3. Select Save.

For a list of Azure services monitored, see Cloud Services and Resource Units. Due to how Azure generates metric data, there may be a delay before logs and metrics appear in LogicMonitor. This delay time varies based on the type and size of the data gathered from Azure.

In This Article