Skip to content

Commit d9452b4

Browse files
authored
Merge pull request #193835 from bmansheim/patch-3
Add note to highlight ASC:true
2 parents 8e71b39 + d621faa commit d9452b4

File tree

1 file changed

+52
-49
lines changed

1 file changed

+52
-49
lines changed

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

Lines changed: 52 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ zone_pivot_groups: manage-asc-initiatives
1414

1515
To help secure your systems and environment, Microsoft Defender for Cloud generates security recommendations. These recommendations are based on industry best practices, which are incorporated into the generic, default security policy supplied to all customers. They can also come from Defender for Cloud's knowledge of industry and regulatory standards.
1616

17-
With this feature, you can add your own *custom* initiatives. Although custom initiatives are not included in the secure score, you'll receive recommendations if your environment doesn't follow the policies you create. Any custom initiatives you create are shown in the list of all recommendations and you can filter by initiative to see the recommendations for your initiative. They are also shonw with the built-in initiatives in the regulatory compliance dashboard, as described in the tutorial [Improve your regulatory compliance](regulatory-compliance-dashboard.md).
17+
With this feature, you can add your own *custom* initiatives. Although custom initiatives are not included in the secure score, you'll receive recommendations if your environment doesn't follow the policies you create. Any custom initiatives you create are shown in the list of all recommendations and you can filter by initiative to see the recommendations for your initiative. They are also shown with the built-in initiatives in the regulatory compliance dashboard, as described in the tutorial [Improve your regulatory compliance](regulatory-compliance-dashboard.md).
1818

1919
As discussed in [the Azure Policy documentation](../governance/policy/concepts/definition-structure.md#definition-location), when you specify a location for your custom initiative, it must be a management group or a subscription.
2020

@@ -165,66 +165,69 @@ This example shows you how to assign the built-in Defender for Cloud initiative
165165
```
166166

167167
This example shows you how to assign a custom Defender for Cloud initiative on a subscription or management group:
168+
169+
> [!NOTE]
170+
> Make sure you include `"ASC":"true"` in the request body as shown here. The `ASC` field onboards the initiative to Microsoft Defender for Cloud.
168171
169-
```
170-
PUT
171-
PUT https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.Authorization/policySetDefinitions/{policySetDefinitionName}?api-version=2021-06-01
172+
```
173+
PUT
174+
PUT https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.Authorization/policySetDefinitions/{policySetDefinitionName}?api-version=2021-06-01
172175
173-
Request Body (JSON)
176+
Request Body (JSON)
174177
175-
{
176-
"properties": {
177-
"displayName": "Cost Management",
178-
"description": "Policies to enforce low cost storage SKUs",
179-
"metadata": {
180-
"category": "Cost Management"
181-
"ASC":"true"
182-
},
183-
"parameters": {
184-
"namePrefix": {
185-
"type": "String",
186-
"defaultValue": "myPrefix",
187-
"metadata": {
188-
"displayName": "Prefix to enforce on resource names"
178+
{
179+
"properties": {
180+
"displayName": "Cost Management",
181+
"description": "Policies to enforce low cost storage SKUs",
182+
"metadata": {
183+
"category": "Cost Management"
184+
"ASC":"true"
185+
},
186+
"parameters": {
187+
"namePrefix": {
188+
"type": "String",
189+
"defaultValue": "myPrefix",
190+
"metadata": {
191+
"displayName": "Prefix to enforce on resource names"
192+
}
193+
}
194+
},
195+
"policyDefinitions": [
196+
{
197+
"policyDefinitionId": "/subscriptions/ae640e6b-ba3e-4256-9d62-2993eecfa6f2/providers/Microsoft.Authorization/policyDefinitions/7433c107-6db4-4ad1-b57a-a76dce0154a1",
198+
"policyDefinitionReferenceId": "Limit_Skus",
199+
"parameters": {
200+
"listOfAllowedSKUs": {
201+
"value": [
202+
"Standard_GRS",
203+
"Standard_LRS"
204+
]
189205
}
190206
}
191207
},
192-
"policyDefinitions": [
193-
{
194-
"policyDefinitionId": "/subscriptions/ae640e6b-ba3e-4256-9d62-2993eecfa6f2/providers/Microsoft.Authorization/policyDefinitions/7433c107-6db4-4ad1-b57a-a76dce0154a1",
195-
"policyDefinitionReferenceId": "Limit_Skus",
196-
"parameters": {
197-
"listOfAllowedSKUs": {
198-
"value": [
199-
"Standard_GRS",
200-
"Standard_LRS"
201-
]
202-
}
203-
}
204-
},
205-
{
206-
"policyDefinitionId": "/subscriptions/ae640e6b-ba3e-4256-9d62-2993eecfa6f2/providers/Microsoft.Authorization/policyDefinitions/ResourceNaming",
207-
"policyDefinitionReferenceId": "Resource_Naming",
208-
"parameters": {
209-
"prefix": {
210-
"value": "[parameters('namePrefix')]"
211-
},
212-
"suffix": {
213-
"value": "-LC"
214-
}
208+
{
209+
"policyDefinitionId": "/subscriptions/ae640e6b-ba3e-4256-9d62-2993eecfa6f2/providers/Microsoft.Authorization/policyDefinitions/ResourceNaming",
210+
"policyDefinitionReferenceId": "Resource_Naming",
211+
"parameters": {
212+
"prefix": {
213+
"value": "[parameters('namePrefix')]"
214+
},
215+
"suffix": {
216+
"value": "-LC"
215217
}
216218
}
217-
]
218-
}
219+
}
220+
]
219221
}
220-
```
222+
}
223+
```
221224

222225
This example shows you how to remove an assignment:
223226

224-
```
225-
DELETE
226-
https://management.azure.com/{scope}/providers/Microsoft.Authorization/policyAssignments/{policyAssignmentName}?api-version=2018-05-01
227-
```
227+
```
228+
DELETE
229+
https://management.azure.com/{scope}/providers/Microsoft.Authorization/policyAssignments/{policyAssignmentName}?api-version=2018-05-01
230+
```
228231

229232
::: zone-end
230233

0 commit comments

Comments
 (0)