You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Transitioning to Microsoft's unified SecOps platform
2
+
title: Moving to Microsoft's unified SecOps platform
3
3
description: Learn about the different security roles involved in transitioning to Microsoft's unified SecOps platform from Microsoft Sentinel in the Azure portal.
4
4
ms.service: unified-secops-platform
5
5
ms.author: bagol
@@ -13,17 +13,17 @@ ms.topic: conceptual
13
13
# customer intent: As a security professional, I want to understand the benefits and process of transitioning to Microsoft's unified SecOps platform so I can effectively plan my organization's migration from the standalone Microsoft Sentinel portal before its decommissioning.
14
14
---
15
15
16
-
# Transition to Microsoft's unified SecOps platform
16
+
# Moving to Microsoft's unified SecOps platform
17
17
18
18
Microsoft's unified security operations (SecOps) platform provides a single platform for end-to-end security operations (SecOps). This platform combines services like [Microsoft Defender XDR](/defender-xdr/microsoft-365-defender), [Microsoft Sentinel](/azure/sentinel/overview), [Microsoft Security Exposure Management](/security-exposure-management/microsoft-security-exposure-management), and [Microsoft Security Copilot](/copilot/security/microsoft-security-copilot) within the Microsoft Defender portal. The unified SecOps platform provides multi-tenant and multi-workspace capabilities, a single incident queue, alert correlation, and automatic attack disruption to ensure streamlined workflows and enhances security operations efficiency.
19
19
20
-
Starting in May 2026, customers using the Microsoft Sentinel experience in the Azure portal will be redirected to the unified SecOps platform in the Microsoft Defender portal. Microsoft Sentinel in the Azure portal will be decommissioned on July 1, 2026. To prepare for this change, we recommend that customers that are still using the Microsoft Sentinel experience in the Azure portal proactively transition to Microsoft's unified SecOps platform in the Microsoft Defender portal.
20
+
Starting in May 2026, customers using the Microsoft Sentinel experience in the Azure portal will be redirected to the unified SecOps platform in the Microsoft Defender portal. Microsoft Sentinel in the Azure portal will be decommissioned on July 1, 2026. To prepare for this change, we recommend that customers that are still using the Microsoft Sentinel experience in the Azure portal proactively move to Microsoft's unified SecOps platform in the Microsoft Defender portal.
21
21
22
22
For more information, see the relevant documentation for each feature and [Capability differences between portals](/azure/sentinel/microsoft-sentinel-defender-portal##capability-differences-between-portals).
23
23
24
-
## Benefits of transitioning to the unified SecOps platform
24
+
## Benefits of moving to unified SecOps
25
25
26
-
Transitioning to the unified SecOps platform offers the following benefits, and more:
26
+
Moving to the unified SecOps platform offers the following benefits, and more:
@@ -37,115 +37,50 @@ Transitioning to the unified SecOps platform offers the following benefits, and
37
37
38
38
For more information, see [Microsoft Sentinel in the Microsoft Defender portal](/azure/sentinel/microsoft-sentinel-defender-portal).
39
39
40
-
## Transition to unified SecOps as a security architect
40
+
## Move to unified SecOps as a security architect
41
41
42
-
The following content is relevant for security architects on a SecOps team that's transitioning from Microsoft Sentinel in the Azure portal to unified SecOps in the Defender portal:
42
+
The following content is relevant for security architects on a SecOps team that's moving from Microsoft Sentinel in the Azure portal to unified SecOps in the Defender portal:
|**Access**| - [Plan roles and permissions](overview-plan.md#plan-roles-and-permissions), including role-based access control (RBAC) <br> - [Configure roles and permissions](overview-deploy.md#configure-roles-and-permissions) <br><br> The minimal required permission for an analyst to view Microsoft Sentinel data is to delegate permissions for the Azure RBAC Sentinel Reader role. These permissions are also applied to the unified portal. Without these permissions, the Microsoft Sentinel navigation menu isn't available on the unified portal, despite the analyst having access to the Microsoft Defender portal. <br><br>A best practice is to have all Microsoft Sentinel related resources in the same Azure resource group, then delegate Microsoft Sentinel role permissions (like the Sentinel Reader role) at the resource group level that contains the Microsoft Sentinel workspace. By doing this, the role assignment applies to all the resources that support Microsoft Sentinel. |
48
+
|**Multiple workspaces and tenants**| - [Multiple Microsoft Sentinel workspaces in the Defender portal](/azure/sentinel/prepare-multiple-workspaces) <br>- [Extend Microsoft Sentinel across workspaces and tenants](/azure/sentinel/extend-sentinel-across-workspaces-tenants) <br> - [Microsoft Defender multitenant management](mto-overview.md)|
49
+
|**Log tiering and retention**| - [When to use auxiliary logs in Microsoft Sentinel](/azure/sentinel/basic-logs-use-cases) <br>- [Log retention plans in Microsoft Sentinel](/azure/sentinel/log-plans)<br> - [Set up a table with the Auxiliary plan for low-cost data ingestion and retention in your Log Analytics workspace](/azure/azure-monitor/logs/create-custom-table-auxiliary) <br> - [Microsoft Sentinel in the Defender portal: threat management](/azure/sentinel/microsoft-sentinel-defender-portal#threat-management) <br><br>Microsoft Sentinel classifies security data as primary security data and secondary security data. For primary security data, which you want to monitor closely, we recommend the analytic tier. For secondary security data, we recommend auxiliary. Both types of data are accessible for queries in the **Advanced hunting** page in the Defender portal. |
47
50
48
-
-[Plan roles and permissions](overview-plan.md#plan-roles-and-permissions), including role-based access control (RBAC)
49
-
-[Configure roles and permissions](overview-deploy.md#configure-roles-and-permissions)
50
-
51
-
-**Multiple workspaces and tenants**:
51
+
## Move to unified SecOps as a security engineer
52
52
53
-
-[Multiple Microsoft Sentinel workspaces in the Defender portal](/azure/sentinel/prepare-multiple-workspaces)
54
-
-[Extend Microsoft Sentinel across workspaces and tenants](/azure/sentinel/extend-sentinel-across-workspaces-tenants)
The following content is relevant for security engineers on a SecOps team that's moving from Microsoft Sentinel in the Azure portal to unified SecOps in the Defender portal:
56
54
57
-
-**Log tiering and retention**:
58
55
59
-
Microsoft Sentinel classifies security data as primary security data and secondary security data. For primary security data, which you want to monitor closely, we recommend the analytic tier. For secondary security data, we recommend auxiliary. Both types of data are accessible for queries in the **Advanced hunting** page in the Defender portal.
56
+
| Feature | Details |
57
+
|---------|---------|
58
+
|**Data collection**| - [Microsoft Sentinel data connectors](/azure/sentinel/connect-data-sources?tabs=defender-portal) <br>- Experience in the Defender portal: [Visibility of connectors used by the unified security operations platform](/azure/sentinel/microsoft-sentinel-defender-portal), [Defender for Cloud](/azure/sentinel/microsoft-sentinel-defender-portal), and [DLP data](/azure/sentinel/microsoft-sentinel-defender-portal)|
59
+
|**Automation**|[Automation in the Microsoft Defender portal](/azure/sentinel/automation/automation#automation-in-the-microsoft-defender-portal)|
60
+
|**Ecosystem**| Distribute content across workspaces using one of the following methods: <br> - [Deploy content as code from your repository](/azure/sentinel/ci-cd)<br> - [Microsoft Defender multitenant management](mto-overview.md)|
61
+
|**SOC optimization**|[Optimize your security operations](/azure/sentinel/soc-optimization/soc-optimization-access?toc=%2Funified-secops-platform%2Ftoc.json&bc=%2Funified-secops-platform%2Fbreadcrumb%2Ftoc.json&tabs=defender-portal)|
62
+
|**APIs**| - [Microsoft Sentinel in the Defender portal: Capability differences between portals](/azure/sentinel/microsoft-sentinel-defender-portal) <br>- [Microsoft Sentinel REST API reference](/rest/api/securityinsights/)|
60
63
61
-
-[When to use auxiliary logs in Microsoft Sentinel](/azure/sentinel/basic-logs-use-cases)
62
-
-[Log retention plans in Microsoft Sentinel](/azure/sentinel/log-plans)
63
-
-[Set up a table with the Auxiliary plan for low-cost data ingestion and retention in your Log Analytics workspace](/azure/azure-monitor/logs/create-custom-table-auxiliary)
64
-
-[Microsoft Sentinel in the Defender portal: threat management](/azure/sentinel/microsoft-sentinel-defender-portal#threat-management)
64
+
<!--add bookmark for API related information-->
65
+
<!--add bookmarks for data connector specifics, also add content there re mdc and dlp items. that's on ed-->
66
+
## Move to unified SecOps as a security analyst or manager
65
67
66
-
## Transition to unified SecOps as a security engineer
68
+
The following content is relevant for security analysts or security managers on a SecOps team that's moving from Microsoft Sentinel in the Azure portal to unified SecOps in the Defender portal:
67
69
68
-
The following content is relevant for security engineers on a SecOps team that's transitioning from Microsoft Sentinel in the Azure portal to unified SecOps in the Defender portal:
70
+
| Feature | Details |
71
+
|-------------|-------------|
72
+
|**Incident and alert management**|[Alert correlation and incident merging in the Microsoft Defender portal](/defender-xdr/alerts-incidents-correlation?view=o365-worldwide) <br><br> The streamlined incident triage workflow in the Defender portal may require some retraining of analysts and updates to existing SOC processes. For example, incidents may now contain multiple cross-security domain alerts, reducing the number of required analysts and potentially combining tier 1 and tier 2 analysts. |
73
+
|**Attack disruption**| - [Automatic attack disruption](/defender-xdr/automatic-attack-disruption) <br> - [Details and results of an automatic attack disruption action](/defender-xdr/autoad-results) <br> - [Exclude assets from automated responses](/defender-xdr/automatic-attack-disruption-exclusions)|
74
+
|**Advanced hunting**| - [Advanced hunting with Microsoft Sentinel data in Microsoft Defender](/defender-xdr/advanced-hunting-microsoft-defender) <br> - [Microsoft Sentinel in the Microsoft Defender portal](/azure/sentinel/microsoft-sentinel-defender-portal)|
75
+
|**Entities and user and entity behavior analytics (UEBA)**| - [Advanced threat detection with UEBA](/azure/sentinel/identify-threats-with-entity-behavior-analytics) <br> - [Enable UEBA](/azure/sentinel/enable-entity-behavior-analytics?tabs=defender) <br> - [Microsoft Sentinel UEBA reference](/azure/sentinel/ueba-reference) <br> - [Investigate users](/defender-xdr/investigate-users) <br> - [Device entity pages](/defender-xdr/entity-page-device) <br> - [Global search](/defender-xdr/microsoft-365-defender-portal#global-search)|
76
+
|**Case management**|[Manage cases in Microsoft's unified security operations platform](/unified-secops-platform/cases-overview)|
|**Threat intelligence**| Extra features are available in the Defender portal with unified SecOps, including: <br> - [Threat analytics](/defender-xdr/threat-analytics) <br> - [Intel profiles](https://techcommunity.microsoft.com/blog/defenderthreatintelligence/whats-new-intel-profiles-deliver-crucial-information-context-about-threats/3780076) <br> - [Searching and pivoting with the Intel explorer](/defender/threat-intelligence/searching-and-pivoting) <br> - [Intel projects](/defender/threat-intelligence/using-projects) <br> For more information, see [Microsoft Sentinel in the Defender portal](/azure/sentinel/microsoft-sentinel-defender-portal?toc=%2Funified-secops-platform%2Ftoc.json&bc=%2Funified-secops-platform%2Fbreadcrumb%2Ftoc.json). |
79
+
|**Visualization and reporting with workbooks**| - [Visualize and monitor your data by using workbooks with Microsoft Sentinel](/azure/sentinel/monitor-your-data?tabs=defender-portal) <br> - [Azure Workbooks](/azure/azure-monitor/visualize/workbooks-overview) <br> - [Microsoft Sentinel in the Defender portal](/azure/sentinel/microsoft-sentinel-defender-portal?toc=%2Funified-secops-platform%2Ftoc.json&bc=%2Funified-secops-platform%2Fbreadcrumb%2Ftoc.json)|
69
80
70
-
-**Data collection**:
81
+
<!--do we have nothing in docs about intel profiles?-->
82
+
<!--add bookmark for workbooks related information-->
71
83
72
-
-[Microsoft Sentinel data connectors](/azure/sentinel/connect-data-sources?tabs=defender-portal)
73
-
- Experience in the Defender portal:
74
-
-[Visibility of connectors used by the unified security operations platform](/azure/sentinel/microsoft-sentinel-defender-portal)
75
-
-[Defender for Cloud](/azure/sentinel/microsoft-sentinel-defender-portal)<!--add bookmarks for data connector specifics, also add content there re mdc and dlp items. that's on ed-->
76
-
-[DLP data](/azure/sentinel/microsoft-sentinel-defender-portal)<!--add bookmarks for data connector specifics, also add content there re mdc and dlp items. that's on ed-->
77
-
78
-
-**Automation**: [Automation in the Microsoft Defender portal](/azure/sentinel/automation/automation#automation-in-the-microsoft-defender-portal)
79
-
80
-
-**Ecosystem**: Distribute content across workspaces using one of the following methods:
81
-
82
-
-[Deploy content as code from your repository](/azure/sentinel/ci-cd)
-**SOC optimization**: [Optimize your security operations](/azure/sentinel/soc-optimization/soc-optimization-access?toc=%2Funified-secops-platform%2Ftoc.json&bc=%2Funified-secops-platform%2Fbreadcrumb%2Ftoc.json&tabs=defender-portal)
86
-
87
-
-**APIs**
88
-
89
-
-[Microsoft Sentinel in the Defender portal: Capability differences between portals](/azure/sentinel/microsoft-sentinel-defender-portal)<!--add bookmark for API related information-->
90
-
-[Microsoft Sentinel REST API reference](/rest/api/securityinsights/)
91
-
92
-
## Transition to unified SecOps as a security analyst or manager
93
-
94
-
The following content is relevant for security analysts or security managers on a SecOps team that's transitioning from Microsoft Sentinel in the Azure portal to unified SecOps in the Defender portal:
95
-
96
-
-**Incident and alert management**
97
-
98
-
The streamlined incident triage workflow in the Defender portal may require some retraining of analysts and updates to existing SOC processes. For example, incidents may now contain multiple cross-security domain alerts, reducing the number of required analysts and potentially combining tier 1 and tier 2 analysts.
99
-
100
-
-[Alert correlation and incident merging in the Microsoft Defender portal](/defender-xdr/alerts-incidents-correlation?view=o365-worldwide)
-[Intel profiles](https://techcommunity.microsoft.com/blog/defenderthreatintelligence/whats-new-intel-profiles-deliver-crucial-information-context-about-threats/3780076)<!--do we have nothing in docs about this?-->
139
-
-[Searching and pivoting with the Intel explorer](/defender/threat-intelligence/searching-and-pivoting)
For more information, see [Microsoft Sentinel in the Defender portal](/azure/sentinel/microsoft-sentinel-defender-portal?toc=%2Funified-secops-platform%2Ftoc.json&bc=%2Funified-secops-platform%2Fbreadcrumb%2Ftoc.json).
143
-
144
-
-**Visualization and reporting with workbooks**:
145
-
146
-
-[Visualize and monitor your data by using workbooks with Microsoft Sentinel](/azure/sentinel/monitor-your-data?tabs=defender-portal)
-[Microsoft Sentinel in the Defender portal](/azure/sentinel/microsoft-sentinel-defender-portal?toc=%2Funified-secops-platform%2Ftoc.json&bc=%2Funified-secops-platform%2Fbreadcrumb%2Ftoc.json)<!--add bookmark for workbooks related information-->
0 commit comments