Loading...

Automate your alert response actions in Microsoft 365 Defender

Automate your alert response actions in Microsoft 365 Defender
 

While Microsoft’s Extended Detection and Response (XDR) solution helps prioritize response activities and provides a unified experience that allows for more effective investigation at the incident level, the increasing volume and speed of sophisticated attacks, still challenges the capacity of most security teams.

 

Automation is growing in importance to close the gap to the speed needed to respond to more attacks faster. Automating the response actions to common alerts in can help you stay ahead of threats, protect your organization more effectively, significantly reduce response times, and save manual work for the Security Operations Center (SOC).

 

In this blog post, we'll explain how you can set up automatic response actions for any built-in alerts in Microsoft 365 Defender using This simple method will enable you to take quick, decisive, automatic action on impacted entities and stay ahead of potential threats in your organization.

 

Think about your day-to-day activities – are there recurring alerts in your environment that you typically take the same set of simple actions on to address them? These repetitive activities are good candidates for automated response actions to lighten the load of the SOC team.

So let’s take a look at how you can get started with the automation of response actions in Microsoft 365 Defender.

First, navigate to the Advanced hunting screen You will need to create a new custom detection for a KQL query such as:

 

AlertEvidence | where Title == "Suspicious URL clicked"

 

Next, in your custom detection, you can specify the lookback timeframe, e.g. the past three hours. You can keep it simple and stop here or expand your KQL to include more conditions beyond the alert type, if you want to trigger the automatic response only on a subset of these alerts.

Once you’ve determined the scope of the alert, it’s time to automate the response and define subsequent actions. To do that, choose the entities in the alert that you would like to take an action on by ticking the checkboxes for those entities, and choose which automatic actions to apply to each entity.

 

Image 1: Microsoft 365 Defender dashboard – Navigate to “Advanced Hunting” screenImage 1: Microsoft 365 Defender dashboard – Navigate to “Advanced Hunting” screen

 

Here you can choose from a wide range of actions such as isolating the affected asset, quarantining a file that was identified as malicious, triggering an investigation and more. In our example, we’ll choose to isolate the device associated with the alert but you can find a complete list of available response actions here.

 

GIF 1: Creating custom detections and defining automatic response actions walkthrough.GIF 1: Creating custom detections and defining automatic response actions walkthrough.

 

Using these types of custom detections in combination with KQL queries allow you to easily set up automated playbooks for alerts without the need for complex integrations or development efforts. We’ve seen these especially helpful for smaller SOC teams who don't have a Security, Orchestration, Automation, and Response (SOAR) product, as it allows them to easily add automation to their toolset in a way that is best suited for their organization. However, they are impactful to organizations of any size looking to centralize some of their basic response actions directly within their XDR solution.

 

By automating repetitive tasks in your XDR, you shorten response times and free up the SOC team from mundane and repetitive tasks so they can focus on more important security efforts.

 

 

Learn more:

Published on:

Learn more
Microsoft 365 Defender Blog articles
Microsoft 365 Defender Blog articles

Microsoft 365 Defender Blog articles

Share post:

Related posts

Migration of Topics used in Viva Engage

In February 2024, Microsoft announced the retirement of Viva Topics and the return of Engage topics to Viva Engage. Organizations that possess...

13 hours ago

Microsoft Copilot (Microsoft 365): BizChat – Teams Chats in ContextIQ

Microsoft Copilot is expanding its capabilities with BizChat, which allows users to search and select Teams Chats within ContextIQ to scope th...

14 hours ago

Microsoft Teams: Extensibility for PSTN calls

Microsoft Teams is set to extend the PSTN calling experience through third-party application developers. This new feature will provide context...

14 hours ago

Microsoft Teams: Approvals in Teams within GCCH

Good news for users within GCCH - the Approvals app is now available within Microsoft Teams. This feature has reached the General Availability...

14 hours ago

Microsoft Teams: Default enable transcription policy for new tenants

In a bid to boost the adoption of transcription and AI features in Microsoft Teams, the default policy for Transcription on new tenants is bei...

14 hours ago

Mandatory MFA Requirement for Microsoft 365 Admin Center

In February 2025, Microsoft will begin enforcing a mandatory MFA requirement for the Microsoft 365 admin center. All connections to the Micros...

17 hours ago

How to create SharePoint Lists with MS Graph

In this post I want to showcase how to create a SharePoint Library and SharePoint List using MS Graph. You might need to create a List with MS...

2 days ago

Create & Import Data From SharePoint List to Dataverse Table usign AI in 2 Minutes

you can Create & Import Data From SharePoint List to Dataverse Table usign AI in 2 Minutes Watch the full video here. Hope it helps.

2 days ago

Is Microsoft 365 Copilot becoming our multi-agentic AI assistant?

Microsoft announced Microsoft 365 Copilot for the first time ever around a year and a half ago on the 16th March 2023. Since then, the way we ...

3 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy