All integrationsSecurity

Microsoft Sentinel

Work Microsoft Sentinel incidents from your workflows: list, create, assign, comment on, add tasks to and close incidents, read their alerts and entities, run playbooks, keep watchlists and threat intelligence up to date, and start a workflow when an incident opens or changes.

actions
24
triggers
8

Triggers

Start a workflow when something happens in Microsoft Sentinel.

  • New incidentRuns when Microsoft Sentinel opens a new incident.
  • Incident updatedRuns when a Microsoft Sentinel incident changes: its status, owner, severity, labels, alerts or comments.
  • Incident status changedRuns when a Microsoft Sentinel incident's status changes, such as when it is closed.
  • Incident assignedRuns when a Microsoft Sentinel incident is assigned to someone.
  • Incident severity changedRuns when a Microsoft Sentinel incident's severity changes.
  • New watchlist itemRuns when a row is added to a Microsoft Sentinel watchlist.
  • New threat indicatorRuns when a threat indicator is added to Microsoft Sentinel, from a feed, a person or a workflow.
  • Analytics rule turned offRuns when a Microsoft Sentinel analytics rule is turned off, by a person or by Sentinel after the rule kept failing.

Actions

Steps a workflow can run in Microsoft Sentinel.

  • List incidentsIncidents in the workspace, newest first, filtered by status, severity and when they were created.
  • Get incidentOne incident: its title, severity, status, owner, labels, counts of alerts and comments, and its link in the portal.
  • Create incidentOpen an incident by hand, for something a workflow found outside Sentinel's own analytics rules.
  • Update incidentChange an incident's title, description, severity or status, assign or unassign it, or add and remove labels. Only what you set is changed. To close it, use 'Close incident'.
  • Close incidentClose an incident with the reason, as Sentinel requires.
  • Delete incidentDelete an incident, with its comments and tasks. Its alerts stay in the workspace. This cannot be undone.
  • List incident alertsThe alerts grouped into an incident, with what each found.
  • List incident entitiesThe accounts, hosts, IP addresses, files and other entities an incident involves.
  • List incident commentsAn incident's comments, newest first.
  • Add incident commentAdd a comment to an incident, such as what a workflow found or did.
  • List incident tasksAn incident's tasks, and how many are still to do.
  • Add incident taskAdd a task to an incident's checklist.
  • Update incident taskMark an incident's task done or to do, or change its wording.
  • Run playbook on incidentStart a playbook (a Logic App with a Microsoft Sentinel incident trigger) on an incident. Sentinel starts it and the step does not wait for it to finish.
  • List watchlistsThe workspace's watchlists, with each one's search key column.
  • Create watchlistMake a watchlist (a lookup table your queries and rules can use), empty or filled from CSV. The step stops rather than replace a watchlist that has the alias.
  • Delete watchlistDelete a watchlist and all its items. This cannot be undone.
  • List watchlist itemsThe rows of a watchlist, each with its values by column.
  • Add watchlist itemAdd a row to a watchlist, such as an IP address to block. It needs a value for the watchlist's search key column.
  • Delete watchlist itemTake a row off a watchlist.
  • Create threat indicatorAdd an IP address, domain, URL, email address or file hash to Sentinel's threat intelligence, so analytics rules can match it.
  • Search threat indicatorsFind threat indicators by keyword, type, source and confidence, most recently changed first.
  • Delete threat indicatorDelete a threat indicator. This cannot be undone.
  • List analytics rulesThe analytics rules that raise alerts and incidents, and whether each is turned on.

Automate Microsoft Sentinel with Lodol.

Connect Microsoft Sentinel, then hand Lodol the job in Slack, Claude or ChatGPT.

We’re letting people in a few at a time.