Fix GitHub AuditLogs V3 DCR stream name mismatch in PollingConfig.json

[Copilot]

dcrConfig.streamName in PollingConfig.json was set to Custom-GitHubAuditLogs while the V3 DCR uses outputStream: Custom-GitHubAuditLogsV3_CL, causing ingestion to fail or land in the wrong stream/table.

Change(s):

• Solutions/GitHub/Data Connectors/GitHubAuditLogs_AzStorage/PollingConfig.json: updated dcrConfig.streamName from Custom-GitHubAuditLogs → Custom-GitHubAuditLogsV3_CL to align with the V3 DCR output stream

"dcrConfig": {
  "streamName": "Custom-GitHubAuditLogsV3_CL",
  ...
}

Reason for Change(s):

• Stream name mismatch between polling config and DCR outputStream breaks ingestion for the V3 GitHub Audit Logs connector

Version Updated:

• N/A — no Detections/Analytic Rule templates modified

Testing Completed:

• Config change verified by inspection against DCR outputStream value

Checked that the validations are passing and have addressed any issues that are present:

• Yes

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Aligns the GitHub Audit Logs (V3) polling configuration with the Data Collection Rule (DCR) outputStream to prevent ingestion failures or data landing in the wrong table.

Changes:

• Updated dcrConfig.streamName to match the V3 DCR output stream (Custom-GitHubAuditLogsV3_CL).