Security Cloud security posture

Defender for Cloud

Microsoft Defender for Cloud is a cloud-native application protection platform that provides security posture management, recommendations, regulatory insights, and workload protection across Azure, multicloud, and DevOps environments.

Source: Microsoft Learn - Microsoft Defender for Cloud overview Reviewed 2026-05-13

Exam trap: Changing production before checking the exact owner, scope, downstream dependency, monitoring evidence, and rollback impact.
Production check: Can you name the owner, parent resource, environment, and downstream dependency without guessing?

Practice this topic Microsoft Learn

Article details and learning context

Aliases: Microsoft Defender for Cloud, Azure Defender for Cloud, MDC
Difficulty: beginner
CLI mappings: 4
Last verified: 2026-05-13
Review level: launch-ready
Article depth: field-manual-complete

Learning paths Learn Security and Governance Defender for Cloud

Related context Learning path: Security and Governance Concept cluster: Security concept cluster

Compare related concepts Search related resources Browse the glossary

Understand the concept

In plain English

Defender for Cloud is Microsoft’s cloud security platform for posture management, recommendations, compliance views, and workload protection across Azure and connected environments. In Azure, it helps teams centralize cloud security findings so teams can prioritize risk, enable protection plans, track recommendations, and respond to alerts consistently. Plainly, it is a named operating concept that connects design intent with live configuration, evidence, ownership, and production impact. A useful glossary entry should show where it lives, who controls it, what depends on it, and what signal proves it is working.

Why it matters

Defender for Cloud matters because it turns architecture language into something teams can secure, monitor, troubleshoot, and explain under pressure. When it is documented shallowly, engineers may change the wrong resource, policy, identity, database, queue, workspace, or path while the real dependency remains untouched. In enterprise Azure projects, the value is shared language: platform, security, data, finance, and operations teams can discuss the same object without guessing. That reduces incident time, improves audit evidence, prevents avoidable rework, and makes migrations safer because downstream consumers and failure modes are visible before release. Treat Defender for Cloud as production owned when scheduled jobs, regulated data, customer traffic, or security monitoring depends on it.

Technical context

Technically, Defender for Cloud appears in Defender for Cloud portal, subscription security plans, recommendations, secure score, regulatory compliance views, alerts, and policy assignments and interacts with Microsoft Defender for Cloud, Azure Policy, Azure Monitor, and Log Analytics. Configuration is reviewed through Defender plan enablement, security recommendations, secure score, and policy assignments, while operators validate live state through plan coverage, recommendation status, security alerts, and secure score trend. Scope matters because the same word can refer to a portal setting, API property, runtime behavior, or governance control.

Exam context

Compare with

Defender for Containers Azure Policy

Where it is used

Where you see it

In Defender for Cloud, recommendations, secure score, alerts, and regulatory compliance dashboards show posture and protection status across subscriptions during production review before an approved change.
In subscription settings, Defender plans show which resource types are protected and whether advanced workload protections are enabled during production review before an approved change.
In security operations, Defender for Cloud alerts appear when suspicious activity, vulnerable configurations, or high-risk workloads need triage during production review before an approved change.

Common situations

Review secure score, recommendations, alerts, and regulatory compliance across subscriptions and workloads.
Prioritize remediation for exposed resources, missing controls, vulnerable configurations, and high-risk assets.
Enable workload protection plans and validate pricing, coverage, and ownership before production rollout.
Investigate security alerts with asset context, identity information, and linked monitoring data.
Use posture findings during architecture reviews, incident response, audits, and cloud governance planning.

Illustrative Azure scenarios

These examples show how the concept can affect design and operations. They are illustrative scenarios, not customer claims.

Scenario 01 Defender for Cloud in action for financial services Scenario, objectives, solution, measured impact, and takeaway.

Scenario

Westbridge Bank, a financial services organization, needed to address security teams lacked one prioritized view of risk across Azure subscriptions and DevOps projects. The architecture team used Defender for Cloud as the control point for a measurable production improvement.

Goals

Improve secure score by 20 points
Route high-severity alerts to the SOC
Create evidence for regulatory review

Approach using Defender for Cloud

The security architecture team enabled Defender for Cloud plans by workload risk, reviewed built-in recommendations, and aligned policy assignments with the bank landing zone. Alerts were connected to the SOC workflow, while exemptions required owner, expiration, and compensating-control notes. Weekly secure-score reviews focused on critical internet exposure and identity risks. Engineers captured before-and-after evidence, updated the runbook, and tied the change to named owners, monitoring signals, and rollback steps. The design was tested in a lower environment so security, operations, and finance teams could review the impact before production rollout. Support staff received clear checks for resource state, identity, cost, telemetry, and downstream dependency health. Engineers captured before-and-after evidence, updated the runbook, and tied the change to named owners, monitoring signals, and rollback steps.

Potential outcomes

Secure score improved by 24 points
High-severity alert triage time dropped 43 percent
Regulatory evidence collection fell from weeks to three days

What to learn

Defender for Cloud helps security teams turn cloud posture data into prioritized, owned remediation work.

Scenario 02 Defender for Cloud in action for omnichannel retail Scenario, objectives, solution, measured impact, and takeaway.

Scenario

OmniCart Retail, a omnichannel retail organization, needed to address store modernization created inconsistent Defender plan coverage across subscriptions. The architecture team used Defender for Cloud as the control point for a measurable production improvement.

Goals

Standardize workload protection coverage
Reduce unmanaged recommendations
Show plan cost by subscription owner

Approach using Defender for Cloud

The cloud governance team used Defender for Cloud to inventory plan status, recommendations, and exemptions across retail platform subscriptions. Azure Policy assignments enforced baseline settings, and Cost Management tags linked Defender plan charges to product teams. The team created a dashboard for open recommendations by severity and due date. Engineers captured before-and-after evidence, updated the runbook, and tied the change to named owners, monitoring signals, and rollback steps. The design was tested in a lower environment so security, operations, and finance teams could review the impact before production rollout. Support staff received clear checks for resource state, identity, cost, telemetry, and downstream dependency health. Engineers captured before-and-after evidence, updated the runbook, and tied the change to named owners, monitoring signals, and rollback steps. The design was tested in a lower environment so security, operations, and finance teams could review the impact before production rollout.

Potential outcomes

Uncovered critical subscriptions fell to zero
Overdue high-severity recommendations dropped 64 percent
Plan cost allocation became visible to every product owner

What to learn

Defender for Cloud connects protection coverage, remediation accountability, and cost transparency.

Scenario 03 Defender for Cloud in action for healthcare provider Scenario, objectives, solution, measured impact, and takeaway.

Scenario

HarborView Health, a healthcare provider organization, needed to address clinical workloads needed stronger evidence that cloud resources met security baseline controls. The architecture team used Defender for Cloud as the control point for a measurable production improvement.

Goals

Track compliance against approved standards
Reduce manual spreadsheet assessments
Escalate risky resource findings quickly

Approach using Defender for Cloud

The security team configured Defender for Cloud regulatory views and recommendations for clinical subscriptions. Resource owners received prioritized findings, while Log Analytics and Defender alerts fed the incident-response process. Exceptions for legacy systems required expiration dates and compensating controls so compliance reviews did not become permanent waivers. Engineers captured before-and-after evidence, updated the runbook, and tied the change to named owners, monitoring signals, and rollback steps. The design was tested in a lower environment so security, operations, and finance teams could review the impact before production rollout. Support staff received clear checks for resource state, identity, cost, telemetry, and downstream dependency health. Engineers captured before-and-after evidence, updated the runbook, and tied the change to named owners, monitoring signals, and rollback steps.

Potential outcomes

Manual assessment effort dropped 58 percent
Critical recommendation response improved to under two business days
Compliance review evidence was available on demand

What to learn

Defender for Cloud gives regulated Azure workloads continuous security posture evidence instead of periodic guesswork. Record ownership.

Azure CLI

CLI checks for Defender for Cloud are useful because they turn portal assumptions into repeatable evidence. Start with read-only commands that show the resource, definition, permissions, metrics, or runtime state, then compare the output with the intended design. Use mutating commands only through an approved change process with owner, rollback, and impact notes. For Defender for Cloud, evidence should be captured before and after production changes.

Useful for

Review cloud security posture and prioritize remediation across subscriptions.
Enable workload protection plans and route alerts to security operations teams.
Collect compliance evidence for Azure, multicloud, and DevOps resources.

Before you run a command

Run az account show, confirm tenant and subscription, and verify the operator identity has approved read access for the exact scope.
Confirm the resource group, workspace, account, queue, container, file system, app registration, or security plan name before collecting evidence.
Prefer read-only commands first; review any command that changes access, cost, compute state, network exposure, message settlement, or production data.

What the output tells you

Whether the object exists in the expected Azure resource, tenant, workspace, account, namespace, or governance boundary.
Which owner, identity, permission, status, metric, endpoint, throughput setting, ACL, security plan, or runtime value is visible to the current operator.
Whether the issue is missing scope, permission drift, wrong environment, network misconfiguration, stale deployment, service health, or resource state.

Mapped commands

Defender for Cloud operational checks

direct

az security pricing list

az security pricingdiscoverSecurity

az security assessment list

az security assessmentdiscoverSecurity

az security secure-scores list

az security secure-scoresdiscoverSecurity

az security alert list

az security alertdiscoverSecurity

Architecture context

Defender for Cloud belongs to Security architecture decisions where identity, networking, monitoring, cost ownership, and production support need shared evidence.

Security: Security for Defender for Cloud starts with least privilege, identity clarity, and evidence that access matches the workload classification. Review subscription plan coverage, recommendation remediation, alert triage, regulatory compliance evidence, and least-privilege connector access before approving production use. A common failure is assuming that a successful portal action, query, message receive, or scan result proves the design is secure. Use Microsoft Entra groups, managed identities, role assignments, private connectivity, audit logs, and service-specific privileges where applicable. Keep exceptions ticketed, time-bounded, and tied to a named owner. For regulated workloads, align the configuration with classification, retention, break-glass, and incident-response procedures. Remove broad access, stale secrets, unreviewed public paths, and undocumented administrator permissions before Defender for Cloud becomes an incident path.
Cost: Cost for Defender for Cloud appears through compute duration, request units, protected endpoints, storage growth, diagnostic retention, operational toil, and the downstream work triggered by bad configuration. Review enabled Defender plans, protected resource count, duplicate coverage, log retention, and recommendation remediation effort before expanding production use. Some costs are direct, such as DWU compute, container app profile instances, Cosmos DB throughput, security plan coverage, or storage; others are indirect, such as retries, manual evidence collection, delayed restores, and failed jobs. Tag related Azure resources, monitor usage, and separate exploratory work from production workloads. A cost review should connect spend to a real owner and measurable value.
Reliability: Reliability for Defender for Cloud depends on repeatable configuration, tested dependencies, and clear failure signals. Watch data connector health, policy assignment drift, alert routing, agent coverage, and multicloud connection status because drift often appears later as missed schedules, failed restores, broken private connectivity, stuck messages, slow queries, or incomplete security coverage. Use lower environments, source-controlled definitions where possible, deployment checks, monitoring, and rollback notes before changing production. Operators should know which resource, endpoint, identity, data path, queue, database, or downstream system fails first and which log or metric proves the failure. The goal is predictable recovery: detect Defender for Cloud drift, protect data, restore service, and explain the incident without guessing.
Performance: Performance for Defender for Cloud depends on workload shape, data layout, network path, scale limits, governance choices, and the compute or broker path used to access it. Review alert volume, assessment refresh timing, query latency, agent overhead, and dashboard load time before increasing capacity. The better fix might be scheduling, query tuning, partition design, throughput allocation, lock handling, file compaction, path validation, or clearer orchestration. Measure with representative traffic and data, not a tiny sample that hides production behavior. Operators should connect symptoms to evidence: latency, queue depth, RU consumption, CPU, scan volume, failed stages, status changes, or run duration.
Operations: Operations for Defender for Cloud should focus on ownership, observability, and safe repeatability. Standardize naming, tags, owner groups, environment labels, diagnostic destinations, runbook links, and change approvals so support teams do not reverse-engineer the design during an incident. Use read-only CLI, API, SQL, or portal checks first, then compare live state with the intended configuration. For production, connect alerts, audit events, cost records, access reviews, and release notes to the same term. The support question should be simple: who owns it, what changed, and what proves the current state?. Capture owner, scope, evidence, and rollback before changing Defender for Cloud in a production environment.

Common mistakes

Changing production before checking the exact owner, scope, downstream dependency, monitoring evidence, and rollback impact.
Using a portal screenshot as the only record when CLI, API, audit logs, SQL, or source-controlled configuration can provide repeatable evidence.
Assuming management-plane permissions, data-plane permissions, and service-specific privileges are granted and reviewed by the same team.