Azure

Azure: fields, the check Connect and verify runs, the tools the agent gets and the read gate, from the connector catalog.

How-to · Updated 2026-10-21 · Describes release 0.1.164

Generated from the connector catalog (scripts/docs_integration_stubs.py); the long form of every step is Connect a datasource.

Overview

Azure Resource Manager via the native azure_request tool. The app registration needs an ARM role assignment on the selected resource group or subscription: Access control (IAM) > Add role assignment > Reader (Graph admin consent alone still 403s every read). Writes approval-gated.

Connector type key azure, kind api, listed under Metrics, Cloud providers, Security findings, Cost / FinOps in the catalog.

Setup

Before you start

Installation

Prepare the credential on the vendor side first, scoped to reads: the platform's read gate is a floor, not a substitute for a read-only identity. The connect dialog's Connection guidance column names the vendor-side steps and the exact read permissions for this type.

Configuration

  1. Open Settings · Data in → Data sources and select Connect datasource.
  2. Under Type, choose Azure; the list groups the types by category.
  3. Under Authentication method, keep Keyless workload identity (recommended) or choose the option to use a client secret; the fields the form shows follow that choice, and the rest sit under Advanced connection settings.
  4. Enter a Connection name; the connected list shows it, and per-connection agent tools are named after it.
  5. Fill the fields in the table below.
  6. Optionally, open Optional · describe this environment and say in What should AIOps know about it? what this system is and what matters; the agent reads it as the connection's description.
  7. Under Use this connection for, choose Investigate only and select Connect and verify.

The form shows these fields, in this order; the API key column is the key to send through the REST API.

Field (portal label) API key Stored as
Subscription ID (scope for write access) subscription_id plain
Resource group (optional — limits the read check and approved-plan execution) resource_group plain; optional
Directory (tenant) ID tenant_id plain
App (client) ID client_id plain
Client secret client_secret secret, write-only; optional
Scope JSON (optional: {subscriptions: []}) scope plain; optional

The same connection through the API (POST /api/aiops/{tenant_id}/datasources, datasources.manage; secret fields go in secret_values, which are stored write-only and never echoed):

{
  "type_key": "azure",
  "name": "<name>",
  "description": "<what this is and what matters, for the agent>",
  "config": {
    "subscription_id": "<subscription id>",
    "resource_group": "<resource group>",
    "tenant_id": "<tenant id>",
    "client_id": "<client id>",
    "scope": "<scope>"
  },
  "secret_values": {
    "client_secret": "<client secret>"
  },
  "role": "read",
  "enabled": true
}

Validation

Connect and verify (and Test on the row) runs an Entra client-credentials token, then an ARM read of the configured resource group (or the subscription's resource-group list when none is set).

You should see a dialog titled <connection name> is connected with Connected — verified from the control plane (Connected — verified by your private-network agent when your agent ran the check). Test on the row later writes ok · Azure AD token acquired — ARM read verified for subscription resource-group list (resource group <name> in place of the list when one is set) into Last test. A green result proves the operation named in its detail and nothing more; Audit perms on the row reads what the credential can actually do where the vendor exposes that.

If something fails

The dialog shows Needs a fix, what to fix and the check's own detail; the row is saved either way. Select Edit, correct the field the detail names and save again, or select Retry once a cause outside the form (network, vendor-side permission) is fixed. The verdict strings Test can show (failed · SSRF guard: '<host>' resolves to non-public address …, failed · reachable but auth rejected (HTTP 401/403), failed · HTTP <code> <path>, failed · <field> not configured, failed · <ExceptionName>: …) and what to do about each are in Test a connection and read the failure, and every connection status word is in the status and error reference. A connected datasource the agent never uses is disabled, write-role, allow-listed to other pillars, or of a type platform staff disabled.

Data collected

What the agent gets from a read connection of this type:

Beside the agent tool, the connection runs account-wide jobs: estate inventory, platform checks, security findings sync and change capture, and on AWS also the hourly service map (Application Signals, X-Ray where Application Signals lists nothing) and built-in detection. false under a job's key switches it off: Jobs this connection runs.

An investigation refuses a write through any connection tool, whatever the credential allows (Investigation connections are read-only. This operation was not executed; prepare an incident change using a write connection and obtain approval.); a fix runs through a write-role connection after approval. The exact rule table is under The read/write gate in detail in Connections and remediation access.

Next steps