Description
The [Airlock Digital](https://www.airlockdigital.com/) **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.
- Declared status
- 1
- Declared author / publisher
- Airlock Digital
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Data types
Declared permissions
Read and Write permissions are required.
Workspace
Workspace
Microsoft Entra
Permission to create an app registration in Microsoft Entra ID. Typically requires the Application Developer role or higher.
Microsoft Azure
Permission to assign the Monitoring Metrics Publisher role on the data collection rule. Typically requires Owner or User Access Administrator.
Connector instructions
Content published in the repository. Refer to the original file for all parameters.
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.
Tenant ID
Application (Client) ID
Client Secret
Data Collection Endpoint URI
DCR Immutable ID
Stream Name
Related content
Links established from declared identifiers and solution manifests.
Source provenance
GitHubDisplayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.
- Commit
7ca9800↗- Source identifier
AirlockDigitalPush
GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC