Adding Microsoft Azure Cloud Monitoring

Product Documentation

Monitor the state of your Azure deployment, underlying services, and license usage. Monitoring your Azure environment with LogicMonitor helps you to manage performance and identify potential faults. To add your Azure environment to LogicMonitor, compete the following steps:

Add an App Registration in Microsoft Azure.
Add your Azure environment to LogicMonitor.

Requirements

You must be an administrator of an active Microsoft Azure account to perform the Azure setup steps.

Adding an App Registration in Azure

From the Azure Active Directory, select Add > App registration.
On the Register an application page, provide a name for your application and then select Accounts in this organizational directory only.
Select Register.
On the Overview page, copy the Application (client) ID and the Directory (tenant) ID and save them to a secure location.
Select Certificates & secrets and then select New client secret.
On the Add a client secret panel, enter a Description and select an Expires value (in months).
Select Add.
Copy the Value and Secret ID from the Certificates & secrets page and save them to a secure location.

Important: Do not skip this step. You are not able to retrieve these values after you navigate away from this page. The Value is required when adding the Azure account to LogicMonitor.

Navigate to Azure Services > Subscriptions and select the link for the Subscription name that you’re using.
On the Subscriptions page, copy the Subscription ID and save it to a secure location.
Select Access control (IAM) and then select Add > Add role assignment.
On the Add role assignment page, use the search field to find and select a Role. You must select at least a Reader role to continue.
Select Next.
On the Members tab, click Select members.
On the Select members panel, search for and select the App Registration (member) that you added previously.
Click Select.
Review the information on the Members tab and then select Next.
Review the information on the Review + assign tab and then select Review + assign.

Adding a Large Number of Subscriptions

For a large number of subscriptions, you can assign permissions using PowerShell. For example, the following PowerShell script will add an AAD application for LogicMonitor and add the application as a reader to each subscription available to the user that runs the script.

# Authenticate to all Azure subscriptions that the user has access to
Login-AzureRmAccount

# Password for the service principal
$pwd = "{service-principal-password}"

# Create a new Azure AD application
$azureAdApplication = New-AzureRmADApplication `
             -DisplayName "LogicMonitor" `
             -HomePage "https://lmtest.logicmonitor.com" `
             -IdentifierUris "https://lmtest.logicmonitor.com" `
             -Password $pwd

# Create a new service principal associated with the designated application
New-AzureRmADServicePrincipal -ApplicationId $azureAdApplication.ApplicationId

# Assign Reader role to the newly created service principal for each subscription
Get-AzureRmSubscription | ForEach-Object {
  Set-AzureRmContext -SubscriptionId $_.SubscriptionId
  New-AzureRmRoleAssignment -RoleDefinitionName Reader `
            -ServicePrincipalName $azureAdApplication.ApplicationId.Guid
}

Adding Your Azure Environment to LogicMonitor

In LogicMonitor, add the required information about your Azure App Registration.

Navigate to Resources > Add > Cloud Account.

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

Select Azure > Add.
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.
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.
(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.
Select Next: Permissions.
Enter the following information on the Permissions page:
- Azure Tenant ID: The Directory (tenant) ID from Azure > App Registrations > Overview.
- Azure Client ID: The Application (client) ID from Azure > App Registrations > Overview.
- Azure Secret Key: The Value from Azure > App Registrations > Certificates & Secrets.
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.
Select Next: Services.
On the Services page, enable or disable the Azure services listed.

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.

Select Test Permissions to authenticate.
Select Next: Billing.
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.

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

Configuring Azure Services in LogicMonitor

Navigate to Resources and select the Azure resource that you added.
Select Manage and then select the Services tab.
Select Default Settings.
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.
- 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.

In the Monitored Regions section, you can enable or disable the regions that you want to monitor.
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.
Select Save.

Note: For a list of Azure services monitored, see Cloud Services and Resource Units.

Privacy overview