Secops - Security incident response integration with Microsoft Azure Sentinel - Security Incidents that are being closed in Sentinel One, are not being closed in ServiceNow automatically.Issue When a Security Incident is closed in Sentinel the corresponding incident is not automatically closed within ServiceNow Security Incident Response.ReleaseAll version of Microsoft Azure Sentinel Incident Ingestion Integration For Security Operations CauseIn the current design of the integration "Only update of "Incident Status in sentinel whenever corresponding security incident is opened or closed in ServiceNow" is possible.Comments synchronisation is bidirectional both from "ServiceNow(work notes) to sentinel(comments)" and "sentinel(comments) to ServiceNow(work notes)" based in profile configuration." See the Key Features for this app in the Store This integration includes the following key features: Discover Microsoft Azure Sentinel incidents that are candidates for security incidents and automate the creation of security incidents.Mapping of Microsoft Azure Sentinel incident and entity fields to SIR security incident fields.Filtering of Microsoft Azure Sentinel incidents.Aggregation of similar incidents to existing open security incidents so that you don't have to create duplicate security incidents.Automatic Microsoft Azure Sentinel incident status update for SIR security incident creation and closure.Scheduled ingestion of incidents that create security incidents periodically.Synchronization of Microsoft Azure Sentinel incident comments with SIR Work notes.ResolutionThis behavior is consistent with the current system design. As such, there are no available solutions or workarounds to modify this functionality at present.