Integration

Azure Monitor integration

Azure Monitor through Azure Resource Manager. Read platform and custom metric time series for any Azure resource together with the metric definitions and namespaces that describe them, browse the subscription activity log, manage diagnostic settings that route logs and metrics to storage, event hubs or Log Analytics, and list action groups, metric alert rules, log alert rules, autoscale settings and currently fired alerts. Calls act as the signed-in Azure user and are subject to that user's role assignments.

Connect Azure Monitor How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Azure Monitor.Built from the 14 Azure Monitor tools below, on the connection you add once.

Common Azure Monitor use cases

reviewing which log queries are wired to alerting
finding out who changed a production resource and when
posting newly fired critical alerts into a chat channel
stopping log ingestion costs for a decommissioned resource
auditing which teams are notified by production alert rules
reading a setting before adding one more log category to it
charting request latency for an App Service over the last day
discovering the exact metric name to query for a resource type
pulling the full payload of an alert to enrich an incident ticket
turning on log collection for every new resource in a subscription

What you can do with Azure Monitor

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Diagnostic setting, 4 operations

create_or_update_diagnostic_settingCreate or update diagnostic settingPUTCreates or replaces a diagnostic setting on a resource.
delete_diagnostic_settingDelete diagnostic settingDELETERemoves a diagnostic setting from a resource.
get_diagnostic_settingGet diagnostic settingGETRetrieves a named diagnostic setting.
list_diagnostic_settingsList diagnostic settingsGETLists a resource's diagnostic settings.

Alert, 2 operations

get_fired_alertGet fired alertGETRetrieves a single fired alert.
list_fired_alertsList fired alertsGETLists fired alerts in a subscription.

Alert rule, 2 operations

list_metric_alertsList metric alertsGETLists the metric alert rules of a subscription.
list_scheduled_query_rulesList scheduled query rulesGETLists the log query alert rules of a subscription.

Action group, 1 operation

list_action_groupsList action groupsGETLists the action groups of a subscription.

Activity log, 1 operation

list_activity_log_eventsList activity log eventsGETReads subscription activity log events.

Autoscale setting, 1 operation

list_autoscale_settingsList autoscale settingsGETLists the autoscale settings of a subscription.

Metric, 1 operation

list_metric_valuesList metric valuesGETReads metric values for an Azure resource over a time window.

Metric definition, 1 operation

list_metric_definitionsList metric definitionsGETLists the metrics available for a resource.

Metric namespace, 1 operation

list_metric_namespacesList metric namespacesGETLists the metric namespaces available on a resource.

Use Azure Monitor from Claude Code, Cursor or Codex

Connect Azure Monitor in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Azure Monitor operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Azure Monitor

Create your workspace
Sign up free. Nothing to install.
Connect Azure Monitor once
Add your Azure Monitor connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Azure Monitor integration FAQ

What can you do with the Azure Monitor integration?

LiveContext exposes 14 operations on Azure Monitor, covering diagnostic setting, alert, alert rule and action group. Common uses include reviewing which log queries are wired to alerting, finding out who changed a production resource and when and posting newly fired critical alerts into a chat channel.