Skip to content

Commit 5a4dcc1

Browse files
Merge pull request #50897 from KenMAG/main
Updated module for Microsoft Sentinel in both Azure and Defender portals
2 parents 3177b52 + 241068d commit 5a4dcc1

10 files changed

+71
-33
lines changed

learn-pr/wwl-sci/connect-data-to-azure-sentinel-with-data-connectors/1-introduction.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ title: Introduction
44
metadata:
55
title: Introduction
66
description: "Introduction"
7-
ms.date: 06/21/2022
8-
author: wwlpublish
7+
ms.date: 06/11/2025
8+
author: KenMAG
99
ms.author: kelawson
1010
ms.topic: unit
1111
azureSandbox: false

learn-pr/wwl-sci/connect-data-to-azure-sentinel-with-data-connectors/3-understand-data-connector-providers.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ title: Understand data connector providers
44
metadata:
55
title: Understand data connector providers
66
description: "Understand data connector providers"
7-
ms.date: 06/21/2022
8-
author: wwlpublish
7+
ms.date: 06/11/2025
8+
author: KenMAG
99
ms.author: kelawson
1010
ms.topic: unit
1111
azureSandbox: false

learn-pr/wwl-sci/connect-data-to-azure-sentinel-with-data-connectors/4-view-connected-hosts.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ title: View connected hosts
44
metadata:
55
title: View connected hosts
66
description: "View connected hosts"
7-
ms.date: 06/21/2022
8-
author: wwlpublish
7+
ms.date: 06/11/2025
8+
author: KenMAG
99
ms.author: kelawson
1010
ms.topic: unit
1111
azureSandbox: false

learn-pr/wwl-sci/connect-data-to-azure-sentinel-with-data-connectors/5-knowledge-check.yml

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ title: Module assessment
44
metadata:
55
title: Module assessment
66
description: "Knowledge check"
7-
ms.date: 06/21/2022
8-
author: wwlpublish
7+
ms.date: 06/11/2025
8+
author: KenMAG
99
ms.author: kelawson
1010
ms.topic: unit
1111
azureSandbox: false
@@ -31,21 +31,21 @@ quiz:
3131
choices:
3232
- content: "Microsoft Entra ID"
3333
isCorrect: false
34-
explanation: "Incorrect. The Azure Active Directory provides parsed data."
34+
explanation: "Incorrect. The Entra ID Logs provide parsed data."
3535
- content: "Syslog"
3636
isCorrect: true
37-
explanation: "Correct. The data is stored in the SyslogMessage"
37+
explanation: "Correct. The data is stored in the SyslogMessage"
3838
- content: "CEF"
3939
isCorrect: false
40-
explanation: "Incorrect. The CEF connector provides parsed data."
40+
explanation: "Incorrect. The CEF connector provides parsed data."
4141
- content: "The vendor-provided connectors primarily use which of the following?"
4242
choices:
4343
- content: "Azure Activity Connector"
4444
isCorrect: false
45-
explanation: "Incorrect. Vendors don't use the Azure Activity connector."
45+
explanation: "Incorrect. Vendors don't use the Azure Activity connector."
4646
- content: "Security Events Connector"
4747
isCorrect: false
48-
explanation: "Incorrect. The Security Events connector is for sending Windows event logs."
48+
explanation: "Incorrect. The Security Events connector is for sending Windows event logs."
4949
- content: "CEF Connector"
5050
isCorrect: true
51-
explanation: "Correct. Most Vendor-provided connectors use the CEF connector."
51+
explanation: "Correct. Most Vendor-provided connectors use the CEF connector."

learn-pr/wwl-sci/connect-data-to-azure-sentinel-with-data-connectors/includes/1-introduction.md

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,15 @@
1-
Data is sent to the Microsoft Sentinel workspace by configuring the provided data connectors. The data connectors are included in out-of-the-box (OOTB), or built-in Content Hub solutions for Microsoft 365 services, Azure, and third-party specific.
2-
1+
Data is ingested to the Microsoft Sentinel workspace by configuring data connectors. The data connectors are included in Content Hub solutions for Microsoft services and products, and third-party solutions.
2+
3+
## Microsoft Sentinel and Defender XDR
4+
5+
Use one of the following methods to integrate Microsoft Sentinel with Microsoft Defender XDR services:
6+
7+
- Ingest Microsoft Defender XDR service data into Microsoft Sentinel and view Microsoft Sentinel data in the Azure portal. Enable the Defender XDR connector in Microsoft Sentinel.
8+
9+
- Integrate Microsoft Sentinel and Defender XDR directly in the Microsoft Defender portal. In this case, view Microsoft Sentinel data directly with the rest of your Defender incidents, alerts, vulnerabilities, and other security data. To do this, you must onboard Microsoft Sentinel to the Defender portal.
10+
11+
## Scenario
12+
313
You're a Security Operations Analyst working at a company that implemented Microsoft Sentinel. You need to learn how to connect log data from the many different data sources in your organization. The organization has data from Microsoft 365, Microsoft Defender XDR, Azure resources, non-azure virtual machines, and network appliances.
414

515
You plan on using the Microsoft Sentinel Content Hub solutions that include the data connectors to integrate the log data from the various sources. You need to document a connector plan for management that maps each of the organization's data sources to the proper Microsoft Sentinel data connector.
@@ -13,7 +23,7 @@ After completing this module, you'll be able to:
1323

1424
## Prerequisites
1525

16-
Basic experience with Microsoft Azure operations.
26+
Basic experience with Microsoft Azure or Microsoft Defender operations.
1727

1828
## Interactive lab simulation
1929

learn-pr/wwl-sci/connect-data-to-azure-sentinel-with-data-connectors/includes/3-understand-data-connector-providers.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,20 +10,19 @@ The Microsoft Defender XDR data connector provides alerts, incidents, and raw da
1010

1111
- Microsoft Defender for Cloud Apps
1212

13-
1413
### Microsoft Azure Services
1514

1615
The connectors for Microsoft and Azure-related services include (but aren't limited to):
1716

18-
- Microsoft Entra ID
17+
- Microsoft Entra ID
1918

2019
- Azure Activity
2120

2221
- Microsoft Entra ID Protection
2322

2423
- Azure DDoS Protection
2524

26-
- Microsoft Defender for IoT
25+
- Microsoft Defender for IoT
2726

2827
- Azure Information Protection
2928

@@ -37,13 +36,13 @@ The connectors for Microsoft and Azure-related services include (but aren't limi
3736

3837
- Office 365
3938

40-
- Windows firewall
39+
- Windows Firewall
4140

4241
- Security Events
4342

4443
### Vendor connectors
4544

46-
Microsoft Sentinel provides an ever-growing list of vendor-specific data connectors. These connectors primarily use the CEF and Syslog connector as their foundation.
45+
Microsoft Sentinel provides an ever-growing list of vendor-specific data connectors. These connectors primarily use the CEF and Syslog connector as their foundation.
4746

4847
> [!TIP]
4948
> Remember to check the connector page to see the Data Type (table) that the connector writes to.
@@ -66,7 +65,7 @@ Common Event Format (CEF) is an industry-standard format on top of Syslog messag
6665

6766
### Syslog vs. Common Event Format
6867

69-
CEF is always a superior choice because the log data is parsed into predefined fields in the CommonSecurityLog table. Syslog provides header fields, but the raw log message is stored in a field named SyslogMessage in the Syslog table. For the Syslog data to be queried, you need to write a parser to extract the specific fields. The process to create a Parser for a Syslog message is demonstrated in a later module.
68+
CEF is always a superior choice because the log data is parsed into predefined fields in the CommonSecurityLog table. Syslog provides header fields, but the raw log message is stored in a field named SyslogMessage in the Syslog table. For the Syslog data to be queried, you need to write a parser to extract the specific fields. The process to create a Parser for a Syslog message is demonstrated in a later module.
7069

7170
### Connector architecture options
7271

Lines changed: 33 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,37 @@
1-
The Data Connector page shows the connectors that are installed and can be filtered to show the ones with a `Connected` status. The count of Windows and Linux hosts connected with an agent is available in the Log Analytics workspace. To see your connected hosts do the following steps:
1+
To view your Windows and Linux hosts connected with an agent, you can do so in the Log Analytics workspace. To see your connected hosts do the following steps:
22

3-
1. Select **Settings**
3+
## Microsoft Sentinel and Defender XDR
44

5-
1. Workspace Settings (this selection transfers you to Log Analytics)
5+
Select the appropriate tab to see the connected hosts depending on which integration method you use.
66

7-
1. In Log Analytics Settings area, select **Agents**
7+
## [Defender portal](#tab/defender-portal)
88

9-
1. There are two tabs to view - one for Windows another for Linux.
9+
1. In the Microsoft Defender portal navigation menu, expand **System**, and select **Settings**.
10+
11+
1. Select **Microsoft Sentinel**.
12+
13+
1. Select the appropriate Microsoft Sentinel workspace.
14+
15+
1. In the side panel that opens, select **Log Analytics settings**, and **Configure Log Analytics work**.
16+
17+
:::image type="content" source="../media/04-view-connected-hosts-defender.png" alt-text="Screen shot of Microsoft Defender Microsoft Sentinel workspace configuration page.":::
18+
19+
1. In the Log Analytics workspace, select **Settings** from the navigation menu, and then select **Agents**.
20+
21+
1. Select either the **Windows** or **Linux** tab to view the connected hosts.
22+
23+
:::image type="content" source="../media/04-log-analytics-connected-hosts.png" alt-text="Screen shot of Log Analytics Agents page.":::
24+
25+
## [Azure portal](#tab/azure-portal)
26+
27+
1. In the Microsoft Sentinel navigation menu, expand **Configuration**, and select **Settings**.
28+
29+
1. Select the **Workspace settings** tab (this selection transfers you to Log Analytics).
30+
31+
1. In the Log Analytics workspace, select **Settings** from the navigation menu, and then select **Agents**.
32+
33+
1. Select either the **Windows** or **Linux** tab to view the connected hosts.
34+
35+
:::image type="content" source="../media/04-log-analytics-connected-hosts.png" alt-text="Screen shot of Log Analytics Agents page.":::
36+
37+
---

learn-pr/wwl-sci/connect-data-to-azure-sentinel-with-data-connectors/index.yml

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,28 +3,29 @@ uid: learn.wwl.connect-data-to-azure-sentinel-with-data-connectors
33
metadata:
44
title: Connect data to Microsoft Sentinel using data connectors
55
description: "Connect data to Microsoft Sentinel using data connectors"
6-
ms.date: 08/02/2023
7-
author: wwlpublish
6+
ms.date: 06/11/2025
7+
author: KenMAG
88
ms.author: kelawson
99
ms.topic: module
1010
ms.service: microsoft-sentinel
1111
title: Connect data to Microsoft Sentinel using data connectors
12-
summary: The primary approach to connect log data is using the Microsoft Sentinel provided data connectors. This module provides an overview of the available data connectors.
12+
summary: The primary approach to connect log data is using the Microsoft Sentinel provided data connectors. This module provides an overview of the available data connectors.
1313
abstract: |
14-
Upon completion of this module, the learner will be able to:
14+
Upon completion of this module, the learner is able to:
1515
- Describe how to install Content Hub Solutions to provision Microsoft Sentinel Data connectors
1616
- Explain the use of data connectors in Microsoft Sentinel
1717
- Describe the Microsoft Sentinel data connector providers
1818
- Explain the Common Event Format and Syslog connector differences in Microsoft Sentinel
1919
prerequisites: |
20-
Basic experience with Microsoft Azure operations
20+
Basic experience with Microsoft Azure and Microsoft Defender operations
2121
iconUrl: /training/achievements/connect-data-to-azure-sentinel-with-data-connectors.svg
2222
levels:
2323
- intermediate
2424
roles:
2525
- security-operations-analyst
2626
products:
2727
- azure
28+
- microsoft-defender
2829
- microsoft-sentinel
2930
- azure-log-analytics
3031
subjects:
153 KB
Loading
330 KB
Loading

0 commit comments

Comments
 (0)