Skip to content

Manage Subscription Defender Settings

The engineer's guide to Microsoft Defender for Cloud on a vended subscription. Use this runbook to:

  • Find where a subscription's Defender settings now live.
  • Exempt one resource from an EPAC policy.

Defender is no longer set in vending

Plans, the security contact and every other Defender setting are now decided once, for every subscription, in azure-defender. Don't set defender_plans or security_contact_email in a subscription's vending file. For the steps, see Manage Defender for Cloud.

The projects

Project Lane Holds
azure-defender Tier 1, CI applies Every Defender setting, for every subscription under mg-intermediate-root except mg-sandboxes. A per-subscription change is an override in its config/*.yaml.
azure-governance-epac Tier 1, CI applies Policy exemptions in Definitions/policyExemptions/grinntec/exemptions.jsonc.

Change Defender for one subscription

📁 azure-defender: 📃 config/<setting>.yaml

Add an override keyed by the subscription's name, with a reason. For example, a plan on for one subscription:

overrides:
  grinntec-website-prod-westeu-00:
    StorageAccounts:
      enabled: true
      reason: "Hosts public uploads."

See Manage Defender for Cloud for every setting.


Exempt one resource

📁 azure-governance-epac: 📃 Definitions/policyExemptions/grinntec/exemptions.jsonc

For an EPAC policy (such as MCSB psa-sec-mcsb-001, or a governance policy) that one resource can't meet yet. Add one entry, scoped as narrowly as possible, with an expiry no more than 90 days out:

{
  "name": "exm-sec-mcsb-st-payments-001",
  "displayName": "MCSB waiver - st-payments-export public network access",
  "description": "Export account needs a public endpoint until the partner's private link is live (GRIN-1234).",
  "exemptionCategory": "Waiver",
  "expiresOn": "2027-01-15",
  "scope": "/subscriptions/<sub-id>/resourceGroups/rg-payments-prod/providers/Microsoft.Storage/storageAccounts/stpaymentsexport",
  "policyAssignmentId": "psa-sec-mcsb-001",
  "policyDefinitionReferenceIds": [ "<policyDefinitionReferenceId>" ],
  "metadata": {
    "requestedBy": "someone@grinntec.net",
    "approvedBy": "neil@grinntec.net",
    "ticket": "GRIN-1234"
  }
}

A CODEOWNER other than you approves the MR. The full rules are in the EPAC repo's Definitions/policyExemptions/README.md.

An EPAC exemption covers the compliance dashboard only

Defender's Secure Score comes from SecurityCenterBuiltIn on each subscription, which EPAC doesn't manage. To take the resource out of the Secure Score as well, add a matching entry to azure-defender's config/exemptions.yaml, with the same reason and expiry. See Exempt one resource.