Connect Azure

What you connect

You connect an Azure subscription so VerOps can read its Azure Monitor metrics. The recommended method is multi-tenant app + admin consent: you grant VerOps's application read-only monitoring access in your directory. You never share a client secret.

Prerequisites

• Permission to grant admin consent and assign roles in the target Azure subscription.
• Your Directory (tenant) ID and Subscription ID.
• The resource IDs you want metrics for (Phase 1 collects by resource id).

Steps — multi-tenant app + consent (recommended)

1. In VerOps, go to Manage → Cloud Integrations → Connect account and choose Microsoft Azure and Multi-tenant app + consent.
2. Use the consent link shown in the setup panel to grant admin consent to the VerOps application in your directory.
3. In the Azure portal, assign the Monitoring Reader role to the VerOps application (service principal) on the subscription or resource group you want read.
4. Back in VerOps, enter your Directory (tenant) ID, Subscription ID, and the Resource IDs to collect, then save.
5. Click Test connection. A green result means VerOps authenticated to your directory and could read metric definitions.

Finding a resource ID

A resource ID looks like this:

/subscriptions/<SUB_ID>/resourceGroups/<RG>/providers/Microsoft.Compute/virtualMachines/<VM_NAME>

In the Azure portal, open the resource → Properties → copy the Resource ID. Enter one or more, comma-separated.

Service Principal (fallback)

Prefer a dedicated app? Choose Service Principal, register an app in your directory, assign it Monitoring Reader, and give VerOps the tenant id, client id and a client secret. VerOps encrypts the secret at rest. The multi-tenant consent flow is recommended because it keeps no per-tenant secret on our side.

Note: Azure Monitor metrics are read per resource. Grant Monitoring Reader at the narrowest scope that covers the resources you care about — least privilege by default.