# Azure Monitor integrations: metrics

> Create or update a metric alert and create or update an action group in Azure Monitor. Connect Azure Monitor to the rest of your IT stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/azure-monitor-integrations/
**Categories:** IT
**Connects through:** HTTP Connector

## Overview

Azure Monitor is Microsoft's monitoring service for Azure resources, collecting metrics and activity logs and sending alerts through configurable action groups. Tray.ai connects to Azure Monitor through the HTTP Connector, so your workflows can call the Azure Monitor API alongside the rest of your stack.

## Use cases

### Metrics

Read metrics in Azure Monitor from any Tray.ai workflow. The Azure Monitor API covers calls such as list metric values for a resource and list metrics for a subscription.

- List metric values for a resource
- List metrics for a subscription

### Metric alerts

Read, create, update, and delete metric alerts in Azure Monitor from any Tray.ai workflow. The Azure Monitor API covers calls such as create or update a metric alert and get a metric alert.

- Create or update a metric alert
- Get a metric alert
- List metric alerts

### Action groups

Read, create, and delete action groups in Azure Monitor from any Tray.ai workflow. The Azure Monitor API covers calls such as create or update an action group and get an action group.

- Create or update an action group
- Get an action group
- List action groups

## Challenges Tray.ai solves

### Keeping Azure Monitor credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Azure Monitor credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Azure Monitor API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Azure Monitor API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Azure Monitor?

Yes. Tray.ai connects to Azure Monitor through the HTTP Connector, which calls the Azure Monitor API directly. Any call the Azure Monitor API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Azure Monitor?

The Azure Monitor API uses OAuth 2.0 and a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Azure Monitor connector?

Azure Monitor runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Azure Monitor connector from the Azure Monitor API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/