az storage container immutability-policy create --account-name <account> --container-name <container> --period <days> --auth-mode loginCreate, update, or operate storage container immutability-policy with the Azure CLI.
Search an az command, command group, or Azure task. AzureGlossary shows what the command touches, how risky it is, which concepts explain it, and what safer checks and generated safe-first paths to run first.
Microsoft Learn remains the official Azure CLI reference. This page is the plain-English command map for safety, context, operator review, and safe-first command paths.
az storage container immutability-policy commands for Storage; browse safety labels, operation lanes, mapped Azure concepts, and safe-first examples.
az storage container immutability-policy create --account-name <account> --container-name <container> --period <days> --auth-mode loginCreate, update, or operate storage container immutability-policy with the Azure CLI.
az storage container immutability-policy create --account-name <storage-account> --container-name <container> --period <days> --auth-mode loginCreate, update, or operate storage container immutability-policy with the Azure CLI.
az storage container immutability-policy extend --account-name <storage-account> --container-name <container> --period <days> --if-match <etag> --auth-mode loginCreate, update, or operate storage container immutability-policy with the Azure CLI.
az storage container immutability-policy lock --account-name <account> --container-name <container> --auth-mode loginCreate, update, or operate storage container immutability-policy with the Azure CLI.
az storage container immutability-policy lock --account-name <account> --container-name <container> --if-match <etag>Delete or remove storage container immutability-policy with the Azure CLI; verify scope and backup/rollback before running.
az storage container immutability-policy lock --account-name <storage-account> --container-name <container> --if-match <etag> --auth-mode loginDelete or remove storage container immutability-policy with the Azure CLI; verify scope and backup/rollback before running.
az storage container immutability-policy show --account-name <account> --container-name <container>Inspect or list storage container immutability-policy with the Azure CLI before making changes.
az storage container immutability-policy show --account-name <account> --container-name <container> --auth-mode loginInspect or list storage container immutability-policy with the Azure CLI before making changes.
az storage container immutability-policy show --account-name <storage-account> --container-name <container> --auth-mode login --output jsonInspect or list storage container immutability-policy with the Azure CLI before making changes.
az storage container immutability-policy show --container-name <container> --account-name <storage-account>Inspect container immutability policy.
Start with a command, group, or messy task. The Command Center gives you a briefing before you copy anything: risk, touched services, safe-first paths, related concepts, and the official Microsoft Learn reference.
Try a real command such as az role assignment list, a group such as az aks, or a task such as private endpoint. Results open as command briefing cards.
Each card explains the command, what it touches, whether it is safe for discovery, and the safe-first path to run before risky changes.
Try a command group such as az group, az storage, az webapp, az aks, az sql, or az role assignment.
Inspect AKS state, credentials, node pools, upgrades, monitoring, and destructive operations from one lane.
Navigate database, analytics, messaging, and AI commands from discovery to controlled mutation.
Inspect identities and assignments before making privileged RBAC, managed identity, or credential changes.
Start with read-only discovery, create only after context checks, then clean up deliberately.
Discover storage accounts, then check network, identity, lifecycle, container, and destructive cleanup commands.
Move from App Service discovery through deployment, slot checks, diagnostics, and guarded rollback.