Overview

When configuring many settings, bulk edit is faster than one-by-one commands. Export settings as JSON, edit, then import.

Short notes (exam revision)

Export: az webapp config appsettings list --output json > settings.json
Import file with @ prefix: --settings @settings.json
Portal: Environment variables → Advanced edit (JSON)

Export current settings

Azure CLI

az webapp config appsettings list \
  --resource-group myResourceGroup \
  --name myDocumentProcessor \
  --output json > settings.json

Exported shape:

JSON

[
  {
    "name": "STORAGE_ACCOUNT_NAME",
    "value": "mystorageaccount",
    "slotSetting": false
  },
  {
    "name": "LOG_LEVEL",
    "value": "INFO",
    "slotSetting": false
  }
]

Import updated settings

Azure CLI

az webapp config appsettings set \
  --resource-group myResourceGroup \
  --name myDocumentProcessor \
  --settings @settings.json

Portal

Azure portal → app → Environment variables → Advanced edit for JSON bulk modifications.

Use cases

Clone prod settings into a staging app (edit values, import)
Add twenty feature flags in one pass for an AI orchestration service
Keep a checked-in settings.dev.json template for labs (no secrets)

Exam tips

Know @settings.json file syntax for CLI
slotSetting in JSON ties to deployment-slot behavior

Bulk editing