Skip to content
Integrations/Microsoft Azure (ARM)/Connection Guide
Connection Guide

Connect Microsoft Azure (ARM) Without Breaking the Audit Trail

Use this guide to connect Microsoft Azure (ARM) or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryCloud
Checklist3 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Microsoft Azure (ARM) and make sure the first collection lands cleanly.

  1. 1
    Register an app in Entra ID and grant it Azure RBAC Reader on each subscription.
  2. 2
    Store tenant_id, client_id, client_secret. Optionally set subscription_ids to restrict scope (CSV or list).
  3. 3
    Validate by listing subscriptions and checking Activity Log diagnostic settings.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

client_idclient_secret

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.