liveBook · Manning

Recommendation

As explained in Microsoft Azure in Action

A security recommendation is actionable guidance for reducing security risk or improving an environment's security controls or posture.

A security recommendation is an actionable to-do item for improving a particular Azure service’s security posture. Microsoft Defender for Cloud continually monitors resources, identifies weaknesses, explains their impact, and suggests ways to fix them. section 6.4 section 6.9

Recommendations appear in resource security menus, including those for virtual machines. They are not merely warnings: each one provides context, a severity rating, remediation steps, and sometimes a direct route to the required configuration change. section 6.4.1

A recommendation typically tells you:

  • How serious the issue is, such as high severity. section 6.4.1
  • How recently Azure checked whether the issue still exists. section 6.4.1
  • Why the issue matters and when it may reasonably be disregarded or closed. section 6.4.1
  • Which remediation steps can resolve it, either automatically or through manual configuration. section 6.4.1

Encrypting a virtual machine's disks

Suppose the Alpaca-Ma-Bags file server still has its original Azure settings. A recommendation flags missing encryption for temporary disks and data caches. After reviewing its severity, freshness, explanation, and exceptions, the operator selects Take Action, opens the VM's disk settings, and enables disk encryption manually. section 6.4.1

Figure 6.12 Each recommended security fix is described and rated for severity.

Use the figure to see how recommended security fixes are described and rated for severity. section 6.4.1

Recommendations work alongside Secure Score and security alerts. Secure Score helps prioritize improvements that add the most value, while alerts identify detected threats. Together, they turn security monitoring into a practical improvement queue rather than a mysterious cloud scolding. section 6.4 section 6.9

How Microsoft Azure in Action covers it

How deep it goes
Explains severity, freshness, rationale, exceptions, remediation, and action paths, stopping short of detailing every underlying security check.
Examples
Uses an Azure file server, missing disk encryption, severity details, and the Take Action workflow.
What you can do after
Apply via Microsoft Defender for Cloud to prioritize, investigate, and remediate Azure security weaknesses.
How it connects
Connects Microsoft Defender for Cloud with Secure Score, security alerts, virtual machines, and disk encryption.

Also explained in

Compare how 2 books explain recommendation →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microsoft Azure in Action. The section links point to the parts of the book it draws on.