--- sourceDocument: Brazil IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Azure Monitor Issue integration # Azure Monitor Issue integration {#ariaid-title1} Release version: Brazil Updated November 5, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read An Azure Issue is a unified case that aggregates related alerts and signals from Azure Monitor into a single, trackable operational problem. It preserves investigation context and serves as a durable record for incident management Incident Management, so you can resolve problems faster instead of tracking scattered alerts. ## Before you begin Verify you already have an Azure Monitor Workspace. Role required: evt_mgmt_admin ## About this task ServiceNow represents an Azure Issue as a single alert. View the alerts that Azure grouped into the Issue in the Related Records tab from the Express List side panel or the alert record in Service Operations Workspace. ServiceNow retains each related alert as an individual alert. This approach lets ServiceNow group and correlate alerts across multiple resources and monitoring systems. ServiceNow is not limited to the alerts that Azure grouped into the Issue. As a result, ServiceNow identifies broader incidents, reduces duplicate alerts, and provides a more comprehensive operational view. For this reason, ServiceNow represents an Azure Issue as a single alert instead of an alert group. Note the following before you start: * If you already use the Azure Push Connector to send Microsoft Azure alerts to ServiceNow, use the same push connector URL to send Azure Issues. * If you're configuring Azure alerts/issues for the first time, use the Azure Push Connector URL to create an action group in the Azure portal. Use the following URL in the Azure action group secure webhook field: https://.service-now.com/api/sn_em_connector/em/inbound_event?source=azuremonitor * If you have different tenants with different Azure Service Principal credentials (per tenant or per subscription), create separate Azure Push Connector instances. Use them to push Azure alerts or issues into your ServiceNow instances. {#azure-monitor-issue-integration__ul_g5c_bjy_xjc} You can integrate Azure Monitor issues using Integration Launchpad. For more information, see [Configure Azure Monitor Issue in Integrations Launchpad](https://www.servicenow.com/docs/8nZIne~NepjKb2Kovc~7sw "An Azure Issue is a unified case that aggregates related alerts and signals from Azure Monitor into a single, trackable operational problem. It preserves investigation context and serves as a durable record for incident management, so you can resolve problems faster instead of tracking scattered alerts."). ## Procedure 1. In the Azure Monitor portal, perform the following steps: 1. Navigate to your Azure Monitor Workspace. 2. Navigate to SettingsAction groups and select the existing action group that you use to send Azure alerts to ServiceNow. This creates an alert, and in turn, the Alert Management rule creates an incident. If you're configuring Azure issues for the first time, first create an action group by following the steps in [Integrate Azure Monitor with OAuth authentication](https://www.servicenow.com/docs/4hckkC47Gxn8ymDKvryPEg "Integrate Microsoft Azure with Event Management by authenticating Azure V1 or V2 tokens in the Azure Monitor."). 3. To view related alerts and resource information for an issue in the Azure portal under the Alerts and Resources tabs, or to enable bi-directional synchronization, configure the pull connector. Follow the steps in the following procedure. {#azure-monitor-issue-integration__ol_vtp_ddy_xjc} 2. In the ServiceNow AI Platform instance, configure a pull connector if you have used a push connector to send Azure issues by perform the following steps: 1. Navigate to the push connector you're using by going to AllPush connectors. 2. Select the Azure Monitor push connector. 3. Select Configure Issue Alerts on the push connector form. You're redirected to the pull connector instance form. 4. If the Azure Monitor pull connector is already activated, verify your credentials and that the instance is active, then select Test Connection to validate. 5. If the Azure Monitor pull connector is not activated yet, configure it as follows: 1. Leave the pull connector instance name as Azure Monitor. 2. In the Credentials field, enter your Azure Service Principal credential. 3. Leave the Host field as 1.1.1.1 as it will not be used. 4. Select the Active check box to activate the connection. 5. Set fetchIssueRelatedAlerts to control whether the system fetches related alerts for the issue. The default is true. Set it to false if you want to disable this behavior. 6. Set fetchIssueRelatedAlertsLimit to the maximum number of related alerts the system fetches for the issue. The default is 10. 7. Select Test Connection to validate the connection. If Azure bi-directional connector is enabled, when an Azure issue is closed in ServiceNow, it automatically closes in the Azure portal as well. When an Azure issue is closed in ServiceNow, it automatically closes in the Azure portal as well. {#azure-monitor-issue-integration__ol_r2l_rjy_xjc} {#azure-monitor-issue-integration__ol_q2l_rjy_xjc} 3. In the ServiceNow AI Platform instance, configure a pull connector if you have used a push connector instance to send Azure issues by perform the following steps: 1. Navigate to the push connector instance you're using in ServiceNow by navigating to AllPush connector Instances. 2. Select the Azure Monitor push connector instance that was used to send Azure Issues in to ServiceNow instance. 3. Select Configure Issue Alerts UI action present in the push connector form. You're redirected to the pull connect instance form. 4. In the pull connector creation form, perform the following steps: 1. Leave the pull connector instance name as is.The pull connector instance name must match with the push connector instance name. 2. In the Credentials field, enter your Azure Service Principal credential. 3. Leave the Host field as 1.1.1.1 as it will not be used. 4. Select the Active check box to activate the connection. 5. Set fetchIssueRelatedAlerts to control whether the system fetches related alerts for the issue. The default is true. Set it to false if you want to disable this behavior. 6. Set fetchIssueRelatedAlertsLimit to the maximum number of related alerts the system fetches for the issue. The default is 10. 7. Select Test Connection to validate the connection. If Azure bi-directional connector is enabled, when an Azure issue is closed in ServiceNow, it automatically closes in the Azure portal as well. {#azure-monitor-issue-integration__ol_crk_2hd_yjc} {#azure-monitor-issue-integration__ol_brk_2hd_yjc} *[\>]: and then