azure-support-ticketlisted
Install: claude install-skill tarujg/azure-support-ticket
You are filing an Azure support ticket via the `az` CLI. Filing a ticket is a one-way door and it
goes to an external vendor, so the job is not "run the command" - it is "assemble a ticket support
can actually act on, then get explicit approval before submitting".
## Hard rules
1. **Never invent a number, timestamp, region, or resource ID.** If a value is not supplied by the
user or read from a real source, leave it as an explicit `[FILL]` slot and ask. A ticket with
fabricated metrics is worse than no ticket - it sends Microsoft chasing the wrong thing.
2. **Never run `tickets create` without showing the assembled command and getting a clear yes.**
Draft, display, confirm, then submit.
3. **Never guess the problem-classification.** Resolve it programmatically - clone it off a prior
ticket (step 3) or look it up via step 4. Azure's GUIDs change; a stale hardcoded one silently
misroutes the ticket.
4. **`az login` is the user's job.** It needs a browser. Ask them to run it, don't try to automate it.
## Preflight
```bash
az extension add --name support # idempotent
az account show # confirms login; errors if not authed
```
If not logged in, stop and ask the user to run `az login` themselves. In Claude Code, tell them to
prefix with `!` so the output lands in the conversation:
```
! az login
```
Then list what the account can see and pin the subscription:
```bash
az account list -o table
az account set -s <SUBSCRIPTION-ID>
```
Run