Integrate Azure Monitor as an authenticated data source
Summarize
Summary of Integrate Azure Monitor as an Authenticated Data Source
This guide describes how to integrate Microsoft Azure Monitor with ServiceNow Event Management by configuring it as an authenticated data source. This integration allows for the collection of events from Azure Monitor into the ServiceNow platform, enhancing IT operations management.
Show less
Key Features
- Authentication Methods: Two methods are available for authentication:
- OAuth Authentication: Uses Azure Monitor V1 or V2 access tokens for enterprise-grade security.
- Basic Webhook Authentication: A simpler method suitable for smaller teams that do not require Azure Active Directory.
- Event Field Mappings: Predefined mappings are included to map Azure Monitor events to ServiceNow event fields, with the flexibility to add custom mappings.
- Bi-directional Connector: Enables alert state changes to be sent from ServiceNow to the Azure Portal, allowing for synchronized event management.
Key Outcomes
Upon successful integration, ServiceNow customers can expect:
- Automated collection of Azure Monitor alerts, improving incident response and visibility.
- Accurate mapping of Azure event severities to ServiceNow, facilitating effective prioritization and resolution.
- Enhanced operational efficiency through streamlined communication between ServiceNow and Azure Monitor.
Before starting the integration, ensure that the required roles and plugins are in place, and perform Azure Cloud Discovery as needed to bind alerts to configuration items within ServiceNow.
Integrate Microsoft Azure with Event Management by adding the Azure Monitor as an authenticated data source.
- Authenticates the Azure Monitor alert message with the relevant ServiceNow user, using OAuth configuration or a standard webhook.
- Extracts information from the original Azure Monitor alert message to populate required event fields and inserts the event into the ServiceNow AI Platform database.
- Captures specified content in the Additional Information field of the event form.
What authentication is used
- OAuth authentication: Provides enterprise-grade authentication to keep your enterprise environment safe. Authentication is performed using Azure Monitor V1 or V2 access tokens. For more information, see Integrate Azure Monitor with OAuth authentication.
- Basic webhook authentication: Provides a basic standard of authentication, without the need for Azure Active Directory. This authentication can be especially useful for distributed small teams, such as SRE or DevOps teams. For more information, see Integrate Azure Monitor with basic authentication.
What to know before you begin
You can use your integrated Azure Monitor as a data source only after you have verified the following:
- For both methods of authentication, the relevant ServiceNow sys_user is assigned the evt_mgmt_integration role.
- The Event Management Connectors plugin is installed in the ServiceNow AI Platform instance. You can download the plugin from the ServiceNow Store website.
- Azure Cloud Discovery must be performed to ensure that the created alerts are bound to the configuration items in the ServiceNow AI Platform. For more information, see Azure Cloud Discovery.
Event Rules and Event Field mappings
These event rules and event field mappings are provided with the base system:
| Module | Description |
|---|---|
| Event Rules | Azure Monitor: A general event rule to handle all Azure Monitor events. |
| Event Field Mappings | Azure Monitor - ci_type: To map ci_type of events based on resourceType field. A base set of mapping pairs are provided. |
If you want to send alert state changes on the ServiceNow instance from the ServiceNow alerts to the Azure Portal, you need to enable the Azure Monitor Bi-directional connector. For more information, see Configure Azure Monitor Bi-directional connector.
Severity mapping from Azure severity to ServiceNow event severity
| Azure severity condition | ServiceNow event severity |
|---|---|
| When an Azure alert monitorCondition is Fired | |
| Azure Sev0 | ServiceNow Critical (severity "1") |
| Azure Sev1 | ServiceNow Major (severity "2") |
| Azure Sev2 and Sev3 | ServiceNow Warning (severity "4") |
| Azure Sev4 | ServiceNow OK (severity "5") |
| When an Azure alert monitorCondition is resolved | |
| Any Azure severity | ServiceNow CLEAR (severity "0") |