Configure an Azure connector to pull metric data Operational Intelligence provides the AzureConnector connector definition which you can use to create a connector to pull metric data from Microsoft Azure. Operational Intelligence then analyses this data to provide statistical scores and detect anomalies. Before you beginOperational Intelligence plugin (com.snc.sa.metric) must be activated for the Operational Intelligence connectors to appear in the base system. In addition, the Azure connector requires an Azure Service Principal credential that lets the instance access Azure accounts. You can use an existing credential, or create a new one.Role required: evt_mgmt_admin About this task After you configure the Microsoft Azure connector, you can run a test to ensure that the MID Server can authenticate itself to the Azure account. Procedure Navigate to Event Management > Event Connectors (Pull) > Connector Instances. Click New. Fill out the Connector Instance form. Field Description Name A unique name for the connector instance record, such as the name of event source host. Description Any optional information that the administrator wants to use to identify this record. Connector definition Vendor and protocol used to gather metric data from the external source. Select AzureConnector. Host IP Not used for this connector. Therefore any value such as 18.104.22.168, is valid. Metrics collection Designates collection of metric data for Operational Intelligence.This option appears only if the connector definition that is selected supports metric collection (such as SCOM) and if the Metrics collection option is selected. Metrics collection last run time The date and time of the most recent metric data collection. The value of this field is automatically populated. Last metrics collection status Status of the metric data collection activity. The value of this field is automatically populated.This option appears only if the connector definition that is selected supports metric collection (such as SCOM) and if the Metrics collection option is selected. Metrics collection schedule (seconds) The time, in seconds, to repeat the metric data collection scheduled job.This option appears only if the connector definition that is selected supports metric collection (such as SCOM) and when the Metrics collection option is selected. Credential A valid credential of the Azure Service Principal type, to the Microsoft Azure data source host. Click the Lookup using list icon to select a credential, or to create a new one. Last error message Last error message received by the connector. If the test connector fails, an error message appears in this field. In the MID Servers for Connectors related list, click Insert a new row and then select a MID Server to send metric data to. Right-click the form header and select Save. In the Connector Instance Values related list, for each name, double-click the Value column and enter values as follows: Name Value max_fetch_interval_min Maximum time in minutes to go back to for retrieving data.Example value: 15 offset_min Number of minutes to shift the time interval back by.Example value: 5 subscription_id A unique GUID for your subscription to Azure services. To obtain your subscription ID: Log on to the Azure portal. In the left navigation panel, click Subscriptions to list your subscriptions and the subscription ID. Click Test connector to verify that the MID Server can communicate with the external server host. If the test fails, follow the instructions on the page to correct the problem and then run another test. The description of the reason for failure is shown in the MID Server log, according to the type of error, such as, Events, Metrics, or Bi-Directional. After a successful test, select the Active check box and then click Update.