Skip to content

Commit 47617f4

Browse files
Merge pull request #101643 from memildin/asc-melvyn-quickfixFriday
Removed obsolete article about Playbooks
2 parents 12a6358 + c92cfbb commit 47617f4

File tree

5 files changed

+7
-108
lines changed

5 files changed

+7
-108
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27981,6 +27981,11 @@
2798127981
"redirect_url": "/azure/security-center/security-center-partner-integration",
2798227982
"redirect_document_id": false
2798327983
},
27984+
{
27985+
"source_path": "articles/security-center/security-center-playbooks.md",
27986+
"redirect_url": "/azure/security-center/workflow-automation",
27987+
"redirect_document_id": false
27988+
},
2798427989
{
2798527990
"source_path": "articles/security-center/security-center-compliance-rest-api.md",
2798627991
"redirect_url": "https://docs.microsoft.com/rest/api/securitycenter/compliances",

articles/security-center/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -178,8 +178,6 @@
178178
href: security-center-investigation.md
179179
- name: Manage investigation user data
180180
href: security-center-investigation-user-data.md
181-
- name: Logic Apps playbooks
182-
href: security-center-playbooks.md
183181
- name: Planning and operations
184182
href: security-center-planning-and-operations-guide.md
185183

articles/security-center/security-center-planning-and-operations-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -235,7 +235,7 @@ This page shows the details regarding the time that the attack took place, the s
235235

236236
From this page, you can also start an [investigation](https://docs.microsoft.com/azure/security-center/security-center-investigation) to better understand the timeline of the attack, how the attack took place, which systems were potentially compromised, which credentials were used, and see a graphical representation of the entire attack chain.
237237

238-
Once you identify the compromised system, you can run security [playbooks](https://docs.microsoft.com/azure/security-center/security-center-playbooks) that were previously created. Security playbook is a collection of procedures that can be executed from Security Center once a certain playbook is triggered from selected alert.
238+
Once you identify the compromised system, you can run a [Workflow Automation](workflow-automation.md) that was previously created. These are a collection of procedures that can be executed from Security Center once triggered by an alert.
239239

240240
In the [How to Leverage the Azure Security Center & Microsoft Operations Management Suite for an Incident Response](https://channel9.msdn.com/Blogs/Taste-of-Premier/ToP1703) video, you can see some demonstrations that can help you to understand how Security Center can be used in each one of those stages.
241241

articles/security-center/security-center-playbooks.md

Lines changed: 0 additions & 104 deletions
This file was deleted.

articles/security-center/security-center-readiness-roadmap.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ Videos
8080

8181
Articles
8282
* [Using Azure Security Center for an incident response](https://docs.microsoft.com/azure/security-center/security-center-incident-response)
83-
* [Automate response with security playbook](https://docs.microsoft.com/azure/security-center/security-center-playbooks)
83+
* [Automate response with Workflow Automation](workflow-automation.md)
8484

8585
## Advanced cloud defense
8686

0 commit comments

Comments
 (0)