Microsoft Sentinel
Cloud and workloadsMigrate IBM Security QRadar SOAR Automation to Microsoft Sentinel
In brief
The guide updates its title and metadata, improves section headings, adds navigation anchors, and clarifies the workflow-stage and component mapping guidance between QRadar SOAR and Microsoft Sentinel.
What Defender admins need to know
Administrators migrating QRadar SOAR workflows can use the clearer structure and mapping guidance to find relevant migration information more easily.
Summaries are generated from the documentation change itself.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
title: Migrate IBM Security QRadar SOAR automationAutomation to Microsoft Sentinel
description: Learn how to identify SOAR use cases, and how to migrate your QRadar SOAR automation to Microsoft Sentinel.
author: EdB-MSFT
ms.author: edbaynash
ms.topic: how-to
ms.date: 06/15/07/01/2026
ai-usage: ai-assisted
ms.custom: msecd-doc-authoring-10141016
#Customer intent: As a security engineer, I want to migrate my SOAR automation from IBM Security QRadar to Microsoft Sentinel so that I can streamline incident response and enhance threat remediation using Microsoft Sentinel's advanced automation capabilities.
Microsoft Sentinel provides Security Orchestration, Automation, and Response (SOAR) capabilities with automation rules and playbooks. Automation rules automate incident handling and response, and playbooks run predetermined sequences of actions to response and remediate threats. This article discusses how to identify SOAR use cases, and how to migrate your IBM Security QRadar SOAR automation to Microsoft Sentinel.
Automation rules simplify complex workflows for your incident orchestration processes, and allow you to centrally manage your incident handling automation.
With automation rules, you can:
- Perform simple automation tasks without necessarily using playbooks. For example, you can assign, tag incidents, change status, and close incidents.
- Automate responses for multiple analytics rules at once.
- Control the order of actions that are executed.
- Run playbooks for those cases where more complex automation tasks are necessary.
Identify SOAR use cases
Here’s what you need to think about when migrating SOAR use cases from IBM Security QRadar SOAR.
- Use case quality
.: Choose good use cases for automation. Use cases should be based on procedures that are clearly defined, with minimal variation, and a low false-positive rate. Automation should work with efficient use cases. - Manual intervention
.: Automated response can have wide ranging effects and high impact automations should have human input to confirm high impact actions before they’re taken. - Binary criteria
.: To increase response success, decision points within an automated workflow should be as limited as possible, with binary criteria. Binary criteria reduces the need for human intervention, and enhances outcome predictability. - Accurate alerts or data
.: Response actions are dependent on the accuracy of signals such as alerts. Alerts and enrichment sources should be reliable. Microsoft Sentinel resources such as watchlists and reliable threat intelligence can enhance reliability. - Analyst role
.: While automation where possible is great, reserve more complex tasks for analysts, and provide them with the opportunity for input into workflows that require validation. In short, response automation should augment and extend analyst capabilities.
Migrate SOAR workflowworkflows to Microsoft Sentinel
This section shows how key SOAR concepts in IBM Security QRadar SOAR translate to Microsoft Sentinel components. TheThis section also provides general guidelines for how to migrate each step or component in the SOAR workflow.
The following diagram labels four numbered workflow stages. The table after the diagram maps each numbered stage from QRadar SOAR to its Microsoft Sentinel equivalent.
:::image type="content" source="media/migration-qradar-automation/qradar-sentinel-soar-workflow.png" alt-text="Diagram displaying the QRadar and Microsoft Sentinel SOAR workflows." lightbox="media/migration-qradar-automation/qradar-sentinel-soar-workflow.png" border="false":::
|3 |Execute selected workflows. |Execute other playbooks according to tags applied by playbooks that were executed previously. | |4 |Post data to message destinations. |Execute code snippets using inline actions in Logic Apps. |
Map QRadar SOAR components to Microsoft Sentinel capabilities
Review which Microsoft Sentinel or Azure Logic Apps features map to the main QRadar SOAR components.
Most of the playbooks that you use with Microsoft Sentinel are available in either the Automation > Templates tab, the Content hub catalog, or Microsoft Sentinel playbooks on GitHub. In some cases, however, you might need to create playbooks from scratch or from existing templates.
You typically build your custom logic app using the Azure Logic App Designer feature. The logic apps code is based on Azure Resource Manager (ARM) templates, which facilitate development,. ARM templates are deployment files that package and portability ofmove Azure Logic Appsresources across multiple environments. To convert your custom playbook into a portable ARM template, you can use the ARM template generator.
Use the followingthese articles and blog posts for cases where you need to build your own playbooks either from scratch or from existing templates.
- Automate incident handling in Microsoft Sentinel
- Automate threat response with playbooks in Microsoft Sentinel
- Tutorial: Use playbooks with automation rules in Microsoft Sentinel
- How to use Microsoft Sentinel for Incident Response, Orchestration and Automation
- Adaptive Cards to enhance incident response in Microsoft Sentinel
SOAR post Post-migration best practices for SOAR in Microsoft Sentinel
Here are best practices you should take into account after your SOAR migration:
- Monitor the performance of your playbooks using the Playbooks health monitoring workbook.
- Use managed identities and service principals: Authenticate against various Azure services within your Logic Apps, store the secrets in Azure Key Vault, and obscure the output of the flow execution. We also recommend that you monitor the activities of the service principals used by your Logic Apps.
Next stepsstep
In this article, you learned how to map your SOAR automation from IBM Security QRadar SOAR to Microsoft Sentinel.
[!div class="nextstepaction"] Export your historical data
@@ -1,12 +1,12 @@ ----title: Migrate IBM Security QRadar SOAR automation to Microsoft Sentinel+title: Migrate IBM Security QRadar SOAR Automation to Microsoft Sentinel description: Learn how to identify SOAR use cases, and how to migrate your QRadar SOAR automation to Microsoft Sentinel. author: EdB-MSFT ms.author: edbaynash ms.topic: how-to-ms.date: 06/15/2026+ms.date: 07/01/2026 ai-usage: ai-assisted-ms.custom: msecd-doc-authoring-1014+ms.custom: msecd-doc-authoring-1016 #Customer intent: As a security engineer, I want to migrate my SOAR automation from IBM Security QRadar to Microsoft Sentinel so that I can streamline incident response and enhance threat remediation using Microsoft Sentinel's advanced automation capabilities.@@ -17,26 +17,31 @@ ms.custom: msecd-doc-authoring-1014 Microsoft Sentinel provides Security Orchestration, Automation, and Response (SOAR) capabilities with [automation rules](automate-incident-handling-with-automation-rules.md) and [playbooks](tutorial-respond-threats-playbook.md). Automation rules automate incident handling and response, and playbooks run predetermined sequences of actions to response and remediate threats. This article discusses how to identify SOAR use cases, and how to migrate your IBM Security QRadar SOAR automation to Microsoft Sentinel. -Automation rules simplify complex workflows for your incident orchestration processes, and allow you to centrally manage your incident handling automation. +Automation rules simplify complex workflows for your incident orchestration processes, and allow you to centrally manage your incident handling automation. -With automation rules, you can: -- Perform simple automation tasks without necessarily using playbooks. For example, you can assign, tag incidents, change status, and close incidents. -- Automate responses for multiple analytics rules at once. -- Control the order of actions that are executed. -- Run playbooks for those cases where more complex automation tasks are necessary. +With automation rules, you can:++- Perform simple automation tasks without necessarily using playbooks. For example, you can assign, tag incidents, change status, and close incidents.+- Automate responses for multiple analytics rules at once.+- Control the order of actions that are executed.+- Run playbooks for those cases where more complex automation tasks are necessary. ## Identify SOAR use cases Here’s what you need to think about when migrating SOAR use cases from IBM Security QRadar SOAR.-- **Use case quality**. Choose good use cases for automation. Use cases should be based on procedures that are clearly defined, with minimal variation, and a low false-positive rate. Automation should work with efficient use cases.-- **Manual intervention**. Automated response can have wide ranging effects and high impact automations should have human input to confirm high impact actions before they’re taken.-- **Binary criteria**. To increase response success, decision points within an automated workflow should be as limited as possible, with binary criteria. Binary criteria reduces the need for human intervention, and enhances outcome predictability.-- **Accurate alerts or data**. Response actions are dependent on the accuracy of signals such as alerts. Alerts and enrichment sources should be reliable. Microsoft Sentinel resources such as watchlists and reliable threat intelligence can enhance reliability.-- **Analyst role**. While automation where possible is great, reserve more complex tasks for analysts, and provide them with the opportunity for input into workflows that require validation. In short, response automation should augment and extend analyst capabilities. -## Migrate SOAR workflow+- **Use case quality**: Choose good use cases for automation. Use cases should be based on procedures that are clearly defined, with minimal variation, and a low false-positive rate. Automation should work with efficient use cases.+- **Manual intervention**: Automated response can have wide ranging effects and high impact automations should have human input to confirm high impact actions before they’re taken.+- **Binary criteria**: To increase response success, decision points within an automated workflow should be as limited as possible, with binary criteria. Binary criteria reduces the need for human intervention, and enhances outcome predictability.+- **Accurate alerts or data**: Response actions are dependent on the accuracy of signals such as alerts. Alerts and enrichment sources should be reliable. Microsoft Sentinel resources such as watchlists and reliable threat intelligence can enhance reliability.+- **Analyst role**: While automation where possible is great, reserve more complex tasks for analysts, and provide them with the opportunity for input into workflows that require validation. In short, response automation should augment and extend analyst capabilities.++<a name="migrate-soar-workflow"></a>+## Migrate SOAR workflows to Microsoft Sentinel++This section shows how key SOAR concepts in IBM Security QRadar SOAR translate to Microsoft Sentinel components. This section also provides general guidelines for how to migrate each step or component in the SOAR workflow. -This section shows how key SOAR concepts in IBM Security QRadar SOAR translate to Microsoft Sentinel components. The section also provides general guidelines for how to migrate each step or component in the SOAR workflow.+The following diagram labels four numbered workflow stages. The table after the diagram maps each numbered stage from QRadar SOAR to its Microsoft Sentinel equivalent. :::image type="content" source="media/migration-qradar-automation/qradar-sentinel-soar-workflow.png" alt-text="Diagram displaying the QRadar and Microsoft Sentinel SOAR workflows." lightbox="media/migration-qradar-automation/qradar-sentinel-soar-workflow.png" border="false"::: @@ -47,7 +52,8 @@ This section shows how key SOAR concepts in IBM Security QRadar SOAR translate t |3 |Execute selected workflows. |Execute other playbooks according to tags applied by playbooks that were executed previously. | |4 |Post data to message destinations. |Execute code snippets using inline actions in Logic Apps. | -## Map SOAR components +<a name="map-soar-components"></a>+## Map QRadar SOAR components to Microsoft Sentinel capabilities Review which Microsoft Sentinel or Azure Logic Apps features map to the main QRadar SOAR components. @@ -65,16 +71,18 @@ Review which Microsoft Sentinel or Azure Logic Apps features map to the main QRa Most of the playbooks that you use with Microsoft Sentinel are available in either the [Automation > Templates tab](use-playbook-templates.md), the [Content hub catalog](sentinel-solutions-catalog.md), or [Microsoft Sentinel playbooks on GitHub](https://github.com/Azure/Azure-Sentinel/tree/master/Playbooks/Block-OnPremADUser). In some cases, however, you might need to create playbooks from scratch or from existing templates. -You typically build your custom logic app using the Azure Logic App Designer feature. The logic apps code is based on [Azure Resource Manager (ARM) templates](/azure/azure-resource-manager/templates/overview), which facilitate development, deployment and portability of Azure Logic Apps across multiple environments. To convert your custom playbook into a portable ARM template, you can use the [ARM template generator](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/export-microsoft-sentinel-playbooks-or-azure-logic-apps-with/ba-p/3275898).+You typically build your custom logic app using the Azure Logic App Designer feature. The logic apps code is based on [Azure Resource Manager (ARM) templates](/azure/azure-resource-manager/templates/overview). ARM templates are deployment files that package and move Azure resources across multiple environments. To convert your custom playbook into a portable ARM template, you can use the [ARM template generator](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/export-microsoft-sentinel-playbooks-or-azure-logic-apps-with/ba-p/3275898).++Use these articles and blog posts for cases where you need to build your own playbooks either from scratch or from existing templates. -Use the following articles and blog posts for cases where you need to build your own playbooks either from scratch or from existing templates. - [Automate incident handling in Microsoft Sentinel](automate-incident-handling-with-automation-rules.md) - [Automate threat response with playbooks in Microsoft Sentinel](automate-responses-with-playbooks.md) - [Tutorial: Use playbooks with automation rules in Microsoft Sentinel](tutorial-respond-threats-playbook.md) - [How to use Microsoft Sentinel for Incident Response, Orchestration and Automation](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/how-to-use-azure-sentinel-for-incident-response-orchestration/ba-p/2242397) - [Adaptive Cards to enhance incident response in Microsoft Sentinel](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/using-microsoft-teams-adaptive-cards-to-enhance-incident/ba-p/3330941) -## SOAR post migration best practices+<a name="soar-post-migration-best-practices"></a>+## Post-migration best practices for SOAR in Microsoft Sentinel Here are best practices you should take into account after your SOAR migration: @@ -83,9 +91,7 @@ Here are best practices you should take into account after your SOAR migration: - Monitor the performance of your playbooks using the [Playbooks health monitoring workbook](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/what-s-new-monitoring-your-logic-apps-playbooks-in-azure/ba-p/1873211). - Use managed identities and service principals: Authenticate against various Azure services within your Logic Apps, store the secrets in Azure Key Vault, and obscure the output of the flow execution. We also recommend that you [monitor the activities of the service principals used by your Logic Apps](https://techcommunity.microsoft.com/t5/azure-sentinel/non-interactive-logins-minimizing-the-blind-spot/ba-p/2287932). -## Next steps--In this article, you learned how to map your SOAR automation from IBM Security QRadar SOAR to Microsoft Sentinel. +## Next step > [!div class="nextstepaction"] > [Export your historical data](migration-qradar-historical-data.md)