Skip to content
Connection Guide

Connect Microsoft Defender for Cloud Without Breaking the Audit Trail

Use this guide to connect Microsoft Defender for Cloud 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 Security
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 Defender for Cloud and make sure the first collection lands cleanly.

  1. 1
    Register an Entra ID application and grant Security Reader on each in-scope subscription.
  2. 2
    Add Azure Reader only when Aurora must resolve underlying ARM resource metadata for cloud.resource coverage.
  3. 3
    Store tenant_id, client_id, client_secret, and subscription_ids; validate by listing subscriptions and reading Defender alerts and assessments.

Credentials and Secrets

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

client_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.