Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | AirlockDigitalPush |
| Publisher | Airlock Digital |
| Used in Solutions | AirlockDigital |
| Collection Method | CCF Push |
| Connector Definition Files | AirlockDigitalPush_ConnectorDefinition.json |
| DCR Definition Files | AirlockDigitalPush_DCR.json |
| CCF Configuration | AirlockDigitalPush_PollerConfig.json |
| CCF Capabilities | Push |
| Ingestion API | Log Ingestion API — CCF Push connectors use DCR-based Log Ingestion API |
The Airlock Digital Push connector streams execution history, server activity, and policy change logs into Microsoft Sentinel in near real time. It supports both self-hosted servers and Airlock Digital SaaS running v7.0 or higher. Events are pushed by Airlock's external logging feature as they occur, so there is no polling delay, and authentication uses a Microsoft Entra application. This is the recommended connector for Airlock Digital v7.0 and higher. For self-hosted servers older than v7.0, use the Airlock Digital (Poll) connector.
NOTE: Use one connector per Airlock Digital server. If the same server is collected by more than one Airlock Digital connector, duplicate data is populated in the tables.
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
AirlockDigitalExecutionHistories_CL |
? | ✓ | ? |
AirlockDigitalPolicyChanges_CL |
? | ✓ | ? |
AirlockDigitalServerActivities_CL |
? | ✓ | ? |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Resource Provider Permissions:
Custom Permissions:
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
1. Deploy the push resources
This step provisions the data collection rule, custom table, and Microsoft Entra application that Airlock uses to send logs into Microsoft Sentinel.
ℹ️ The Client Secret is never stored. It is shown only once, right after you select Deploy, and the connector page may clear it within a few seconds, so use the copy icon beside the field to copy it immediately. If you miss it, open Microsoft Entra ID > App registrations, select the app named Airlock Digital Log Push OAuth, go to Certificates & secrets, create a new client secret, and copy its value. There it stays visible until you leave that page. Deploy
2. Configure Airlock external logging
On your Airlock Digital server, go to Settings > Logging > External Logging and add a Microsoft Sentinel CEF - HTTP(S) log receiver using the values below.
TenantIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
ApplicationIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
ApplicationSecretNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
DataCollectionEndpointNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
DataCollectionRuleIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
Custom-AirlockDigital_CLBrowse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊