Skip to content

Commit 15104f7

Browse files
authored
Private endpoints support disclaimer v2
1 parent 6856f9c commit 15104f7

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/sentinel/automate-responses-with-playbooks.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,6 @@ ms.custom: ignite-fall-2021
1010

1111
# Automate threat response with playbooks in Microsoft Sentinel
1212

13-
[!INCLUDE [Banner for top of topics](./includes/banner.md)]
14-
1513
This article explains what Microsoft Sentinel playbooks are, and how to use them to implement your Security Orchestration, Automation and Response (SOAR) operations, achieving better results while saving time and resources.
1614

1715
## What is a playbook?
@@ -76,10 +74,9 @@ Azure Logic Apps communicates with other systems and services using connectors.
7674
Microsoft Sentinel now supports the following logic app resource types:
7775

7876
- **Consumption**, which runs in multi-tenant Azure Logic Apps and uses classic, original Azure Logic Apps engine
79-
8077
- **Standard**, which runs in single-tenant Azure Logic Apps and uses a redesigned Azure Logic Apps engine
8178

82-
This logic app type offers higher performance, fixed pricing, multiple workflow capability, easier API connections management, native network capabilities such as support for virtual networks and private endpoints, built-in CI/CD features, better Visual Studio Code integration, an updated workflow designer, and more.
79+
This logic app type offers higher performance, fixed pricing, multiple workflow capability, easier API connections management, native network capabilities such as support for virtual networks and private endpoints (see note below), built-in CI/CD features, better Visual Studio Code integration, an updated workflow designer, and more.
8380

8481
To use this logic app version, create new Standard playbooks in Microsoft Sentinel. You can use these playbooks in the same ways that you use Consumption playbooks:
8582

@@ -91,6 +88,9 @@ Microsoft Sentinel now supports the following logic app resource types:
9188
>
9289
> - Standard workflows currently don't support Playbook templates, which means you can't create a Standard workflow from within Microsoft Sentinel. Instead, you must create the workflow in Azure Logic Apps. After creation, the workflow appears in Microsoft Sentinel.
9390
>
91+
> - Although Standard workflows support private endpoints as mentioned above, Microsoft Sentinel doesn't currently support the use of private endpoints in playbooks, even those based on Standard workflows.
92+
> Workflows with private endpoints might still be visible and selectable when you're choosing a playbook from a list in Microsoft Sentinel (whether to run manually, to add to an automation rule, or in the playbooks gallery), and you'll be able to select them, but their execution will fail.
93+
>
9494
> - An indicator identifies Standard workflows as either *stateful* or *stateless*. Microsoft Sentinel doesn't support stateless workflows at this time. Learn about the differences between [**stateful and stateless workflows**](../logic-apps/single-tenant-overview-compare.md#stateful-and-stateless-workflows).
9595
9696
There are many differences between these two resource types, some of which affect some of the ways they can be used in playbooks in Microsoft Sentinel. In such cases, the documentation will point out what you need to know. For more information, see [Resource type and host environment differences](../logic-apps/logic-apps-overview.md#resource-environment-differences) in the Azure Logic Apps documentation.
@@ -99,12 +99,12 @@ There are many differences between these two resource types, some of which affec
9999

100100
To give your SecOps team the ability to use Azure Logic Apps to create and run playbooks in Microsoft Sentinel, assign Azure roles to your security operations team or to specific users on the team. The following describes the different available roles, and the tasks for which they should be assigned:
101101

102-
#### Roles for Azure Logic Apps
102+
#### Azure roles for Azure Logic Apps
103103

104104
- **Logic App Contributor** lets you manage logic apps and run playbooks, but you can't change access to them (for that you need the **Owner** role).
105-
- **Logic App Operator** lets you read, enable, and disable logic apps, but you can't edit or update them.
105+
- **Logic App Operator** lets you read, enable, and disable logic apps, but you can't edit or update them.
106106

107-
#### Azure roles for Sentinel
107+
#### Azure roles for Microsoft Sentinel
108108

109109
- **Microsoft Sentinel Contributor** role lets you attach a playbook to an analytics rule.
110110
- **Microsoft Sentinel Responder** role lets you run a playbook manually.

0 commit comments

Comments
 (0)