Microsoft Defender XDR

Bring Microsoft Defender XDR incidents into the security signal inbox, where a person decides what becomes an Aegis incident.

At a glance

Direction Into Aegis.
What it brings in Defender XDR incidents, with their related alerts grouped. A connection authorised before SecurityIncident.Read.All was granted falls back to single alerts and asks you to re-authorise.
Where it lands The security signal inbox (/incidents/signals). A sync never creates an incident: a reviewer accepts, merges or dismisses each signal (see Incidents).
Credentials and permissions An app registration in your Microsoft Entra ID tenant with the delegated Microsoft Graph permissions SecurityAlert.Read.All, SecurityIncident.Read.All and User.Read and admin consent, then Authorize with Microsoft.
Owner of imported records A signal has no owner. The incident created when a reviewer accepts it belongs to that reviewer.
When it runs On demand with the sync button, or on a schedule under Sync Settings (see Connectors).
Set it up /connectors/azure, by people allowed to configure connectors (Manager or above), on a plan that includes the connector.

Who uses it

The page opens for Manager and Admin users. A Contributor or Viewer who opens /connectors/azure is sent to the /unauthorized page. Saving, authorising and syncing also need the connector permission, the Microsoft Defender XDR module switched on for your organisation, and a licence that includes the connector; without them the action is refused.

What's on this screen

No screenshot of this page was captured for this edition of the guide. The page reads from top to bottom in this order:

Connect Defender XDR

  1. In Microsoft Entra ID, create an app registration, add the delegated permissions SecurityAlert.Read.All and SecurityIncident.Read.All (the permissions box in Aegis also lists User.Read, for sign-in), grant admin consent, and add a client secret. Copy the secret straight away; Microsoft shows it only once.
  2. Under the app's Web platform, add the redirect URI shown in Setup Instructions, exactly as shown. If Microsoft later reports AADSTS50011 or AADSTS900971, the URI is missing, registered under another platform, or differs by a character.
  3. In Aegis, enter the Client ID, Client Secret and Tenant ID, then select Save Configuration. Leave the tenant as common only for a multi-tenant app; a single-tenant app needs your organisation's tenant ID. Connection Status then asks for OAuth authorisation.
  4. Select Authorize with Microsoft. Microsoft's sign-in and consent page opens; after you agree you return to the connector page with a banner reporting the outcome.
  5. Select Test Connection. On success the panel shows the recent alert count, and Security Alert Sync appears below it.

Run a sync

  1. In Security Alert Sync, tick the severities to bring in: High, Medium, Low and Informational. Only High is ticked when the page opens, and Sync Now stays disabled while no severity is ticked.
  2. Select Sync Now. The button reads as syncing and a progress line appears while Aegis reads from Microsoft.
  3. Read the result under Sync Complete: how many new signals reached the inbox, how many were already known, and how many items matched your severities out of all those read. The line calls these items alerts, even when the connection reads grouped incidents. If the connection still runs on single alerts, the line also asks you to re-authorise. A failed sync shows Sync Failed with the error instead.
  4. Select Review in the security signal inbox to open /incidents/signals and decide each signal.

Once the connector has synced, the sync history shows Last successful sync: with the date and time of the last completed sync, and it still does after a reload. Only a connector that has never synced reads No sync history yet. The list of individual runs is kept for this visit only; the audit log records every sync.

How signals are filled in

Tips and limits

Where this connects

The shared Microsoft setup steps are in Connectors; the inbox is described in Incidents. Accepted and merged signals are recorded in Evidence.