page_type	languages	products	description
sample	kusto	Microsoft 365 Defender	Microsoft 365 Defender repository for Advanced Hunting

Advanced hunting queries for Microsoft 365 Defender

This repo contains sample queries for advanced hunting in Microsoft 365 Defender. With these sample queries, you can start to experience advanced hunting, including the types of data that it covers and the query language it supports. You can also explore a variety of attack techniques and how they may be surfaced through advanced hunting.

Advanced hunting queries provide a great starting point for locating and investigating suspicious behavior, and they can be customized to fit your organization's unique environment. Further, you can use these queries to build custom detection rules if you determine that behaviors, events, or data from the advanced hunting query helps you surface potential threats.

---

NOTE: Most of these queries can also be used in Microsoft Defender ATP. However, queries that search tables containing consolidated alert data as well as data about email, apps, and identities can only be used in Microsoft 365 Defender.

• Microsoft Defender ATP schema
• Microsoft 365 Defender schema

---

To get started, simply paste a sample query into the query builder and run the query. If you get syntax errors, try removing empty lines introduced when pasting. If a query returns no results, try expanding the time range.

We are continually building up documentation about advanced hunting and its data schema. You can access the full list of tables and columns in the portal or reference the following resources:

• Advanced hunting overview
• Language overview
• Schema tables descriptions
• Kusto query language reference

Contributions

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

How to contribute

Everyone can freely add a file for a new query or improve on existing queries. To help other users locate new queries quickly, we suggest that you:

• Create a new MarkDown file in the relevant folder according to the MITRE ATT&CK category with contents based on the query submission template
• In the new file:
  • Provide a name for the query that represents the components or activities that it searches for, e.g. Files from malicious sender
  • Describe the query and provide sufficient guidance when applicable
  • Select the categories that apply by marking the appropriate cell with a "v"
• Use the query name as the title, separating each word with a hyphen (-), e.g. files-from-malicious-sender.md
• Include comments that explain the attack technique or anomaly being hunted. Whenever possible, provide links to related documentation.

In addition, construct queries that adhere to the published advanced hunting performance best practices.

Suggestions and feedback

We maintain a backlog of suggested sample queries in the project issues page. Feel free to comment, rate, or provide suggestions.

We value your feedback. Let us know if you run into any problems or share your suggestions by sending email to wdatpqueriesfeedback@microsoft.com.