A Defender for Cloud recommendation shows that an Azure AI Services resource has 'Managed identity not enabled,' rated as medium severity. The security team wants to remediate this across 20 Azure AI Services resources at once. Which Defender for Cloud feature enables bulk remediation?
Select an answer to reveal the explanation.
Short Explanation
Here's the deal — Defender for Cloud's 'Fix' button or Quick Fix logic lets you remediate all affected Azure AI Services resources at once. It enables the system-assigned managed identity across the selected resources in bulk, so you don't have to touch each one individually.
Full Explanation
The Defender for Cloud recommendation's 'Fix' button, or remediation via the REST API using the same 'Quick Fix' logic, is the right answer because Microsoft Defender for Cloud recommendations with a 'Quick Fix' capability include a 'Fix' button that, when clicked, applies the automated remediation logic to all selected affected resources in bulk. For the 'managed identity not enabled' recommendation on Azure AI Services resources, the Quick Fix enables the system-assigned managed identity on each selected resource simultaneously, eliminating the need to configure 20 resources individually. The Azure Policy deployIfNotExists approach is also a valid long-term enforcement approach, but it is a preventive control for future deployments, not a bulk remediation mechanism for existing resources. The manual portal fix option is wrong because manually fixing 20 resources individually is time-consuming and error-prone. The PowerShell or Azure CLI script approach is wrong because a PowerShell/CLI script is a valid alternative but is a custom automation approach, whereas the Defender for Cloud Quick Fix is the built-in, purpose-designed remediation mechanism.