--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Microsoft Azure Log Analytics # Microsoft Azure Log Analytics integration configuration fields {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Microsoft Azure Log Analytics integration configuration fields This guide details the configuration fields required to set up the Microsoft Azure Log Analytics integration within ServiceNow's Health Log Analytics. It explains how to configure the integration to retrieve log data from Azure Log Analytics, including defining connection settings, authentication, data retrieval parameters, and advanced options for log processing. Show full answer Show less ## Integration Setup Essentials * **Integration Name:** A unique identifier for the integration instance, which dynamically updates the displayed form name. * **Execute on:** Choose whether to use a specific MID Server or a MID Server cluster for pulling log data. * **MID Server / MID Server Cluster:** Required selection depending on the execute option. Only MID Servers that support basic authentication (not mTLS) are selectable. Clusters provide failover protection by shifting data input tasks if a MID Server fails. * **Service Instance:** Bind the retrieved log data to a specific ServiceNow service instance. * **Data Source:** Fixed as Azure Log Analytics, indicating the source of log data. * **Description:** Optional field to add descriptive information for easier identification. ## Authentication and Data Retrieval Configuration * **Redirect URL:** Required URL corresponding to the Azure redirecturi authorization property, essential for OAuth workflows. * **Authentication Method:** Choose an existing Azure Service Principal credential or create a new one by providing Tenant ID, Client ID, and Secret key, enabling secure API access. * **Workspace ID:** The Azure Log Analytics Customer ID used for REST API calls. * **Table Name:** Specify the Azure Log Analytics table from which logs will be fetched. * **Event Time Property Name:** Define the Azure Log Analytics field that contains the event timestamp. ## Advanced Settings for Log Processing * **Event Processor Workers and Queue Size:** Configure concurrency and queue capacity for efficient log event processing. * **Sub Sample Ratios:** Control the volume of events fetched and received to manage data load. * **Max Documents per Query:** Limit the number of rows returned per API query to optimize performance. * **Columns to Select:** Specify which columns to retrieve unless a custom query is used. * **Character Encoding:** Define encoding for the incoming data. * **Sleep and Polling Intervals:** Set time delays between queries, especially after no events are returned, to balance timeliness and resource use. * **Drop if Queue is Full:** Option to discard logs under MID Server load to prevent overload. * **Log Query:** Allows defining a custom Kusto Query Language (KQL) query in JSON format, overriding other query fields. This enables tailored data retrieval according to specific criteria. ## Practical Benefits for ServiceNow Customers By configuring these fields accurately, ServiceNow customers can effectively integrate Azure Log Analytics data into Health Log Analytics for enhanced monitoring and operational insights. The ability to select MID Servers or clusters provides resilience and scalability, while flexible authentication ensures secure data access. Advanced query customization and data retrieval settings allow customers to optimize performance and focus on relevant log data, enabling informed decision-making and streamlined IT operations. Description of the fields on the Microsoft Azure Log Analytics integration configuration forms for Health Log Analytics. For the Microsoft Azure Log Analytics integration setup procedure, see [Set up a Microsoft Azure Log Analytics integration for Health Log Analytics](https://www.servicenow.com/docs/psDo1Bm5unXdAKSgBSTcIA "Set up an integration for streaming log data from Microsoft Azure Log Analytics to your ServiceNow instance. The integration points the Health Log Analytics AI engine to a data source in your Microsoft Azure Log Analytics account."). {#il-connector-hla-azure-la-fields__table_pxx_hz1_42c__entry__2} | Field | Description | |-|-| | Integration Name | Unique name of this integration. For example: My Azure Log Analytics integration. This field is required. Note: When you fill in this field, the generic name displayed on the form adjusts automatically to match the name you entered. | | Execute on | Option to select whether to use a specific MID Server or a MID Server cluster. This field is required. | | MID server name | (Only when the Execute on field is set to Specific MID Server) MID Server to which log data from Microsoft Azure Log Analytics is pulled. This field is required. Note: * You can select only MID Servers that support basic authentication. MID Servers that support mTLS are not listed. * The default maximum number of integrations streaming logs to a single MID Server is 10. You can modify this number in the MID Server properties. * If log ingestion is not enabled for the selected MID Server, Health Log Analytics enables it automatically. {#il-connector-hla-azure-la-fields__ul_m4x_kcb_42c} | | MID MID Server Cluster | (Only when Execute on is set to Specific MID Server cluster.) The MID Server cluster to which the log data is pulled. This field is required. The data input runs on a single MID Server in the cluster until that MID Server fails. The system then moves all the data input tasks to the next available MID Server in the cluster according to the configured order. Note: * Health Log Analytics supports only failover MID Server clusters. In these clusters, multiple MID Servers are grouped together for failover protection. When selecting a cluster from the data input or integration form, the MID Server clusters list displays only failover clusters. * Log ingestion must be enabled for each MID Server in the cluster. If log ingestion is not enabled for the active MID Server, Health Log Analytics enables it automatically. * The default maximum number of data inputs or integrations streaming logs to a single MID Server is 10. A cluster passes capacity validation if it contains at least one MID Server with fewer than 10 data inputs or integrations running on it. This is true even when that MID Server is down. {#il-connector-hla-azure-la-fields__ul_htt_wdq_dwb} For more information about MID Server clusters, see [Configure a MID Server cluster](https://www.servicenow.com/docs/access?context=t_ConfigureAMIDServerCluster&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). | | Service instance | The service instance (formerly the application service) to which to bind the log data. This field is required. | | Data source | The source of the log data that the integration pulls to your ServiceNow instance: Azure Log Analytics. This field is read-only. | | Description | Option to add a brief description of the integration to help identify it. | [Table 1. Provide details] {#il-connector-hla-azure-la-fields__table_pxx_hz1_42c} {#il-connector-hla-azure-la-fields__table_gpq_jz1_42c__entry__2} | Field | Description | |-|-| | Redirect url | The redirect URL of the access log application. This field is required. The URL refers to the Microsoft Azure redirect_uri authorization property. For more information, see the Authorization code URL (GET request) section in the [Microsoft Azure documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/logs/api/access-api). | | Authentication method | The credentials used to access Microsoft Azure resources. This field is required. If no credentials exist, select Create new Azure Service Principal credential. Create a credential by filling in the fields and then selecting Submit. For information on the Tenant ID, Client ID, and Secret key fields, refer to the [Microsoft Azure documentation](https://learn.microsoft.com/en-us/azure/?product=popular). When you have created a credential, you can select it from the drop-down list. | | Workspace ID | The Customer ID used to call the Microsoft Azure Log Analytics REST API. This field is required. | | Table name | The name of the table in Microsoft Azure Log Analytics where the data input fetches the log data. For more information, see the View table information section in the [Microsoft Azure documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/logs/log-analytics-tutorial). This field is required. | | Event time property name | The Microsoft Azure Log Analytics field in which to detect the event time. This field is required. | [Table 2. Set data retrieval method] {#il-connector-hla-azure-la-fields__table_gpq_jz1_42c} {#il-connector-hla-azure-la-fields__table_cyy_kz1_42c__entry__2} | Field | Description | |-|-| | Event Processor workers | The number of concurrent event processing workers, where each worker processes a batch of events independently. | | Workers queue size | The queue size of the Event Processor workers. | | Sub sample drop ratio | The number of events to batch together, out of which one will be discarded. This setting is used to reduce the number of fetched events. | | Sub sample receive ratio | The number of events to batch together, out of which all but one will be discarded. This setting is used to decrease the number of received events. | | Max documents per query | The highest number of rows retrieved in each query. | | Columns to select | Comma-separated list of column names to return. Note: This field is ignored when you provide a custom query. | | Character encoding | The character encoding for this data input. | | Sleep interval (seconds) | The interval, in seconds, to wait before querying again after a query has returned no events. | | Polling interval | The interval, in seconds, to wait before polling for new events. | | Drop if queue is full | Option to discard logs if there is a load on the MID Server. | | Log Query | Option to define your own Log Analytics query. This field overrides the values configured in the other query settings fields. Note: If this field is empty, Health Log Analytics generates the query using the values set in the other fields. For your custom query, use the following JSON format: `{"query": "query | where TimeGenerated > %s | take 500"}` For example: { "query":"ContainerLog | where LogEntry contains 'cartservice' | where TimeGenerated > %s | take 500", "workspaces": ["defaultworkspace-3ab145ff-f9cd-433f-8533-d1b1ee24aee6-eus"], "project": ["TimeGenerated", "LogEntry", "LogEntrySource"] } | [Table 3. Advanced settings] {#il-connector-hla-azure-la-fields__table_cyy_kz1_42c}