Microsoft Security Exposure Management
Vulnerabilities and exposure

Defender CLI setup for agentic code security

In brief

The documentation adds a prerequisite requiring accounts to have at least one listed permission before running Defender CLI commands and updates the Defender.InteractiveLogin scope identifier.

What Defender admins need to know

Ensure affected accounts have the required permission and update authentication configuration to use the new scope identifier.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Prerequisites

Before you can run the Defender CLI commands, make sure your account has been assigned at least one of the following permissions:

az login \
  --tenant <DEFENDER_DFD_TENANT_ID> \
  --scope b1a78a13-a596-4366-b37d-406048fa4a23/c2fd607e-fe6e-41bd-ae58-08e2f24014aa/Defender.InteractiveLogin \
  --allow-no-subscriptions \
  --use-device-code