Skip to content

Commit ddee2d4

Browse files
committed
date and small fixes
1 parent 9b77148 commit ddee2d4

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/defender-for-cloud/custom-security-policies.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Create custom Azure security policies in Microsoft Defender for Cloud
33
description: Azure custom policy definitions monitored by Microsoft Defender for Cloud.
44
ms.topic: how-to
55
ms.custom: ignite-2022
6-
ms.date: 01/19/2023
6+
ms.date: 01/22/2023
77
zone_pivot_groups: manage-asc-initiatives
88
---
99

@@ -64,7 +64,7 @@ If there isn't an initiative in the list that meets your needs, you can create o
6464
> [!NOTE]
6565
> Creating new initiatives requires subscription owner credentials. For more information about Azure roles, see [Permissions in Microsoft Defender for Cloud](permissions.md).
6666
67-
Your new initiative takes effect and you can see the impact in the following two ways:
67+
Your new initiative takes effect and you can see the results in the following two ways:
6868

6969
* From the Defender for Cloud menu, select **Regulatory compliance**. The compliance dashboard opens to show your new custom initiative alongside the built-in initiatives.
7070

@@ -260,7 +260,7 @@ The metadata should be added to the policy definition for a policy that is part
260260
},
261261
```
262262

263-
Below is an example of a custom policy including the metadata/securityCenter property:
263+
Here's another example of a custom policy including the metadata/securityCenter property:
264264

265265
```json
266266
{

0 commit comments

Comments
 (0)