Skip to content

Connectors · MSP & PSA

Azure Log Analytics MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Azure Log Analytics and the rest of your systems. It gives your agent 94 Azure Log Analytics actions (50 reads, 25 writes and 19 that wait for a confirmation) and holds the Azure Log Analytics credential itself, so the agent never does. It paces Azure Log Analytics's limits and records every call.

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "azure_log_analytics.operations.list",  intent: "check which Azure Log Analytics account is connected"}# Lists all of the available OperationalInsights Rest API operations · read · 1 upstream call
  • 94actionsin one signed file
  • 50readlook, never change
  • 25writecreate and update
  • 19wait for a yesdestructive, confirmed first

Set up

Connect Azure Log Analytics in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Azure Log Analytics.

    OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in. actionlake stores what you paste write-only, sealed under your tenant's key.

    • client_idEntra application (client) id of a service principal with Log Analytics Reader (or Contributor) on the workspace
    • client_secretEntra client secret
    • tenant_idYour Azure Log Analytics tenant id
    • token_audienceYour Azure Log Analytics token audience
    account { op: "connections.requirements", service: "azure_log_analytics" }
    # free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "azure_log_analytics.operations.list" }# lists all of the available operationalinsights rest api operations · read · 1 upstream callcheck { action: "azure_log_analytics.query_pack_queries.update", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Azure Log Analytics at a glance

Sign-in
OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in.
You provide
client_idclient_secret
Setup fields
tenant_idtoken_audience
Limits we pace to
200 calls a minute, per connection
API covered
Microsoft.OperationalInsights Resource Manager and Log Analytics query API: specification/operationalinsights/resource-manager/Microsoft.OperationalInsights/OperationalInsights/stable/2026-03-01/openapi.json (2026-03-01), specification/monitor/data-plane/OperationalInsights/stable/v1/OperationalInsights.json (v1)management.azure.com
Built from
Azure Log Analytics's documentation, read 23 October 2026OpenAPI spec (GitHub)OpenAPI spec (GitHub)learn.microsoft.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
43 of 50 reads, for up to 5 minutes; a write clears what it affects
Shared entities
1, so ask can line Azure Log Analytics up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Azure Log Analytics.

94 actions in 27 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 50readlook, never change
  • 25writecreate and update
  • 19destructivewait for a confirmation
  1. Workspaces

    11

    5 read · 3 write · 3 destructive

    Gets the workspaces in a subscription · Gets workspaces in a resource group · Gets a list of NSP configurations for specified workspace · Gets a workspace instance

  2. Query packs

    7

    3 read · 3 write · 1 destructive

    Gets a list of all Log Analytics QueryPacks within a subscription · Gets a list of Log Analytics QueryPacks within a resource group · Returns a Log Analytics QueryPack · Creates a Log Analytics QueryPack

  3. Summary logs

    7

    2 read · 4 write · 1 destructive

    Gets all summary rules for the specified Log Analytics workspace · Gets Log Analytics workspace Summary rules · Retries a failed Summary rule bin · Starts an inactive Summary rule

  4. Tables

    7

    2 read · 3 write · 2 destructive

    Gets all the tables for the specified Log Analytics workspace · Gets a Log Analytics workspace table · Migrate a Log Analytics table from support of the Data Collector API and Custom Fields features to support of Data Collection Rule-based Custom Logs · Update a Log Analytics workspace table

  5. Clusters

    6

    3 read · 2 write · 1 destructive

    Gets the Log Analytics clusters in a subscription · Gets Log Analytics clusters in a resource group · Gets a Log Analytics cluster instance · Updates a Log Analytics cluster

  6. Query pack queries

    6

    3 read · 2 write · 1 destructive

    Gets a list of Queries defined within a Log Analytics QueryPack · Gets a specific Log Analytics Query defined within a Log Analytics QueryPack · Adds or Updates a specific Query within a Log Analytics QueryPack · Deletes a specific Query defined within an Log Analytics QueryPack

  7. Query

    5

    5 read · 0 write · 0 destructive

    Execute an Analytics query · Execute a batch of Analytics queries · Execute an Analytics query using resource ID · Execute an Analytics query

  8. Data exports

    4

    2 read · 1 write · 1 destructive

    Lists the data export instances within a workspace · Gets a data export instance · Deletes the specified data export in a given workspace · Create or update a data export

19 more areas · 41 actions
  • Data sources 4
  • Linked services 4
  • Linked storage accounts 4
  • Saved searches 4
  • Storage insight configs 4
  • Intelligence packs 3
  • Workspace purge 3
  • Deleted workspaces 2
  • Metadata 2
  • Shared keys 2
  • Available service tiers 1
  • Gateways 1
  • Management groups 1
  • Operation statuses 1
  • Operations 1
  • Resource groups 1
  • Schema 1
  • Subscriptions 1
  • Usages 1

Top actions

The Azure Log Analytics API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 10 of Azure Log Analytics's 12 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
azure_log_analytics.query_pack_queries.listGets a list of Queries defined within a Log Analytics QueryPackGets a list of Queries defined within a Log Analytics QueryPack.readanalytics.saved_query.list10 connectors
azure_log_analytics.resource_groups.listList the resource groups in a subscriptionList the resource groups in a subscription.readinfra.resource_group.list19 connectors
azure_log_analytics.query_pack_queries.getGets a specific Log Analytics Query defined within a Log Analytics QueryPackGets a specific Log Analytics Query defined within a Log Analytics QueryPack.readanalytics.saved_query.get9 connectors
azure_log_analytics.query_pack_queries.updateAdds or Updates a specific Query within a Log Analytics QueryPackAdds or Updates a specific Query within a Log Analytics QueryPack.writeanalytics.saved_query.update9 connectors
azure_log_analytics.tables.list_by_workspaceGets all the tables for the specified Log Analytics workspaceGets all the tables for the specified Log Analytics workspace.readthis connector
azure_log_analytics.query_pack_queries.deleteDeletes a specific Query defined within an Log Analytics QueryPackDeletes a specific Query defined within an Log Analytics QueryPack.destructiveanalytics.saved_query.delete10 connectors
azure_log_analytics.query.executeExecute an Analytics queryExecute an Analytics query.readanalytics.query_result.query2 connectors
azure_log_analytics.saved_searches.list_by_workspaceGets the saved searches for a given Log Analytics WorkspaceGets the saved searches for a given Log Analytics Workspace.readplatform.saved_search.list16 connectors
azure_log_analytics.usages.listGets a list of usage metrics for a workspaceGets a list of usage metrics for a workspace.readthis connector
azure_log_analytics.clusters.listGets the Log Analytics clusters in a subscriptionGets the Log Analytics clusters in a subscription.readthis connector
azure_log_analytics.query_pack_queries.putAdds or Updates a specific Query within a Log Analytics QueryPackAdds or Updates a specific Query within a Log Analytics QueryPack.writeanalytics.saved_query.upsert2 connectors
azure_log_analytics.query_packs.create_without_nameCreates a Log Analytics QueryPackCreates a Log Analytics QueryPack.writethis connector

Try it

Prompts to paste into Claude.

Each one names the Azure Log Analytics actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Lists all of the available OperationalInsights Rest API operations in Azure Log Analytics and tell me what stands out.

    callsazure_log_analytics.operations.list

  2. Writewrite

    Adds or Updates a specific Query within a Log Analytics QueryPack in Azure Log Analytics. Show me exactly what you will send before you save it.

    callsazure_log_analytics.query_pack_queries.update

Governance for Azure Log Analytics

Destructive actions wait for a yes.

19 Azure Log Analytics actions are destructive. These are all of them:

  • Deletes a specific Query defined within an Log Analytics QueryPackazure_log_analytics.query_pack_queries.delete
  • Deletes the specified saved search in a given workspaceazure_log_analytics.saved_searches.delete
  • Deactivates failover for the specified workspaceazure_log_analytics.workspaces.failback
  • Activates failover for the specified workspaceazure_log_analytics.workspaces.failover
  • Regenerates the shared keys for a Log Analytics Workspaceazure_log_analytics.shared_keys.regenerate
  • Delete a Log Analytics workspace tableazure_log_analytics.tables.delete
  • Deletes a cluster instanceazure_log_analytics.clusters.delete
  • Delete a Log Analytics gatewayazure_log_analytics.gateways.delete
  • Deletes a workspace resourceazure_log_analytics.workspaces.delete
  • Deletes a Log Analytics QueryPackazure_log_analytics.query_packs.delete
  • Deletes the specified data export in a given workspaceazure_log_analytics.data_exports.delete
  • Deletes a data source instanceazure_log_analytics.data_sources.delete
  • Deletes Log Analytics workspace Summary rulesazure_log_analytics.summary_logs.delete
  • Purges data in an Log Analytics workspace by a set of user-defined filtersazure_log_analytics.workspace_purge.purge
  • Deletes a linked service instanceazure_log_analytics.linked_services.delete
  • Deletes all linked storage accounts of a specific data source type associated with the specified workspaceazure_log_analytics.linked_storage_accounts.delete
  • Deletes a storageInsightsConfigs resourceazure_log_analytics.storage_insight_configs.delete
  • Purges data lake data in a Log Analytics workspace for a table over a specified time rangeazure_log_analytics.workspace_purge.purge_lake_data
  • Cancel a log analytics workspace search results table query runazure_log_analytics.tables.cancel_search

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

doazure_log_analytics.query_pack_queries.deleteconfirm_policy: human

Deletes a specific Query defined within an Log Analytics QueryPack?

intent: the user asked me to deletes a specific Query defined within an Log Analytics QueryPack

run suspended · waiting for a named person · key azure-log-analytics-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "azure-log-analytics-agent",  allowed_actions: ["azure_log_analytics.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "azure_log_analytics.query_pack_queries.delete", approver: "[email protected]" },    { match: "azure_log_analytics.saved_searches.delete", approver: "[email protected]" },    { match: "azure_log_analytics.workspaces.failback", approver: "[email protected]" }  ]}
Illustrative. Scoped to Azure Log Analytics only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Azure Log Analytics costs on actionlake.

Every Azure Log Analytics action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Azure Log Analytics refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 94 Azure Log Analytics actions
  • 22actions pageeach page of a long list is one call
  • 43reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Azure Log Analytics action.

94 actions by area: the id your agent calls, what it does, and its effect.

Workspaces11
  • azure_log_analytics.workspaces.create_or_updateCreate or update a workspacewrite
  • azure_log_analytics.workspaces.deleteDeletes a workspace resourcedestructive
  • azure_log_analytics.workspaces.failbackDeactivates failover for the specified workspacedestructive
  • azure_log_analytics.workspaces.failoverActivates failover for the specified workspacedestructive
  • azure_log_analytics.workspaces.getGets a workspace instanceread
  • azure_log_analytics.workspaces.get_network_security_perimeter_configurationGets a network security perimeter configurationread
  • azure_log_analytics.workspaces.listGets the workspaces in a subscriptionread
  • azure_log_analytics.workspaces.list_by_resource_groupGets workspaces in a resource groupread
  • azure_log_analytics.workspaces.list_network_security_perimeter_configurationsGets a list of NSP configurations for specified workspaceread
  • azure_log_analytics.workspaces.reconcile_network_security_perimeter_configurationReconcile network security perimeter configuration for Workspace resourcewrite
  • azure_log_analytics.workspaces.updateUpdates a workspacewrite
Query packs7
  • azure_log_analytics.query_packs.create_or_updateCreates (or updates) a Log Analytics QueryPackwrite
  • azure_log_analytics.query_packs.create_without_nameCreates a Log Analytics QueryPackwrite
  • azure_log_analytics.query_packs.deleteDeletes a Log Analytics QueryPackdestructive
  • azure_log_analytics.query_packs.getReturns a Log Analytics QueryPackread
  • azure_log_analytics.query_packs.listGets a list of all Log Analytics QueryPacks within a subscriptionread
  • azure_log_analytics.query_packs.list_by_resource_groupGets a list of Log Analytics QueryPacks within a resource groupread
  • azure_log_analytics.query_packs.update_tagsUpdates an existing QueryPack's tagswrite
Summary logs7
  • azure_log_analytics.summary_logs.create_or_updateCreates or updates Log Analytics workspace Summary ruleswrite
  • azure_log_analytics.summary_logs.deleteDeletes Log Analytics workspace Summary rulesdestructive
  • azure_log_analytics.summary_logs.getGets Log Analytics workspace Summary rulesread
  • azure_log_analytics.summary_logs.list_by_workspaceGets all summary rules for the specified Log Analytics workspaceread
  • azure_log_analytics.summary_logs.retry_binRetries a failed Summary rule binwrite
  • azure_log_analytics.summary_logs.startStarts an inactive Summary rulewrite
  • azure_log_analytics.summary_logs.stopStops an active Summary rulewrite
Tables7
  • azure_log_analytics.tables.cancel_searchCancel a log analytics workspace search results table query rundestructive
  • azure_log_analytics.tables.create_or_updateUpdate or Create a Log Analytics workspace tablewrite
  • azure_log_analytics.tables.deleteDelete a Log Analytics workspace tabledestructive
  • azure_log_analytics.tables.getGets a Log Analytics workspace tableread
  • azure_log_analytics.tables.list_by_workspaceGets all the tables for the specified Log Analytics workspaceread
  • azure_log_analytics.tables.migrateMigrate a Log Analytics table from support of the Data Collector API and Custom Fields features to support of Data Collection Rule-based Custom Logswrite
  • azure_log_analytics.tables.updateUpdate a Log Analytics workspace tablewrite
Clusters6
  • azure_log_analytics.clusters.create_or_updateCreate or update a Log Analytics clusterwrite
  • azure_log_analytics.clusters.deleteDeletes a cluster instancedestructive
  • azure_log_analytics.clusters.getGets a Log Analytics cluster instanceread
  • azure_log_analytics.clusters.listGets the Log Analytics clusters in a subscriptionread
  • azure_log_analytics.clusters.list_by_resource_groupGets Log Analytics clusters in a resource groupread
  • azure_log_analytics.clusters.updateUpdates a Log Analytics clusterwrite
Query pack queries6
  • azure_log_analytics.query_pack_queries.deleteDeletes a specific Query defined within an Log Analytics QueryPackdestructive
  • azure_log_analytics.query_pack_queries.getGets a specific Log Analytics Query defined within a Log Analytics QueryPackread
  • azure_log_analytics.query_pack_queries.listGets a list of Queries defined within a Log Analytics QueryPackread
  • azure_log_analytics.query_pack_queries.putAdds or Updates a specific Query within a Log Analytics QueryPackwrite
  • azure_log_analytics.query_pack_queries.searchSearch a list of Queries defined within a Log Analytics QueryPack according to given search propertiesread
  • azure_log_analytics.query_pack_queries.updateAdds or Updates a specific Query within a Log Analytics QueryPackwrite
Query5
  • azure_log_analytics.query.batchExecute a batch of Analytics queriesread
  • azure_log_analytics.query.executeExecute an Analytics queryread
  • azure_log_analytics.query.execute_for_resourceExecute an Analytics query using resource IDread
  • azure_log_analytics.query.getExecute an Analytics queryread
  • azure_log_analytics.query.get_for_resourceExecute an Analytics query using resource URIread
Data exports4
  • azure_log_analytics.data_exports.create_or_updateCreate or update a data exportwrite
  • azure_log_analytics.data_exports.deleteDeletes the specified data export in a given workspacedestructive
  • azure_log_analytics.data_exports.getGets a data export instanceread
  • azure_log_analytics.data_exports.list_by_workspaceLists the data export instances within a workspaceread
Data sources4
  • azure_log_analytics.data_sources.create_or_updateCreate or update a data sourcewrite
  • azure_log_analytics.data_sources.deleteDeletes a data source instancedestructive
  • azure_log_analytics.data_sources.getGets a datasource instanceread
  • azure_log_analytics.data_sources.list_by_workspaceGets the first page of data source instances in a workspace with the link to the next pageread
Linked services4
  • azure_log_analytics.linked_services.create_or_updateCreate or update a linked servicewrite
  • azure_log_analytics.linked_services.deleteDeletes a linked service instancedestructive
  • azure_log_analytics.linked_services.getGets a linked service instanceread
  • azure_log_analytics.linked_services.list_by_workspaceGets the linked services instances in a workspaceread
Linked storage accounts4
  • azure_log_analytics.linked_storage_accounts.create_or_updateCreate or Update a link relation between current workspace and a group of storage accounts of a specific data source typewrite
  • azure_log_analytics.linked_storage_accounts.deleteDeletes all linked storage accounts of a specific data source type associated with the specified workspacedestructive
  • azure_log_analytics.linked_storage_accounts.getGets all linked storage account of a specific data source type associated with the specified workspaceread
  • azure_log_analytics.linked_storage_accounts.list_by_workspaceGets all linked storage accounts associated with the specified workspace, storage accounts will be sorted by their data source typeread
Saved searches4
  • azure_log_analytics.saved_searches.create_or_updateCreates or updates a saved search for a given workspacewrite
  • azure_log_analytics.saved_searches.deleteDeletes the specified saved search in a given workspacedestructive
  • azure_log_analytics.saved_searches.getGets the specified saved search for a given workspaceread
  • azure_log_analytics.saved_searches.list_by_workspaceGets the saved searches for a given Log Analytics Workspaceread
Storage insight configs4
  • azure_log_analytics.storage_insight_configs.create_or_updateCreate or update a storage insightwrite
  • azure_log_analytics.storage_insight_configs.deleteDeletes a storageInsightsConfigs resourcedestructive
  • azure_log_analytics.storage_insight_configs.getGets a storage insight instanceread
  • azure_log_analytics.storage_insight_configs.list_by_workspaceLists the storage insight instances within a workspaceread
Intelligence packs3
  • azure_log_analytics.intelligence_packs.disableDisables an intelligence pack for a given workspacewrite
  • azure_log_analytics.intelligence_packs.enableEnables an intelligence pack for a given workspacewrite
  • azure_log_analytics.intelligence_packs.listLists all the intelligence packs possible and whether they are enabled or disabled for a given workspaceread
Workspace purge3
  • azure_log_analytics.workspace_purge.get_purge_statusGets status of an ongoing purge operationread
  • azure_log_analytics.workspace_purge.purgePurges data in an Log Analytics workspace by a set of user-defined filtersdestructive
  • azure_log_analytics.workspace_purge.purge_lake_dataPurges data lake data in a Log Analytics workspace for a table over a specified time rangedestructive
Deleted workspaces2
  • azure_log_analytics.deleted_workspaces.listGets recently deleted workspaces in a subscription, available for recoveryread
  • azure_log_analytics.deleted_workspaces.list_by_resource_groupGets recently deleted workspaces in a resource group, available for recoveryread
Metadata2
  • azure_log_analytics.metadata.getGets metadata informationread
  • azure_log_analytics.metadata.get_via_postGets metadata informationread
Shared keys2
  • azure_log_analytics.shared_keys.getGets the shared keys for a workspaceread
  • azure_log_analytics.shared_keys.regenerateRegenerates the shared keys for a Log Analytics Workspacedestructive
Available service tiers1
  • azure_log_analytics.available_service_tiers.list_by_workspaceGets the available service tiers for the workspaceread
Gateways1
  • azure_log_analytics.gateways.deleteDelete a Log Analytics gatewaydestructive
Management groups1
  • azure_log_analytics.management_groups.listGets a list of management groups connected to a workspaceread
Operation statuses1
  • azure_log_analytics.operation_statuses.getGet the status of a long running azure asynchronous operationread
Operations1
  • azure_log_analytics.operations.listLists all of the available OperationalInsights Rest API operationsread
Resource groups1
  • azure_log_analytics.resource_groups.listList the resource groups in a subscriptionread
Schema1
  • azure_log_analytics.schema.getGets the schema for a given workspaceread
Subscriptions1
  • azure_log_analytics.subscriptions.listList the subscriptions the credential can seeread
Usages1
  • azure_log_analytics.usages.listGets a list of usage metrics for a workspaceread

Questions

The Azure Log Analytics MCP server, answered.

Is there an Azure Log Analytics MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 94 Azure Log Analytics actions across workspaces, query packs, summary logs and tables, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Azure Log Analytics.

What do I need to connect Azure Log Analytics?

Entra application (client) id of a service principal with Log Analytics Reader (or Contributor) on the workspace and Entra client secret. Plus your tenant id and your token audience. The free call account { op: "connections.requirements", service: "azure_log_analytics" } lists exactly what to paste.

Can an AI agent delete or change things in Azure Log Analytics?

Only if its key allows it, and only with an explicit confirmation. 19 Azure Log Analytics actions are destructive, including deletes a specific Query defined within an Log Analytics QueryPack, deletes the specified saved search in a given workspace and deactivates failover for the specified workspace. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Azure Log Analytics API limit?

actionlake paces every call to the limits in the Azure Log Analytics service file: 200 calls a minute per connection. Repeated reads are answered from cache (43 Azure Log Analytics actions can be), which never reaches Azure Log Analytics.

What does an Azure Log Analytics action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (22 Azure Log Analytics actions page). Cache hits, searches, dry runs and calls Azure Log Analytics refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Azure Log Analytics API does it cover?

The Microsoft.OperationalInsights Resource Manager and Log Analytics query API: specification/operationalinsights/resource-manager/Microsoft.OperationalInsights/OperationalInsights/stable/2026-03-01/openapi.json (2026-03-01), specification/monitor/data-plane/OperationalInsights/stable/v1/OperationalInsights.json (v1) at management.azure.com. It is built from Azure Log Analytics's documentation as read on 23 October 2026. 94 actions in 27 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Azure Log Analytics data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Azure Log Analytics credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent Azure Log Analytics today.

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.