You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/migrate-to-supported-api-solutions.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,11 +5,11 @@ ms.date: 05/19/2025
5
5
ms.topic: article
6
6
---
7
7
8
-
# Migrate from Defender for Cloud Apps SIEM Agent to Supported APIs
8
+
# Migrate from Defender for Cloud Apps SIEM agent to supported APIs
9
9
10
-
Transitioning from the legacy [Defender for Cloud Apps SIEM agent ](siem.md) to supported APIs enables continued access to enriched activities and alerts data. While the APIs may not have exact one-to-one mappings to the legacy Common Event Format (CEF) schema, they provide comprehensive and enhanced data enriched by integration across multiple Microsoft Defender workloads.
10
+
Transitioning from the legacy [Defender for Cloud Apps SIEM agent ](siem.md) to supported APIs enables continued access to enriched activities and alerts data. While the APIs might not have exact one-to-one mappings to the legacy Common Event Format (CEF) schema, they provide comprehensive, enhanced data through integration across multiple Microsoft Defender workloads.
11
11
12
-
## Recommended APIs for Migration
12
+
## Recommended APIs for migration
13
13
14
14
> To ensure continuity and access to data currently available through Microsoft Defender for Cloud Apps SIEM agents, we recommend transitioning to the following supported APIs:
15
15
>
@@ -30,16 +30,16 @@ The table below compares the legacy SIEM agent’s CEF fields to the nearest equ
30
30
|`rt`| Activity or alert timestamp |`createdDateTime`|`createdDateTime` / `lastUpdateDateTime` / `resolvedDateTime`|
|`destinationServiceName`| Originating app (for example, SharePoint, Box) |`CloudAppEvents > Application`| See `cloudApplicationEvidence` resource type |
34
+
|`cs<X>Label`, `cs<X>`| Dynamic fields (for example, target user, object) |`Entities`, `Evidence`, `additionalData`, `ActivityObjects`| Various `alertEvidence` resource types |
0 commit comments