Zoom Reports CCF Connector: Table Migration From Legacy Zoom_CL to ZoomV2_CL Schema

What Changed

The Zoom Reports CCF connector has been migrated to use a new table schema and naming convention, moving from Zoom_CL to ZoomV2_CL with standardized field names.

Data Connector Impact

Table and Stream Changes

• Output table: Zoom_CL → ZoomV2_CL
• DCR streams: Custom-ZoomReportsGeneral_CL → Custom-ZoomReportsV2General_CL
• DCR name: ZoomReportsDCR → ZoomReportsV2DCR

Schema Normalization

The DCR transform KQL now maps to normalized field names without legacy suffix conventions:

• event_type_s → EventType
• event_name_s → EventName
• email_s → Email
• user_name_s → UserName
• meeting_minutes_d → MeetingMinutes
• ip_address_s → IpAddress
• Added new CustomAttributes dynamic field for extensibility

Deployment Coexistence

This change eliminates table conflicts between the CCF connector and legacy Azure Function App deployments. Organizations can now run both connectors simultaneously without schema conflicts, with the Function App continuing to use Zoom_CL while the CCF connector uses ZoomV2_CL.

Detection Surface Impact

Existing queries targeting Zoom_CL will not automatically work with the new CCF connector data. Organizations migrating from Function App to CCF deployments must update:

• Analytic Rules referencing Zoom_CL table
• Hunting queries with legacy field names (event_type_s, email_s, etc.)
• Workbooks and dashboards showing Zoom activity

The connector UI now provides updated KQL examples using the new ZoomV2_CL table and normalized field names.

Affected Files

Solutions/ZoomReports/Data Connectors/ZoomReports_ccf/ConnectorDefinition.json
Solutions/ZoomReports/Data Connectors/ZoomReports_ccf/DCR.json
Solutions/ZoomReports/Data Connectors/ZoomReports_ccf/PollingConfig.json
(packaging artefacts: 3.0.7.zip, ReleaseNotes.md, Solution_ZoomReports.json, mainTemplate.json)