You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
16
16
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).
18
18
19
19
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.
20
20
@@ -165,66 +165,69 @@ This example shows you how to assign the built-in Defender for Cloud initiative
165
165
```
166
166
167
167
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.
168
171
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
172
175
173
-
Request Body (JSON)
176
+
Request Body (JSON)
174
177
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"
0 commit comments