az storage message clear --queue-name <queue-name> --account-name <storage-account> --auth-mode loginDelete or remove storage message with the Azure CLI; verify scope and backup/rollback before running.
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 message commands for Storage; browse safety labels, operation lanes, mapped Azure concepts, and safe-first examples.
az storage message clear --queue-name <queue-name> --account-name <storage-account> --auth-mode loginDelete or remove storage message with the Azure CLI; verify scope and backup/rollback before running.
az storage message delete --queue-name <queue-name> --account-name <storage-account> --id <message-id> --pop-receipt <pop-receipt>Delete or remove storage message with the Azure CLI; verify scope and backup/rollback before running.
az storage message delete --queue-name <queue-name> --id <message-id> --pop-receipt <pop-receipt> --account-name <storage-account> --auth-mode loginDelete or remove storage message with the Azure CLI; verify scope and backup/rollback before running.
az storage message delete --queue-name <queue-name>-poison --id <message-id> --pop-receipt <pop-receipt> --account-name <storage-account> --auth-mode loginDelete or remove storage message with the Azure CLI; verify scope and backup/rollback before running.
az storage message get --account-name <account> --queue-name <queue> --visibility-timeout 300 --auth-mode loginInspect or list storage message with the Azure CLI before making changes.
az storage message get --queue-name <queue-name> --account-name <storage-account> --auth-mode loginInspect or list storage message with the Azure CLI before making changes.
az storage message get --queue-name <queue-name> --account-name <storage-account> --num-messages 32 --visibility-timeout 300 --auth-mode loginInspect or list storage message with the Azure CLI before making changes.
az storage message get --queue-name <queue-name> --account-name <storage-account> --visibility-timeout 300 --auth-mode loginInspect or list storage message with the Azure CLI before making changes.
az storage message get --queue-name <queue-name> --account-name <storage-account> --visibility-timeout 300 --num-messages 1Inspect or list storage message with the Azure CLI before making changes.
az storage message get --queue-name <queue-name>-poison --account-name <storage-account> --num-messages 1 --visibility-timeout 300 --auth-mode loginInspect or list storage message with the Azure CLI before making changes.
az storage message peek --account-name <account> --queue-name <queue> --num-messages 5 --auth-mode loginInspect or list storage message with the Azure CLI before making changes.
az storage message peek --account-name <storage-account> --queue-name <queue>Peek at queue messages.
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.