Microsoft Defender XDR

Security alerts and incidents across Microsoft Defender, plus secure scores

Connects by
Signing in with Microsoft
Category
Developer tools
Part of
Microsoft
Tools
174
ServiceKey
Microsoft Defender XDRmicrosoft-defender

Connecting

Your client presses Connect on their link and approves on Microsoft's own screen. Operate As never sees their password.

Check they're connected
curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"
Response
[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "microsoft-defender"    ]  }]

Permissions

What the client readsPermission it asks for
See your organization's security alertsSecurityAlert.Read.All
See your organization's security incidentsSecurityIncident.Read.All
See your organization's secure scores and security eventsSecurityEvents.Read.All

Tools

Install Microsoft Defender XDR's typed package for your language:

pip install operate-as-microsoft-defender
Run microsoft-defender.get_count_additional_sources_f0d1
curl -X POST https://api.operate.as/v1/actions/microsoft-defender.get_count_additional_sources_f0d1 \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "ediscovery_case_id": "<ediscovery_case_id>",      "ediscovery_search_id": "<ediscovery_search_id>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/microsoft-defender.get_count_additional_sources_f0d1

Response
{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://graph.microsoft.com/v1.0. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint
curl "https://api.operate.as/v1/clients/6f1c2a7e-.../microsoft-defender/..." \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"
Response
{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If Microsoft refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer
HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Microsoft access ended. Send them their link to reconnect."}
Your webhook receives
{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "microsoft",    "services": [      "microsoft-defender"    ],    "reconnectUrl": "https://…"  }}