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
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/onboard-management-group.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Onboard a management group
3
3
description: Learn how to use a supplied Azure Policy definition to enable Microsoft Defender for Cloud for all the subscriptions in a management group.
4
4
ms.topic: how-to
5
-
ms.date: 02/21/2023
5
+
ms.date: 03/20/2024
6
6
---
7
7
8
8
# Enable Defender for Cloud on all subscriptions in a management group
@@ -78,11 +78,9 @@ There are various ways you might choose to modify the Azure Policy definition:
- **Define some Microsoft Defender plans to apply when enabling Defender for Cloud** - The supplied policy enables Defender for Cloud without any of the optional enhanced security features. You might choose to enable one or more of the Microsoft Defender plans.
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/workflow-automation.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to create and automate workflows in Microsoft Defender fo
4
4
ms.topic: how-to
5
5
author: dcurwin
6
6
ms.author: dacurwin
7
-
ms.date: 06/18/2023
7
+
ms.date: 03/20/2024
8
8
---
9
9
# Automate remediation responses
10
10
@@ -16,6 +16,7 @@ This article describes the workflow automation feature of Microsoft Defender for
16
16
17
17
- You need **Security admin role** or **Owner** on the resource group.
18
18
- You must also have write permissions for the target resource.
19
+
- The workflow automation feature supports consumption logic app workflows and not standard logic app workflows.
19
20
- To work with Azure Logic Apps workflows, you must also have the following Logic Apps roles/permissions:
20
21
21
22
-[Logic App Operator](../role-based-access-control/built-in-roles.md#logic-app-operator) permissions are required or Logic App read/trigger access (this role can't create or edit logic apps; only *run* existing ones)
0 commit comments