Skip to content

Commit 16e633c

Browse files
committed
Updated what's new
1 parent 92f2768 commit 16e633c

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

articles/sentinel/whats-new.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,16 @@ See these [important announcements](#announcements) about recent changes to feat
1919

2020
## February 2023
2121

22+
- [Microsoft 365 Defender data connector is now generally available](#microsoft-365-defender-data-connector-is-now-generally-available)
2223
- [Advanced scheduling for analytics rules (Preview)](#advanced-scheduling-for-analytics-rules-preview)
2324

25+
### Microsoft 365 Defender data connector is now generally available
26+
27+
Microsoft 365 Defender incidents, alerts, and raw event data can be ingested into Microsoft Sentinel using this connector. It also enables the bi-directional synchronization of incidents between Microsoft 365 Defender and Microsoft Sentinel. This integration allows you to manage all of your incidents in Microsoft Sentinel, while taking advantage of Microsoft 365 Defender's specialized tools and capabilities to investigate those incidents that originated in Microsoft 365.
28+
29+
- Learn more about [Microsoft 365 Defender integration with Microsoft Sentinel](microsoft-365-defender-sentinel-integration.md)
30+
- Learn how to [connect Microsoft 365 Defender to Microsoft Sentinel](connect-microsoft-365-defender.md).
31+
2432
### Advanced scheduling for analytics rules (Preview)
2533

2634
To give you more flexibility in scheduling your analytics rule execution times and to help you avoid potential conflicts, Microsoft Sentinel now allows you to determine when newly created analytics rules will run for the first time. The default behavior is as it has been: for them to run immediately upon creation.

0 commit comments

Comments
 (0)