Skip to content

Commit d9c0a27

Browse files
authored
Merge pull request #178457 from memildin/asc-melvyn-release-notes
Tweak to Ignite "we've renamed" banner + 2 updated screenshots
2 parents 83dada0 + 9ffdd03 commit d9c0a27

File tree

5 files changed

+7
-8
lines changed

5 files changed

+7
-8
lines changed

articles/security-center/implement-security-recommendations.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,6 @@ ms.service: security-center
77
ms.topic: conceptual
88
ms.date: 03/04/2021
99
ms.author: memildin
10-
1110
---
1211
# Implement security recommendations in Microsoft Defender for Cloud
1312

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
author: memildin
33
ms.author: memildin
4-
ms.date: 10/21/2021
4+
ms.date: 11/03/2021
55
ms.service: security-center
66
ms.topic: include
77
---
88

99
> [!NOTE]
1010
>
11-
> Azure Security Center and Azure Defender are now called **Microsoft Defender for Cloud**. We've also renamed Azure Defender plans to Microsoft Defender plans. For example, Azure Defender for Storage is now Microsoft Defender for Storage. We’ll update these pages with the changes during the coming weeks.
11+
> Azure Security Center and Azure Defender are now called **Microsoft Defender for Cloud**. We've also renamed *Azure Defender* plans to *Microsoft Defender* plans. For example, Azure Defender for Storage is now Microsoft Defender for Storage.
1212
>
1313
> [Learn more about the recent renaming of Microsoft security services.](https://aka.ms/secblg11)
20.6 KB
Loading
44.7 KB
Loading

articles/security-center/workflow-automation.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -35,13 +35,15 @@ This article describes the workflow automation feature of Microsoft Defender for
3535

3636
1. From Defender for Cloud's sidebar, select **Workflow automation**.
3737

38-
:::image type="content" source="./media/workflow-automation/list-of-workflow-automations.png" alt-text="List of workflow automations.":::
38+
:::image type="content" source="./media/workflow-automation/list-of-workflow-automations.png" alt-text="Screenshot of workflow automation page showing the list of defined automations." lightbox="./media/workflow-automation/list-of-workflow-automations.png":::
3939

4040
From this page you can create new automation rules, as well as enable, disable, or delete existing ones.
4141

42-
1. To define a new workflow, click **Add workflow automation**.
42+
1. To define a new workflow, click **Add workflow automation**. The options pane for your new automation opens.
4343

44-
A pane appears with the options for your new automation. Here you can enter:
44+
:::image type="content" source="./media/workflow-automation/add-workflow.png" alt-text="Add workflow automations pane.":::
45+
46+
Here you can enter:
4547
1. A name and description for the automation.
4648
1. The triggers that will initiate this automatic workflow. For example, you might want your Logic App to run when a security alert that contains "SQL" is generated.
4749

@@ -50,8 +52,6 @@ This article describes the workflow automation feature of Microsoft Defender for
5052
5153
1. The Logic App that will run when your trigger conditions are met.
5254

53-
:::image type="content" source="./media/workflow-automation/add-workflow.png" alt-text="Add workflow automations pane.":::
54-
5555
1. From the Actions section, select **visit the Logic Apps page** to begin the Logic App creation process.
5656

5757
You'll be taken to Azure Logic Apps.

0 commit comments

Comments
 (0)