Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | AirlockDigitalSaas |
| Publisher | Airlock Digital |
| Used in Solutions | AirlockDigital |
| Collection Method | CCF |
| Connector Definition Files | AirlockDigitalSaas_ConnectorDefinition.json |
| DCR Definition Files | AirlockDigitalSaas_DCR.json |
| CCF Configuration | AirlockDigitalSaas_PollerConfig.json |
| CCF Capabilities | APIKey, Paging, POST |
The Airlock Digital SaaS connector periodically pulls execution history and server activity logs from the Airlock Digital SaaS API, authenticating with a user API key together with your directory and tenant identifiers. It is the polling connector for Airlock Digital's hosted SaaS offering, and it does not collect policy change logs. For self-hosted servers or Airlock Digital SaaS running v7.0 or higher, the Airlock Digital (Push) connector delivers events in near real time and also collects policy changes. 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 |
? | ✓ | ? |
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. Configure access to the Airlock Digital SaaS API
Set up API access in your Airlock Digital SaaS tenant before connecting.
Your server URL comes from your portal address: take https://portal.au.YourDomain.com/tenant/XYZ/dashboard and drop the portal. prefix and everything after the top-level domain, leaving https://au.YourDomain.com.
The user API key, directory ID and tenant ID are in Airlock Digital under User Menu > My Profile.
Logs are polled every five minutes.
2. Connect Airlock Digital SaaS instances to Microsoft Sentinel
This connector supports multiple simultaneous connections. Add one connection per Airlock Digital SaaS instance; each connection ingests the selected data types in parallel. Use the grid below to review existing connections or add a new one. Connector Management Interface
This section is an interactive interface in the Microsoft Sentinel portal that allows you to manage your data collectors.
📊 View Existing Collectors: A management table displays all currently configured data collectors with the following information:
➕ Add New Collector: Click the "Add new collector" button to configure a new data collector (see configuration form below).
🔧 Manage Collectors: Use the actions menu to delete or modify existing collectors.
💡 Portal-Only Feature: This configuration interface is only available when viewing the connector in the Microsoft Sentinel portal. You cannot configure data collectors through this static documentation.
Connect an Airlock Digital SaaS instance
Airlock Digital
When you click the "Add Connection" button in the portal, a configuration form will open. You'll need to provide:
Provide the SaaS URL, user API key, directory ID and tenant ID, then choose which data types to collect. Create a separate connection for each Airlock Digital SaaS instance.
💡 Portal-Only Feature: This configuration form is only available in the Microsoft Sentinel portal.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊