Once you have a decision in place, you should make sure that every time the new subscription is created these settings are aligned with the policy. One of my customers has more than 100 subscriptions and for example, in that specific environment, there are small variations in the settings between different sub-categories (test/dev/QA/prod). In the larger environments, there might be also a differentiation between enhanced security features configuration in the subscriptions. What is important is that you have your settings aligned with your security policy and decisions. It doesn’t matter what mechanism you are using as long as you use one. Microsoft Defender for open-source relational databasesĮnable Enhanced Security Features for the SubscriptionĮnhanced security features can be managed with any of the following methods:.Microsoft Defender for Resource Manager.For enabling MDC Advanced Threat protection the plans need to be enabled (those are not enabled by default).

In the last category, there are Microsoft Defender Advanced Threat protection, security alerts, and integration with Microsoft Sentinel or 3rd party SIEM. In general, Defender for Cloud (MDC) can be categorized into three (3) different categories

Earlier there were two different modes available: Free & Standard but nowadays Microsoft is talking about ‘Enhanced Security Features’. In the last Microsoft Ignite new name for the former Azure Security Center was announced – Microsoft Defender for Cloud. The assumption on this write-up is that decision of enabling the features has been made (including cost impact). In this blog post, I share a simple solution on how the challenge can be tackled.

The main reason often is manual configuration instead of automatic configuration of the settings (technical control is missing). What I see often is that these plans, or features, are not consistently enabled between subscriptions even though there would be a decision that the features should be enabled.

Microsoft Defender for Cloud (former Azure Security Center) provides ‘Enhanced Security Features’ also known as Defender plans, to protect workloads in the Azure environment.

How to enable microsoft defender