# Microsoft Defender for Identity

**URL:** <https://discuss.rapid7.com/t/microsoft-defender-for-identity/16700>\
**Category:** Event Sources\
**Created:** [November 1, 2022, 1:49pm UTC](https://discuss.rapid7.com/t/microsoft-defender-for-identity/16700 "2022-11-01T13:49:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dbutler](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/d/9e8a1a/32.png) [@dbutler](https://discuss.rapid7.com/u/dbutler)\
**Post date:** [November 1, 2022, 1:49pm UTC](https://discuss.rapid7.com/t/microsoft-defender-for-identity/16700/1 "2022-11-01T13:49:41Z")

</div>

We currently have the Rapid7 SIEM and I’m trying confirm a Microsoft log source. We have Microsoft Defender for Cloud, Endpoint, and Identity. I have seen Defender for Cloud and Endpoint alerts coming into the SIEM but I can’t find Identity alerts. Does any else have Identity configured to feed the SIEM or is it supposed to be by default since the alerts are supposed to feed to Defender for Endpoint?

---

<div class="post-metadata">

**Author:** ![matt\_robinson](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/m/d2c977/32.png) [@matt\_robinson](https://discuss.rapid7.com/u/matt_robinson)\
**Post date:** [November 1, 2022, 8:33pm UTC](https://discuss.rapid7.com/t/microsoft-defender-for-identity/16700/2 "2022-11-01T20:33:47Z")

</div>

If you’re talking about things like Risky sign-ins, we’ve got a custom alert that looks for the following in the Ingress Authentication \> Azure Event Hub log  
**source\_json.properties.riskState = "atRisk"**

---

<div class="post-metadata">

**Author:** ![SDavis](https://discuss.rapid7.com/user_avatar/discuss.rapid7.com/sdavis/32/843_2.png) [@SDavis](https://discuss.rapid7.com/u/SDavis)\
**Post date:** [November 4, 2022, 1:09pm UTC](https://discuss.rapid7.com/t/microsoft-defender-for-identity/16700/3 "2022-11-04T13:09:43Z")

</div>

@dbutler and @matt_robinson,

I made these a while back but let me know if they are helpful, they go against the Ingress Auth for logset for your Azure Event Hub:

```auto
groupby("source_json.properties.riskLevelDuringSignIn")

where(source_json.properties.riskLevelDuringSignIn!=none)groupby("source_json.properties.riskLevelDuringSignIn")

where(source_json.properties.riskLevelDuringSignIn=low)groupby(user, result)limit(1000, 1000)

where(source_json.properties.riskLevelDuringSignIn=medium)groupby(user, result)limit(1000, 1000)

where( source_json.properties.riskLevelDuringSignIn=high)groupby(user, result)

where( source_json.properties.riskLevelDuringSignIn=low)groupby(result, source_json.resultDescription)

where( source_json.properties.riskLevelDuringSignIn=medium)groupby(result, source_json.resultDescription)

where( source_json.properties.riskLevelDuringSignIn=high)groupby(result, source_json.resultDescription)

where(source_json.properties.riskState!=none AND source_json.properties.riskState=dismissed)groupby(user, source_json.properties.riskDetail)

where(source_json.properties.riskState!=none)groupby(source_json.properties.riskState)

where(source_json.properties.riskState!=none AND source_json.properties.riskState=dismissed)groupby(user, source_json.properties.riskDetail)

where(source_json.properties.riskState!=none AND source_json.properties.riskState=remediated)groupby(user, source_json.properties.riskDetail)

where(source_json.properties.riskState!=none AND source_json.properties.riskState=atRisk)groupby(user, source_json.properties.riskEventTypes.0)limit(1000)

where(source_json.properties.riskState=atRisk AND source_json.properties.riskEventTypes.0=unlikelyTravel)groupby(user, geoip_country_name)

```

edit: these are old queries and aren’t taking advantage of the newish LEQL Operators, just FYI. I will try and go back through and update them.
