↳ GitHub sourceConnector
Atlassian Organization Audit Events (via Codeless Connector Framework)
Description
The Atlassian Organization Audit Events data connector provides the capability to ingest organization audit events from Atlassian Cloud into Microsoft Sentinel through the Polling API. This connector enables comprehensive security monitoring and compliance auditing across all Atlassian Cloud products including Jira (Software/Service Desk/Core), Confluence, Bitbucket, Trello, Opsgenie, Statuspage, and Loom. The connector ingests audit events covering user management, authentication activities, group changes, product access modifications, administrative actions, and policy changes. With 180 days of data retention in Atlassian Cloud, this connector provides visibility into user access granted/revoked, authentication failures and successes, MFA configuration changes, API token management, group membership changes, product license assignments, organization policy updates, and domain verification activities. The connector uses API Key authentication with read-only OAuth scope (read:events:admin) and is optimized for continuous polling with cursor-based pagination. This connector is built on Microsoft Sentinel Codeless Connector Platform and supports DCR-based ingestion time transformations for optimized query performance. Refer to Atlassian Organization Events API documentation for more information.
- Declared status
- 1
- Declared author / publisher
- Atlassian
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Data types
Declared permissions
Read and Write permissions are required.
Workspace
Workspace
Atlassian Organization Events API access
An API key with the read-only `read:events:admin` OAuth scope is required to read organization audit events. See the [Atlassian Organization Events API documentation](https://developer.atlassian.com/cloud/admin/organization/rest/) for more information.
Connector instructions
Content published in the repository. Refer to the original file for all parameters.
Prerequisites
Before setting up this connector, ensure you have the following:
1. Create API Key in Atlassian
Follow these steps to create an API key with the required permissions:
2. Get Your Organization ID
Your Organization ID is required to connect to the Atlassian API:
3. Connect to Microsoft Sentinel
Add one connection per Atlassian organization (tenant). Each connection is identified by a unique Connection Alias and may target a different organization or API base URL, so you can ingest events from multiple Atlassian organizations side by side.
Add Connection
Configure Atlassian Connection
Connection Details
Enter the details for this Atlassian organization.
Connection Alias
Enter a unique alias to identify this Atlassian connection. **Important:** Use a different alias for each connection. To update an existing connection, delete it and recreate it with the same alias.
Atlassian API Base URL
Enter the API base URL for this tenant without a trailing slash (e.g. `https://api.atlassian.com`). Use the region-specific base URL if your organization is assigned one.
Organization ID
API Key
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
9800e51↗- Source identifier
AtlassianAuditEventsConnector
GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC