Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | GitHubAuditDefinitionV2 |
| Publisher | Microsoft |
| Used in Solutions | GitHub |
| Collection Method | CCF |
| Connector Definition Files | GitHubAuditLogs_ConnectorDefinition.json |
| DCR Definition Files | GitHubAuditLogs_DCR.json |
| CCF Configuration | GitHubAuditLogs_PollerConfig.json |
| CCF Capabilities | APIKey, Paging |
| Microsoft Learn | View on Learn |
The GitHub audit log connector provides the capability to ingest GitHub logs into Microsoft Sentinel. By connecting GitHub audit logs into Microsoft Sentinel, you can view this data in workbooks, use it to create custom alerts, and improve your investigation process.
Note: If you intended to ingest GitHub subscribed events into Microsoft Sentinel, please refer to GitHub (using Webhooks) Connector from "Data Connectors" gallery.
Volume limitation: GitHub limits this audit-log API to 1,750 requests/hour per user, source IP, and enterprise. With the current default of 30 events/page, the theoretical ceiling is about 13,100 events/15 minutes, before retries or competing requests. In Azure public cloud, we recommend GitHub Enterprise Audit Log (via Azure Storage) when your enterprise regularly generates 10,000+ audit and Git events/15 minutes, or connector health reports recurring GitHub rate-limit errors (HTTP 403/429) or ingestion delays keep increasing.
Azure Government Cloud: The Azure Storage connector is not supported in Azure Government Cloud. GitHub documentation states: "Audit log streaming to blob storage in Azure Government is not supported". The Azure Storage migration recommendation above does not apply in this cloud; the REST API connector remains subject to GitHub's API rate limits.
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
GitHubAuditLogsV2_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:
read:audit_log scope.⚠️ 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. Connect the GitHub Enterprise-level Audit Log to Microsoft Sentinel
Enable GitHub audit logs. Follow this guide to create or find your personal access token. 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.
Add Enterprise
When you click the "Add Enterprise" button in the portal, a configuration form will open. You'll need to provide:
Enter your Github Enterprise API URL and API key. Github Enterprise API URL formats:
https://api.github.com/enterprises/{enterprise}https://api.{subdomain}.ghe.com/enterprises/{enterprise}💡 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 · 📊