What Changed

The Atlassian Jira Audit connector has been rebranded from “Atlassian Jira Audit (using REST API)” to “Atlassian Jira Audit (via Codeless Connector Framework)” to align with current Microsoft Sentinel connector terminology standards. This is a pure branding change with no functional modifications to the connector logic or ingestion behavior.

Security Impact

No security implications — this is a display name update only. The connector continues to ingest Jira audit events through the same CCF mechanism as before. All detection rules, queries, and data ingestion remain unaffected.

The accompanying API version updates in ARM templates (from 2023-04-01-preview to 2025-01-01-preview) are standard Microsoft.SecurityInsights API versioning maintenance with no functional changes to the connector behavior.

Affected Files

Solutions/AtlassianJiraAudit/Data Connectors/JiraAuditAPISentinelConnector_ccpv2/JiraAudit_DataConnectorDefinition.json
Solutions/AtlassianJiraAudit/Data Connectors/JiraAuditAPISentinelConnector_ccpv2/azuredeploy_JiraAudit_poller_connector.json
Solutions/AtlassianJiraAudit/Playbooks/Sync-CommentsFunctionApp/azuredeploy.json
(packaging artefacts: 3.0.5.zip, ReleaseNotes.md, createUiDefinition.json, mainTemplate.json)