Skip to content

Commit f1e35c8

Browse files
authored
Merge pull request #300388 from batamig/freshness-may25
removing name for freshness - azure-docs
2 parents 71c95cb + 7a9c0c2 commit f1e35c8

File tree

12 files changed

+191
-557
lines changed

12 files changed

+191
-557
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -504,6 +504,11 @@
504504
"redirect_url": "/azure/security/fundamentals/azure-CA-details",
505505
"redirect_document_id": false
506506
},
507+
{
508+
"source_path": "articles/security/fundamentals/recover-from-identity-compromise.md",
509+
"redirect_url": "/azure/security/fundamentals/ransomware-detect-respond#road-to-recovery",
510+
"redirect_document_id": false
511+
},
507512
{
508513
"source_path": "articles/event-grid/event-schema-storage-actions.md",
509514
"redirect_url": "/azure/storage-actions/overview",

articles/defender-for-iot/device-builders/index.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,11 +7,11 @@ metadata:
77
title: Microsoft Defender for IoT for device builders documentation
88
description: Microsoft Defender for IoT provides comprehensive threat detection for IoT/OT environments, with multiple deployment options including fully on-premises, cloud-connected, or hybrid.
99
ms.service: defender-for-iot
10-
ms.author: raynew
10+
ms.author: lwainstein
1111
ms.topic: landing-page
1212
ms.collection: M365-security-compliance
13-
author: batamig
14-
manager: raynew
13+
author: lwainstein
14+
manager: orspodek
1515
ms.date: 01/01/2023
1616

1717
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new

articles/defender-for-iot/organizations/appliance-catalog/index.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ metadata:
77
title: Microsoft Defender for IoT - OT monitoring appliance reference
88
description: Learn about the appliances available for use with Microsoft Defender for IoT OT sensors.
99
ms.topic: landing-page
10-
ms.author: raynew
10+
ms.author: lwainstein
1111
ms.date: 07/24/2022
1212

1313
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new

articles/defender-for-iot/organizations/index.yml

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,9 @@ metadata:
66
title: Microsoft Defender for IoT documentation for organizations
77
description: Microsoft Defender for IoT provides comprehensive threat detection for IoT/OT environments, with multiple deployment options that include cloud-connected, fully on-premises, or hybrid.
88
ms.service: defender-for-iot
9-
ms.author: raynew
9+
ms.author: lwainstein
1010
ms.topic: landing-page
1111
ms.collection: M365-security-compliance
12-
author: batamig
13-
manager: raynew
1412
ms.date: 07/10/2022
1513

1614
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new

articles/security/fundamentals/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,8 +36,6 @@
3636
href: backup-plan-to-protect-against-ransomware.md
3737
- name: Ransomware protection with Azure Firewall Premium
3838
href: ransomware-protection-with-azure-firewall.md
39-
- name: Recovering from systemic identity compromise
40-
href: recover-from-identity-compromise.md
4139
- name: Threat protection
4240
href: threat-detection.md
4341

articles/security/fundamentals/recover-from-identity-compromise.md

Lines changed: 0 additions & 363 deletions
This file was deleted.

articles/sentinel/automation/automate-responses-with-playbooks.md

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Automate threat response with playbooks in Microsoft Sentinel | Microsoft Docs
3-
description: This article explains automation in Microsoft Sentinel, and shows how to use playbooks to automate threat prevention and response.
2+
title: Automate Threat Response with Playbooks in Microsoft Sentinel
3+
description: Learn how to automate threat response in Microsoft Sentinel using playbooks to efficiently manage security alerts and incidents.
44
ms.topic: conceptual
55
author: batamig
66
ms.author: bagol
7-
ms.date: 03/14/2024
7+
ms.date: 05/27/2025
88
appliesto:
99
- Microsoft Sentinel in the Microsoft Defender portal
1010
- Microsoft Sentinel in the Azure portal
@@ -15,33 +15,33 @@ ms.collection: usx-security
1515

1616
# Automate threat response with playbooks in Microsoft Sentinel
1717

18-
SOC analysts deal with numerous security alerts and incidents, and the sheer volume can overwhelm teams, leading to ignored alerts and uninvestigated incidents. Many alerts and incidents can be addressed by the same sets of predefined remediation actions, which can be automated to make the SOC more efficient and free up analysts for deeper investigations.
18+
Security operations centers (SOCs) face a constant stream of security alerts and incidents. Managing these efficiently is critical to keeping your organization’s security strong. Microsoft Sentinel playbooks are automated workflows that help you respond to threats quickly and consistently. This article shows how to use playbooks in Microsoft Sentinel to automate threat response, cut manual effort, and let your team focus on deeper investigations.
1919

20-
Use Microsoft Sentinel playbooks to run preconfigured sets of remediation actions to help [automate and orchestrate your threat response](tutorial-respond-threats-playbook.md). Run playbooks automatically, in response to specific alerts and incidents that trigger a configured [automation rule](../automate-incident-handling-with-automation-rules.md), or manually and on-demand for a particular entity or alert.
20+
Use Microsoft Sentinel playbooks to run preconfigured sets of remediation actions and [automate and orchestrate your threat response](tutorial-respond-threats-playbook.md). Run playbooks automatically in response to specific alerts and incidents that trigger a configured [automation rule](../automate-incident-handling-with-automation-rules.md), or run them manually for a particular entity or alert.
2121

22-
For example, if an account and machine are compromised, a playbook can automatically isolate the machine from the network and block the account by the time the SOC team is notified of the incident.
22+
For example, if an account and machine are compromised, a playbook can automatically isolate the machine from the network and block the account before the SOC team gets notified of the incident.
2323

2424
> [!NOTE]
25-
> Because playbooks make use of Azure Logic Apps, additional charges may apply. Visit the [Azure Logic Apps](https://azure.microsoft.com/pricing/details/logic-apps/) pricing page for more details.
25+
> Because playbooks use Azure Logic Apps, additional charges can apply. Go to the [Azure Logic Apps](https://azure.microsoft.com/pricing/details/logic-apps/) pricing page for more details.
2626
2727
[!INCLUDE [unified-soc-preview](../includes/unified-soc-preview.md)]
2828

2929
## Recommended use cases
3030

31-
The following table lists high-level use cases where we recommend using Microsoft Sentinel playbooks to automate your threat response:
31+
The following table lists common use cases where Microsoft Sentinel playbooks help automate threat response:
3232

3333
|Use case |Description |
3434
|---------|---------|
35-
|**Enrichment** | Collect data and attach it to an incident to help your team make smarter decisions. |
36-
|**Bi-directional sync** | Sync Microsoft Sentinel incidents with other ticketing systems. For example, create an automation rule for all incident creations, and attach a playbook that opens a ticket in ServiceNow. |
37-
|**Orchestration** | Use the SOC team's chat platform to better control the incidents queue. For example, send a message to your security operations channel in Microsoft Teams or Slack to make sure your security analysts are aware of the incident. |
38-
|**Response** | Immediately respond to threats, with minimal human dependencies, such as when a compromised user or machine is indicated. Alternately, manually trigger a series of automated steps during an investigation or while hunting. |
35+
|**Enrichment** | Collect data and attach it to an incident so your team can make better decisions. |
36+
|**Bi-directional sync** | Sync Microsoft Sentinel incidents with other ticketing systems. For example, create an automation rule for all new incidents, and attach a playbook that opens a ticket in ServiceNow. |
37+
|**Orchestration** | Use the SOC team's chat platform to manage the incident queue. For example, send a message to your security operations channel in Microsoft Teams or Slack so your security analysts know about the incident. |
38+
|**Response** | Respond to threats right away with minimal human involvement, such as when a compromised user or machine is detected. Or, manually trigger automated steps during an investigation or while hunting. |
3939

4040
For more information, see [Recommended playbook use cases, templates, and examples](playbook-recommendations.md).
4141

4242
## Prerequisites
4343

44-
The following roles are required to use Azure Logic Apps to create and run playbooks in Microsoft Sentinel.
44+
You need the following roles to use Azure Logic Apps to create and run playbooks in Microsoft Sentinel.
4545

4646
[!INCLUDE [playbooks-roles](../includes/playbooks-roles.md)]
4747

@@ -56,15 +56,15 @@ The following roles are required to use Azure Logic Apps to create and run playb
5656
5757
Playbook templates are prebuilt, tested, and ready-to-use workflows that aren't usable as playbooks themselves, but are ready for you to customize to meet your needs. We also recommend that you use playbook templates as a reference of best practices when developing playbooks from scratch, or as inspiration for new automation scenarios.
5858

59-
Access playbook templates from the following sources:
59+
Get playbook templates from these sources:
6060

6161
|Location |Description |
6262
|---------|---------|
63-
|**Microsoft Sentinel Automation page** | The **Playbook templates** tab lists all installed playbooks. Create one or more active playbooks using the same template. <br><br>When we publish a new version of a template, any active playbooks created from that template have an extra label added in the **Active playbooks** tab to indicate that an update is available. |
64-
|**Microsoft Sentinel Content hub page** | Playbook templates are available as part of product solutions or standalone content installed from the **Content hub**. <br><br>For more information, see: <br> [About Microsoft Sentinel content and solutions](../sentinel-solutions.md) <br>[Discover and manage Microsoft Sentinel out-of-the-box content](../sentinel-solutions-deploy.md)|
65-
|**GitHub** | The [Microsoft Sentinel GitHub repository](https://github.com/Azure/Azure-Sentinel/tree/master/Playbooks) contains many other playbook templates. Select **Deploy to Azure** to deploy a template to your Azure subscription.|
63+
|**Microsoft Sentinel Automation page** | The **Playbook templates** tab shows all installed playbooks. Create one or more active playbooks using the same template. <br><br>When a new version of a template is published, any active playbooks created from that template get an extra label in the **Active playbooks** tab to show that an update is available. |
64+
|**Microsoft Sentinel Content hub page** | Playbook templates are part of product solutions or standalone content you install from the **Content hub**. <br><br>For more information, see: <br> [About Microsoft Sentinel content and solutions](../sentinel-solutions.md) <br>[Discover and manage Microsoft Sentinel out-of-the-box content](../sentinel-solutions-deploy.md)|
65+
|**GitHub** | The [Microsoft Sentinel GitHub repository](https://github.com/Azure/Azure-Sentinel/tree/master/Playbooks) has many other playbook templates. Select **Deploy to Azure** to deploy a template to your Azure subscription.|
6666

67-
Technically, a playbook template is an [Azure Resource Manager (ARM) template](/azure/azure-resource-manager/templates/), which consists of several resources: an Azure Logic Apps workflow and API connections for each connection involved.
67+
A playbook template is an [Azure Resource Manager (ARM) template](/azure/azure-resource-manager/templates/) that includes several resources: an Azure Logic Apps workflow and API connections for each connection involved.
6868

6969
For more information, see:
7070

@@ -74,15 +74,15 @@ For more information, see:
7474

7575
## Playbook creation and usage workflow
7676

77-
Use the following workflow to create and run Microsoft Sentinel playbooks:
77+
Follow these steps to create and run Microsoft Sentinel playbooks:
7878

79-
1. Define your automation scenario. We recommend that you review [recommended playbooks use cases](playbook-recommendations.md#recommended-playbook-use-cases) and [playbook templates](playbook-recommendations.md#recommended-playbook-templates) to start.
79+
1. Define your automation scenario. Review [recommended playbooks use cases](playbook-recommendations.md#recommended-playbook-use-cases) and [playbook templates](playbook-recommendations.md#recommended-playbook-templates) to get started.
8080

8181
1. If you're not using a template, create your playbook and build your logic app. For more information, see [Create and manage Microsoft Sentinel playbooks](create-playbooks.md).
8282

8383
Test your logic app by running it manually. For more information, see [Run a playbook manually, on demand](run-playbooks.md#run-a-playbook-manually-on-demand).
8484

85-
1. Configure your playbook to run automatically on a new alert or incident creation, or run it manually as needed for your processes. For more information, see [Respond to threats with Microsoft Sentinel playbooks](run-playbooks.md).
85+
1. Set up your playbook to run automatically when a new alert or incident is created, or run it manually as needed for your process. For more information, see [Respond to threats with Microsoft Sentinel playbooks](run-playbooks.md).
8686

8787
## Related content
8888

Lines changed: 22 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Connect your data sources to Microsoft Sentinel by using data connectors
3-
description: Learn how to install and configure a data connector in Microsoft Sentinel.
4-
author: cwatson-cat
2+
title: Connect Data Sources to Microsoft Sentinel Using Data Connectors
3+
description: Learn how to connect data sources to Microsoft Sentinel using data connectors for improved threat detection.
4+
author: batamig
55
ms.topic: how-to
6-
ms.date: 03/28/2024
7-
ms.author: cwatson
6+
ms.date: 05/27/2025
7+
ms.author: bagol
88
appliesto:
99
- Microsoft Sentinel in the Microsoft Defender portal
1010
- Microsoft Sentinel in the Azure portal
@@ -15,21 +15,20 @@ ms.collection: usx-security
1515

1616
---
1717

18-
# Connect your data sources to Microsoft Sentinel by using data connectors
18+
# Connect data sources to Microsoft Sentinel by using data connectors
1919

20-
Install and configure data connectors to ingest your data into Microsoft Sentinel. Data connectors are available as part of solutions from the content hub in Microsoft Sentinel. After you install a solution from the content hub, the related data connectors are available to enable and configure. To find and install solutions that include data connectors, see [Discover and manage Microsoft Sentinel out-of-the-box content](sentinel-solutions-deploy.md).
21-
22-
This article provides general information about how to enable a data connector and how to find more detailed installation instructions for other data connectors. For more information about data connectors in Microsoft Sentinel, see the following articles:
20+
Connect data sources to Microsoft Sentinel by installing and configuring data connectors. This article generally explains how to install data connectors available in the Microsoft Sentinel **Content hub** to ingest and analyze data for improved threat detection.
2321

2422
- [Microsoft Sentinel data connectors](connect-data-sources.md)
2523
- [Find your Microsoft Sentinel data connector](data-connectors-reference.md)
26-
24+
- [Discover and manage Microsoft Sentinel out-of-the-box content](sentinel-solutions-deploy.md)
2725

2826
[!INCLUDE [unified-soc-preview](includes/unified-soc-preview.md)]
2927

3028
## Prerequisites
3129

3230
Before you begin, make sure you have the appropriate access and you or someone in your organization installs the related solution.
31+
3332
- You must have read and write permissions on the Microsoft Sentinel workspace.
3433
- Install the solution that includes the data connector from the **Content Hub** in Microsoft Sentinel. For more information, see [Discover and manage Microsoft Sentinel out-of-the-box content](sentinel-solutions-deploy.md).
3534

@@ -38,8 +37,10 @@ Before you begin, make sure you have the appropriate access and you or someone i
3837

3938
After you or someone in your organization installs the solution that includes the data connector you need, configure the data connector to start ingesting data.
4039

41-
1. For Microsoft Sentinel in the [Azure portal](https://portal.azure.com), under **Configuration**, select **Data connectors**.<br> For Microsoft Sentinel in the [Defender portal](https://security.microsoft.com/), select **Microsoft Sentinel** > **Configurations** > **Data connectors**.
42-
1. Search for and select the connector. If you don't see the data connector you want, install the solution associated with it from the **Content Hub**.
40+
1. For Microsoft Sentinel in the [Defender portal](https://security.microsoft.com/), select **Microsoft Sentinel** > **Configurations** > **Data connectors**. For Microsoft Sentinel in the [Azure portal](https://portal.azure.com), under **Configuration**, select **Data connectors**.
41+
42+
1. Search for and select the connector. If you don't see the data connector you want, check again that the relevant solution is installed in the **Content hub**.
43+
4344
1. Select **Open connector page**.
4445

4546
#### [Defender portal](#tab/defender-portal)
@@ -48,32 +49,24 @@ After you or someone in your organization installs the solution that includes th
4849
:::image type="content" source="media/configure-data-connector/open-connector-page-option.png" alt-text="Screenshot of data connector details page with open connector page button.":::
4950
---
5051

51-
1. Review the **Prerequisites**. To configure the data connector, fulfill all the prerequisites.
52-
1. Follow the steps outlined in the **Configurations** section.
52+
1. Review the **Prerequisites** for your data connector and ensure that they're fulfilled.
53+
54+
1. Follow the steps outlined in the **Configurations** section for your data connector.
5355

54-
For some connectors, find more specific configuration information in the **Collect data** section in the Microsoft Sentinel documentation. For example, see the following articles:
56+
For some connectors, find more specific configuration information in the **Collect data** section in the Microsoft Sentinel documentation.
57+
5558
- [Connect Microsoft Sentinel to Azure, Windows, Microsoft, and Amazon services](connect-azure-windows-microsoft-services.md)
56-
- [Find your Microsoft Sentinel data connector](data-connectors-reference.md)
59+
- [Data connector prerequisites](data-connectors-reference.md#windows-security-events-via-ama)
5760

5861
After you configure the data connector, it might take some time for the data to be ingested into Microsoft Sentinel. When the data connector is connected, you see a summary of the data in the **Data received** graph, and the connectivity status of the data types.
5962

6063
:::image type="content" source="media/configure-data-connector/connected-data-connector.png" alt-text="Screenshot of a data connector page with status connected and graph that shows the data received.":::
6164

6265
## Find your data
6366

64-
After you enable the connector successfully, the connector begins to stream data to the table schemas related to the data types you configurated.
67+
After you enable the connector successfully, the connector begins to stream data to the table schemas related to the data types you configured.
6568

66-
To view the data:
67-
68-
#### [Defender portal](#tab/defender-portal-1)
69-
70-
See [Where to find your Microsoft Sentinel data in Microsoft Defender portal](/defender-xdr/advanced-hunting-microsoft-defender#where-to-find-your-microsoft-sentinel-data).
71-
72-
#### [Azure portal](#tab/azure-portal-1)
73-
74-
Query the tables in the Microsoft Sentinel workspace linked to your Microsoft Sentinel workspace.
75-
76-
---
69+
In the Defender portal, query data in the **Advanced hunting** page, or in the Azure portal, query data in the **Logs** page.
7770

7871
## Find support for a data connector
7972

@@ -92,6 +85,4 @@ For more information about solutions and data connectors in Microsoft Sentinel,
9285

9386
- [Microsoft Sentinel data connectors](connect-data-sources.md)
9487
- [Find your Microsoft Sentinel data connector](data-connectors-reference.md)
95-
- [Connect Microsoft Sentinel to Azure, Windows, Microsoft, and Amazon services](connect-azure-windows-microsoft-services.md)
96-
- [About Microsoft Sentinel content and solutions](sentinel-solutions.md)
97-
- [Discover and manage Microsoft Sentinel out-of-the-box content](sentinel-solutions-deploy.md)
88+
- [Connect Microsoft Sentinel to Azure, Windows, Microsoft, and Amazon services](connect-azure-windows-microsoft-services.md)

0 commit comments

Comments
 (0)