CmdID / az / az webapp / az webapp secure-build

az webapp secure-build show

Show the Secure Build report for the active deployment of a Linux web app. Azure CLI reference

The service uses a cached report when available. Use --rescan to request fresh dependency analysis, which can take several minutes. Output follows the Azure CLI output configuration and is JSON when no format is configured. Use --output table for a human-readable summary and up to 20 findings; when --query is supplied, standard query processing controls the resulting table shape. JSON output and the provided Kudu link contain the full report. Secure Build currently supports Python dependency information produced by supported platform builds.

3 examples 4 options Its page in the Azure CLI reference

Examples

from the Azure CLI, each command read by CmdID

Show a human-readable Secure Build report for the active deployment.

az webapp secure-build show --resource-group ResourceGroup --name AppName --output tableIdentify

--resource-groupName of resource group.

--namename of the web app.

--outputOutput format

Show the complete Secure Build report as JSON.

az webapp secure-build show --resource-group ResourceGroup --name AppName --output jsonIdentify

--resource-groupName of resource group.

--namename of the web app.

--outputOutput format

Run a fresh analysis for a deployment slot and show critical findings.

az webapp secure-build show --resource-group ResourceGroup --name AppName --slot staging --rescan --query "findings[?advisory.severity=='CRITICAL']" --output table

Identify

--resource-groupName of resource group.

--namename of the web app.

--slotName of the web app slot.

--rescanRun a fresh dependency analysis instead of using a cached report.

--queryJMESPath query string.

--outputOutput format

Options

4 in the Azure CLI reference

--name, -nname of the web app.

--rescanRun a fresh dependency analysis instead of using a cached report.

--resource-group, -gName of resource group.

--slot, -sName of the web app slot.