Skip to content

Commit 7561a69

Browse files
Merge branch 'main' into WI359551-rewrite-configure-dsa-mdi-with-gmsa
2 parents 5227286 + cf963b1 commit 7561a69

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

defender-for-cloud-apps/create-snapshot-cloud-discovery-reports.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Create snapshot cloud discovery reports
33
description: This article provides information about how to upload logs manually to create a snapshot report of your cloud discovery apps.
4-
ms.date: 01/29/2023
4+
ms.date: 10/20/2025
55
ms.topic: how-to
66
ms.reviewer: Mravela
77
---
@@ -61,6 +61,7 @@ To create a snapshot report:
6161

6262
Cloud discovery uses the data in your traffic logs. The more detailed your log, the better visibility you get. Cloud discovery requires web-traffic data with the following attributes:
6363

64+
6465
- Date of the transaction
6566
- Source IP
6667
- Source user - highly recommended
@@ -77,9 +78,10 @@ Therefore, these attributes won't be shown in cloud discovery data for these log
7778
To successfully generate a cloud discovery report, your traffic logs must meet the following conditions:
7879

7980
1. [Data source is supported](set-up-cloud-discovery.md#supported-firewalls-and-proxies).
80-
2. Log format matches the expected standard format (format checked upon upload by the Log tool).
81-
3. Events aren't more than 90 days old.
82-
4. The log file is valid and includes outbound traffic information.
81+
1. Log format matches the expected standard format (format checked upon upload by the Log tool).
82+
1. Events aren't more than 90 days old.
83+
1. The log file is valid and includes outbound traffic information.
84+
1. Configure the appliance to forward only traffic logs. Including unrelated logs in the configuration can inflate the ingested traffic volume.
8385

8486
## Next steps
8587

defender-for-identity/deploy/prerequisites-sensor-version-3.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,6 @@ The Defender for Identity sensor v3.x:
1818
- Can't be activated on a server that has a Defender for Identity sensor V2.x already deployed.
1919
- Doesn't currently support VPN integration.
2020
- Doesn't currently support ExpressRoute.
21-
- Doesn't currently offer full functionality of health alerts, posture recommendations, security alerts or advanced hunting data.
2221

2322
## Licensing requirements
2423

defender-xdr/advanced-hunting-security-copilot.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,9 @@ ms.service: defender-xdr
66
ms.subservice: adv-hunting
77
f1.keywords:
88
- NOCSH
9-
ms.author: maccruz
10-
author: schmurky
9+
ms.author: pauloliveria
10+
author: poliveria
1111
ms.localizationpriority: medium
12-
manager: dansimp
1312
audience: ITPro
1413
ms.collection:
1514
- m365-security
@@ -46,7 +45,7 @@ Users with access to Security Copilot have access to this capability in advanced
4645
4746
## Try your first request
4847

49-
1. Open the **Advanced hunting** page from the navigation bar in Microsoft Defender XDR. The Security Copilot side pane for advanced hunting appears at the right hand side.
48+
1. Open the **Advanced hunting** page from the navigation bar in Microsoft Defender portal. The Security Copilot side pane for advanced hunting appears at the right hand side.
5049

5150
:::image type="content" source="/defender/media/advanced-hunting-security-copilot-pane-big.png" alt-text="Screenshot of the Copilot pane in advanced hunting." lightbox="/defender/media/advanced-hunting-security-copilot-pane-big.png":::
5251

0 commit comments

Comments
 (0)