A company uses Microsoft Defender for Cloud to manage the security posture of multiple Azure subscriptions. The security team wants to ensure that all subscriptions are covered by the same Microsoft Defender for Cloud policy initiative, but one subscription is not showing compliance data. The subscription is in the same Azure AD tenant and has the same tags. What is the most likely cause?
Trap 1: The user does not have Security Admin permissions on the…
Permissions affect visibility, not data generation.
Trap 2: The subscription does not have any tags applied.
Tags are not required for compliance scanning.
Trap 3: The subscription does not have the default policy initiative…
Defender for Cloud auto-assigns the default initiative.
- A
The user does not have Security Admin permissions on the subscription.
Why wrong: Permissions affect visibility, not data generation.
- B
The subscription does not have any tags applied.
Why wrong: Tags are not required for compliance scanning.
- C
The subscription does not have the default policy initiative assigned.
Why wrong: Defender for Cloud auto-assigns the default initiative.
- D
The subscription is not registered with the Microsoft.Security resource provider.
Registration is required for Defender for Cloud to assess the subscription.