[FEATURE REQ] Call Correlation ID should be exposed in event data instead of subject #54864
Description
Library name
Azure.Communication.CallAutomation
Please describe the feature.
When handling Microsoft.Communication.RecordingFileStatusUpdated events in the Azure Call Automation client, the call correlation ID is currently hidden inside the subject field.
Example event payload:
{
"id": "5fbbdb97-c35e-412b-9775-e2f59c66d4c2",
"subject": "/recording/call/add67a69-debe-4998-9f92-5a0d8f6dc00c/serverCallId/.../recordingId/...",
"data": {
"recordingStorageInfo": { ... },
"recordingStartTime": "2026-01-07T11:13:04.7438177Z",
"recordingDurationMs": 76440,
"recordingId": "...",
"storageType": "ACS",
"sessionEndReason": "CallEnded"
},
"eventType": "Microsoft.Communication.RecordingFileStatusUpdated",
"dataVersion": "1.0",
"metadataVersion": "1",
"eventTime": "2026-01-07T11:14:24.133879Z"
}
Currently, the correlation ID is only accessible by parsing the subject string. This is error‑prone and inconsistent with other event models where identifiers are exposed directly in the data object.
Expected Behavior:
The event payload should include the call correlation ID (and ideally the server call ID) directly in the data section, making it easier to consume without string parsing.
Why this matters:
• Simplifies event handling for developers.
• Aligns with best practices of exposing identifiers in structured data.
• Reduces risk of parsing errors when subject format changes.
Environment:
• SDK: Azure.Communication.CallAutomation (v 1.5.0)
• Language: .NET
• Service: Azure Communication Services
Proposed Fix:
Expose CorrelationId (and optionally ServerCallId) as explicit fields in the data object of the event.