Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Attention: All Microsoft Sentinel features will be officially retired in Azure in China regions on August 18, 2026 per the announcement posted by 21Vianet.
Best practice guidance is provided throughout the technical documentation for Microsoft Sentinel. This article highlights some key guidance to use when deploying, managing, and using Microsoft Sentinel.
Setting up Microsoft Sentinel
Start with the deployment guide for Microsoft Sentinel. The deployment guide covers the high level steps to plan, deploy, and fine-tune your Microsoft Sentinel deployment. From that guide, select the provided links to find detailed guidance for each stage in your deployment.
Microsoft security service integrations
Microsoft Sentinel is empowered by the components that send data to your workspace, and is made stronger through integrations with other Microsoft services. Any logs ingested into products, such as Microsoft Defender for Endpoint, and Microsoft Defender for Identity, allow these services to create detections, and in turn provide those detections to Microsoft Sentinel. Logs can also be ingested directly into Microsoft Sentinel to provide a fuller picture for events and incidents.
More than ingesting alerts and logs from other sources, Microsoft Sentinel also:
- Uses the information it ingests with machine learning that allows for better event correlation, alert aggregation, anomaly detection, and more.
- Builds and presents interactive visuals via workbooks, showing trends, related information, and key data used for both admin tasks and investigations.
- Runs playbooks to act on alerts, gathering information, performing actions on items, and sending notifications to various platforms.
- Integrates with partner platforms, such as ServiceNow and Jira, to provide essential services for SOC teams.
For more information about integrating data from other services or providers, see Microsoft Sentinel data connectors.
Incident management and response
The following image shows recommended steps in an incident management and response process.
The following table provides high-level descriptions for how to use Microsoft Sentinel features for incident management and response. For more information, see Investigate incidents with Microsoft Sentinel.
| Capability | Best practice |
|---|---|
| Incidents | Any generated incidents are displayed on the Incidents page, which serves as the central location for triage and early investigation. The Incidents page lists the title, severity, and related alerts, logs, and any entities of interest. Incidents also provide a quick jump into collected logs and any tools related to the incident. |
| Investigation graph | The Incidents page works together with the Investigation graph, an interactive tool that allows users to explore and dive deep into an alert to show the full scope of an attack. Users can then construct a timeline of events and discover the extent of a threat chain. Discover key entities, such as accounts, URLs, IP address, host names, activities, timeline, and more. Use this data to understand whether you have a false positive on hand, in which case you can close the incident directly. If you discover that the incident is a true positive, take action directly from the Incidents page to investigate logs, entities, and explore the threat chain. After you identified the threat and created a plan of action, use other tools in Microsoft Sentinel and other Microsoft security services to continue investigating. |
| Information visualization | To visualize and get analysis of what's happening on your environment, first, take a look at the Microsoft Sentinel overview dashboard to get an idea of the security posture of your organization. In addition to information and trends on the Microsoft Sentinel overview page, workbooks are valuable investigative tools. For example, use the Investigation Insights workbook to investigate specific incidents together with any associated entities and alerts. This workbook enables you to dive deeper into entities by showing related logs, actions, and alerts. |
| Threat hunting | While investigating and searching for root causes, run built-in threat hunting queries and check results for any indicators of compromise. For more information, see Threat hunting in Microsoft Sentinel. During an investigation, or after having taken steps to remediate and eradicate the threat, use livestream. Livestream allows you to monitor, in real time, whether there are any lingering malicious events, or if malicious events are still continuing. |
| Entity behavior | Entity behavior in Microsoft Sentinel allows users to review and investigate actions and alerts for specific entities, such as investigating accounts and host names. For more information, see: - Enable User and Entity Behavior Analytics (UEBA) in Microsoft Sentinel - Investigate incidents with UEBA data - Microsoft Sentinel UEBA enrichments reference |
| Watchlists | Use a watchlist that combines data from ingested data and external sources, such as enrichment data. For example, create lists of IP address ranges used by your organization or recently terminated employees. Use watchlists with playbooks to gather enrichment data, such as adding malicious IP addresses to watchlists to use during detection, threat hunting, and investigations. During an incident, use watchlists to contain investigation data, and then delete them when your investigation is done to ensure that sensitive data doesn't remain in view. For more information, see Watchlists in Microsoft Sentinel. |