Skip to main content
Cloud Insights

Configuring the Azure compute data collector

Contributors netapp-alavoie mkniep

Cloud Insights uses the Azure compute data collector to acquire inventory and performance data from Azure compute instances.

Requirements

You need the following information to configure this data collector.

  • Port requirement: 443 HTTPS

  • Azure OAuth 2.0 Redirect URI (login.microsoftonline.com)

  • Azure Management Rest IP (management.azure.com)

  • Azure Resource Manager IP (management.core.windows.net)

  • Azure Service Principal Application (Client) ID (Reader role required)

  • Azure service principal authentication key (user password)

  • You need to set up an Azure account for Cloud Insights discovery.

    Once the account is properly configured and you register the application in Azure, you will have the credentials required to discover the Azure instance with Cloud Insights. The following link describes how to set up the account for discovery.
    https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal

Configuration

Enter data into the data collector fields according to the table below:

Field Description

Azure Service Principal Application (Client) ID (Reader role required)

Sign-in ID to Azure. Requires Reader Role access.

Azure tenant ID

Microsoft tenant ID

Azure Service Principal Authentication Key

Login authentication key

I understand Microsoft bills me for API requests

Check this to verify your understanding that Microsoft bills you for API requests made by Insight polling.

Advanced Configuration

Field Description

Inventory Poll Interval (min)

The default is 60

Choose 'Exclude' or 'Include' to Apply to Filter VMs by Tags

Specify whether to include or exclude VM's by Tags when collecting data. If ‘Include’ is selected, the Tag Key field can not be empty.

Tag Keys and Values on which to Filter VMs

Click + Filter Tag to choose which VMs (and associated disks) to include/exclude by filtering for keys and values that match keys and values of tags on the VM. Tag Key is required, Tag Value is optional. When Tag Value is empty, the VM is filtered as long as it matches the Tag Key.

Performance Poll Interval (sec)

The default is 300

Troubleshooting

Additional information on this Data Collector may be found from the Support page or in the Data Collector Support Matrix.