From a445f048f2575e818584832cfb75da1fbe38e785 Mon Sep 17 00:00:00 2001
From: Manish Kumar <97503740+manishkumar1991@users.noreply.github.com>
Date: Fri, 29 Sep 2023 15:20:53 +0530
Subject: [PATCH] Update readme.md

---
 .../o365-DeleteMaliciousInboxRule/readme.md                     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Solutions/Microsoft Defender for Office 365/Playbooks/O365DefenderPlaybooks/o365-DeleteMaliciousInboxRule/readme.md b/Solutions/Microsoft Defender for Office 365/Playbooks/O365DefenderPlaybooks/o365-DeleteMaliciousInboxRule/readme.md
index 1efddf33d96..b08523e50d3 100644
--- a/Solutions/Microsoft Defender for Office 365/Playbooks/O365DefenderPlaybooks/o365-DeleteMaliciousInboxRule/readme.md	
+++ b/Solutions/Microsoft Defender for Office 365/Playbooks/O365DefenderPlaybooks/o365-DeleteMaliciousInboxRule/readme.md	
@@ -56,7 +56,7 @@ Once deployment is complete, you will need to authorize each connection.
 1. Select the Keyvault resource where you have stored the secret
 2. Click on Access policies Blade
 3. Click on Create
-4. Under Secret permissions columun , Select Get , List from "Secret Management Operations"
+4. Under Secret permissions column , Select Get , List from "Secret Management Operations"
 5. Click next to go to Principal tab and choose your deployed playbook name
 6. Click Next leave application tab as it is .
 7. Click Review and create