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:
-
A breadcrumb back to
Connectors, the titleMicrosoft Defender XDR Connectorand a one-line description. After you return from Microsoft, a banner here reports whether authorisation succeeded or failed. -
Configuration: a box listing the required delegated permissions, then theClient ID(required),Client SecretandTenant IDfields, andSave Configuration. -
Connection Status: a coloured dot with the status in words, any error text, and the buttons the current state allows (Authorize with Microsoft, orTest ConnectionandRe-authorize). When the test succeeds it showsConnected to Azure Security API, the number of recent alerts found and a count per severity. -
Security Alert Sync: shown only once the connection test has succeeded. It holds the severity checkboxes,Sync Now, the results of syncs run in this session and the linkReview in the security signal inbox. -
Setup Instructions: seven numbered steps, including the exact redirect URI to register in Microsoft Entra ID. -
Supported Alert Types: the incident types a signal can be given —Malware,Phishing,Unauthorized Access,Data Breach,Denial of ServiceandOther.
Connect Defender XDR
-
In Microsoft Entra ID, create an app registration, add the delegated
permissions
SecurityAlert.Read.AllandSecurityIncident.Read.All(the permissions box in Aegis also listsUser.Read, for sign-in), grant admin consent, and add a client secret. Copy the secret straight away; Microsoft shows it only once. -
Under the app's
Webplatform, add the redirect URI shown inSetup Instructions, exactly as shown. If Microsoft later reportsAADSTS50011orAADSTS900971, the URI is missing, registered under another platform, or differs by a character. -
In Aegis, enter the
Client ID,Client SecretandTenant ID, then selectSave Configuration. Leave the tenant ascommononly for a multi-tenant app; a single-tenant app needs your organisation's tenant ID.Connection Statusthen asks for OAuth authorisation. -
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. -
Select
Test Connection. On success the panel shows the recent alert count, andSecurity Alert Syncappears below it.
Run a sync
-
In
Security Alert Sync, tick the severities to bring in:High,Medium,LowandInformational. OnlyHighis ticked when the page opens, andSync Nowstays disabled while no severity is ticked. -
Select
Sync Now. The button reads as syncing and a progress line appears while Aegis reads from Microsoft. -
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 showsSync Failedwith the error instead. -
Select
Review in the security signal inboxto open/incidents/signalsand 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
- A signal takes the Defender incident's own title, description, severity and detection time. Its type and affected systems come from the incident's alerts.
-
The type follows Defender's
determinationwhen it names one (phishing, malware, unwanted software, compromised account). A Defender for Office 365 email alert filed under initial access counts as phishing. Otherwise the alert category decides, and anything unrecognised becomesOther. - Affected systems list device names, user accounts and cloud applications from the alert evidence, up to ten per signal.
- A signal is flagged as a possible data breach when an alert's category or description points to exfiltration, data loss or information disclosure.
Tips and limits
- Signals already in the inbox, or already imported as incidents, are not offered twice.
- Nothing is dismissed automatically, not even alerts Defender already resolved; Aegis only suggests keep, merge or dismiss.
-
Defender incidents marked
redirected(merged into another incident in Defender) are skipped, and so is an incident whose every alert is already in Aegis. This stops a move from single alerts to incidents raising alerts you have already reviewed. - One sync reads up to 50 Defender incidents, or up to 100 alerts on a connection that has not been re-authorised for incidents.
-
A scheduled sync uses the severity chosen on the schedule
(
high,mediumorlow); with none chosen it brings in high and medium. - Raw alerts are not written to the Evidence Locker. A signal becomes evidence on its incident only when a reviewer accepts or merges it (see Evidence).
-
A connection authorised before
SecurityIncident.Read.Allexisted keeps refreshing with the permissions it was granted, so it does not break; selectRe-authorizeto move it to grouped incidents. -
Leave
Client Secretblank when saving to keep the stored secret; enter a new value to rotate it.
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.