↳ GitHub sourceConnector

Egress Defend v2

Description

The Egress Defend audit connector ingests Egress Defend audit data into Microsoft Sentinel via the Logs Ingestion API (DCR-based). It pulls from the Egress Defend `V1/events` API and lands events in the `EgressDefend_v4_CL` table.

Declared author / publisher: Egress Software Technologies

Declared sources

Metadata from the source file. No dependencies inferred from KQL.

Data types

Declared permissions

Read and Write permissions on the Log Analytics workspace are required to enable the data connector.

Workspace

Workspace

Egress Defend API access

An Egress Defend API URL, customer domain and API key are required to ingest audit records into Microsoft Sentinel.

Connector instructions

Content published in the repository. Refer to the original file for all parameters.

Connect Egress Defend to Microsoft Sentinel

Enter your Egress Defend API URL, Egress domain and API key, then click Connect.

API URL

Domain name

API Key

Source provenance

GitHub

Displayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.

File: Solutions/Egress Defend/Data Connectors/EgressDefendAuditLogs_ccp/EgressDefendAudit_ConnectorDefinition.json ↗
Commit: 9800e51 ↗
Source identifier: EgressDefendAudit

Additional source files 2

Solutions/Egress Defend/Data Connectors/EgressDefendAuditLogs_ccp/EgressDefendAudit_ConnectorDefinition.jsonsource ↗Solutions/Egress Defend/Data/Solution_EgressDefend.jsonsolution-membership ↗

GSTEP / CATALOG TRACKING

Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC

GSTEP sync dates, separate from the source content’s publication dates.