You have onboarded the organization’s Microsoft Azure account on FortiCNAPP using the automated configuration approach.

Comprehensive and Detailed Explanation From FortiOS 7.6, FortiWeb 7.4 Exact Extract study guide:

Based on the FortiCNAPP 24.x Administration Guide regarding Microsoft Azure onboarding and feature activation:

Separation of Integration Types (Option D): In FortiCNAPP, onboarding a cloud account via the automated configuration approach often initializes the Cloud Security Posture Management (CSPM) and Cloud Infrastructure Entitlement Management (CIEM) features. However, Workload Scanning (specifically Agentless Scanning) is treated as a distinct integration type within the platform.

Guided Configuration Requirement: Even after the account is onboarded, the administrator must navigate to the Integrations or Onboarding section and specifically add the Workload Scanning integration for that Azure account. This "Guided Configuration" ensures that the necessary additional permissions (such as those required to create snapshots of disks and scan them) and resources (like the scanner VNet or regional scanners) are properly deployed within the Azure environment.

Why other options are incorrect:

Option A & B: Automated onboarding already handles the creation of necessary App Registrations and Service Principals. Manually adding more without following the specific integration workflow will not activate the workload scanning engine.

Option C: Threat policies are used to generate alerts based on existing data. If the raw workload scanning data is not being received from Azure, a policy will have no data to analyze; the issue is at the ingestion/integration layer, not the policy layer.