--- title: "Azure Monitor" slug: "azure-monitor" updated: 2026-09-18T12:24:44Z published: 2026-09-18T12:24:44Z canonical: "docs.turbo360.com/azure-monitor" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.turbo360.com/llms.txt > Use this file to discover all available pages before exploring further. # Azure Monitor ## Overview Azure Monitor (formerly Operations Management Suite (OMS)) is a cloud-based IT management solution from Microsoft. It helps organizations manage and protect both on-premises and cloud infrastructure by collecting, analyzing, and acting on telemetry data from a variety of sources. Turbo360 integrates with Azure Monitor as a notification channel. When an alert fires, Turbo360 forwards the alert data to a Log Analytics workspace in Azure Monitor, where it is stored as a custom log record. Your team can then query and analyze these records alongside other infrastructure telemetry. ### Business value Routing Turbo360 alerts to Azure Monitor centralizes your operational data. Teams that already use Log Analytics for infrastructure monitoring gain a unified view of platform health, integration failures, and alert history without switching between tools. ## Prerequisites - An active Azure Monitor Log Analytics workspace - The Workspace ID and a primary or secondary shared key from the workspace - A Turbo360 account with notification channel configuration access ### Required permissions You must have permission to manage notification channels in Turbo360. In Azure Monitor, the shared key must belong to a Log Analytics workspace you have access to. ### Dependencies - The Log Analytics workspace must be active and accepting data ingestion - The shared key must be valid and not expired ## How it works When you configure an Azure Monitor notification channel in Turbo360, you provide the Workspace ID and shared key of a Log Analytics workspace. Turbo360 uses these credentials to authenticate with the Log Analytics Data Collector API. When a Turbo360 alert triggers, it submits a log record to the workspace using the log type you specify. The record appears in Log Analytics as a custom log entry, where it can be queried using Kusto Query Language (KQL) alongside other workspace data. ## Steps Use the following steps to configure an Azure Monitor notification channel. Navigate to **Settings > Notification channels** and select **Azure Monitor** to get started. 1. Enter a **Friendly name** for the Azure Monitor notification channel. 2. Enter the data submission record type in the **Log type** field. This value determines how the log record is categorized in Log Analytics. 3. Enter the **Workspace Id** of your Log Analytics workspace. 4. Enter the primary or secondary key from your Log Analytics workspace in the **Shared key** field. 5. Click **Validate**. Turbo360 sends a sample notification to the provided workspace to verify that the credentials are valid. 6. Click **Save** to complete the setup. Note: You can find your Workspace ID and shared key in the **Agents management** section of your Log Analytics workspace in the Azure portal. See [Obtaining shared key and workspace Id](https://learn.microsoft.com/en-us/azure/azure-monitor/agents/agent-windows?tabs=setup-wizard#requirements) for details. ## Configuration | Option | Type | Required | Description | | --- | --- | --- | --- | | Friendly name | Text | Yes | Display name for this notification channel in Turbo360 | | Log type | Text | Yes | The custom log record type used to categorize alert data in Log Analytics | | Workspace Id | Text | Yes | The unique identifier of your Log Analytics workspace | | Shared key | Text | Yes | The primary or secondary key used to authenticate with the Log Analytics Data Collector API | ## Permission behavior **With access:** You can create and save Azure Monitor notification channels, validate credentials, and assign channels to alert rules. **Without access:** The notification channel configuration section is not available. Contact your Turbo360 administrator to request the necessary permissions. ## Example scenario Your team monitors Azure integration workflows using Turbo360. You configure an Azure Monitor notification channel pointing to a Log Analytics workspace named **IntegrationOps**, with **Log type** set to `Turbo360Alerts`. When a Turbo360 alert fires, a custom log record is written to the workspace under the `Turbo360Alerts_CL` table. Your team queries this table in Log Analytics to review alert history and correlate it with other infrastructure events. ## Limitations - Turbo360 writes log records to Azure Monitor but does not read from it. Alert resolution or acknowledgment must be handled in Turbo360. - The log type value you enter becomes the custom table name in Log Analytics with a `_CL` suffix appended by Azure Monitor. Choose a value that is meaningful for querying. - Shared keys do not expire automatically, but rotating them in Azure requires updating the channel configuration in Turbo360 manually. ## Troubleshooting 1. **Validation fails after entering credentials** Cause: The Workspace ID or shared key may be incorrect, or the Log Analytics workspace may be inactive. Fix: Verify the Workspace ID and shared key in the **Agents management** section of your Log Analytics workspace. Confirm the workspace is active and not in a deleted or disabled state. 2. **Log records do not appear in Log Analytics after an alert fires** Cause: The notification channel may not be assigned to the alert rule, or there may be an ingestion delay in Azure Monitor. Fix: Verify the Azure Monitor channel is selected in the alert rule's notification settings. Azure Monitor can take up to 5–10 minutes to index newly ingested custom log data; check again after a short wait. 3. **Sample notification succeeds but no data appears for the custom log type** Cause: The custom log table (`<LogType>_CL`) may not yet exist in Log Analytics if no prior data has been ingested. Fix: After the first successful validation, allow a few minutes for the table to be created. Search for the table using the Log type name with the `_CL` suffix in the Log Analytics query editor. 4. **Log type name is not accepted during configuration** Cause: Azure Monitor imposes naming restrictions on custom log types. Names may only contain letters, numbers, and underscores, and must not begin with a number. Fix: Update the **Log type** value to use only letters, numbers, and underscores. 5. **Credentials were valid but alerts have stopped arriving in Log Analytics** Cause: The shared key may have been rotated in Azure without updating the channel in Turbo360. Fix: Retrieve the current primary or secondary key from the **Agents management** section of the workspace, update the **Shared key** field in Turbo360, and re-validate the channel. ## FAQs 1. **Where do I find the Workspace ID and shared key?** In the Azure portal, open your Log Analytics workspace and go to **Settings > Agents management**. The Workspace ID and both the primary and secondary keys are displayed there. 2. **Can I use the secondary key instead of the primary key?** Yes. Turbo360 accepts either the primary or secondary shared key. Using the secondary key lets you rotate the primary key without interrupting alert delivery. 3. **What does the `_CL` suffix mean on my log table?** Azure Monitor automatically appends `_CL` (Custom Log) to the log type name you provide. If you set **Log type** to `Turbo360Alerts`, the table in Log Analytics will be named `Turbo360Alerts_CL`. 4. **Can I send alerts from multiple Turbo360 alert rules to the same workspace?** Yes. Azure Monitor is configured globally within Turbo360, enabling it to receive notifications for all supported alerts. ## Related articles - [Obtaining shared key and workspace Id](https://learn.microsoft.com/en-us/azure/azure-monitor/agents/agent-windows?tabs=setup-wizard#requirements)