> ## Content Index
> Fetch the complete content index at: https://shakeride.com/guides/llms.txt
> Use this file to discover other available public pages before exploring further.

# Azure troubleshooting practice: Service Bus, RBAC and alert drills
- URL: https://shakeride.com/guides/azure-troubleshooting-practice/
- Published: 2026-10-21T08:00:00.000Z
- Updated: 2026-11-09T20:15:21.000Z
- Description: Azure troubleshooting practice for the failures that recur: confirm the subscription, ask the activity log what changed, then read the one resource closest to the symptom, from Service Bus lock duration to Key Vault role assignments.
- Author: Shakeride
- Tags: Practice, Azure, Azure Monitor, Service Bus, Key Vault

**In one sentence:** Azure incidents reward a short opening you have rehearsed: confirm the subscription, ask the activity log what changed, then read the configuration and role assignments of the one resource closest to the symptom.

## Symptom

You list resources and get an empty table, then spend ten minutes before noticing you are in another subscription. Or you grant a broad role at the resource group because it makes the error stop, and nobody can say what was actually missing.

## How it happens

![Five steps from left to right: confirm the subscription with az account show, read fired alerts in Azure Monitor, list write operations in the activity log, read the configuration and role assignments of the one resource closest to the symptom, then replay the user action. If the symptom remains, an arrow returns to step two with a new hypothesis.](https://shakeride.com/guides/content/images/2026/11/azure-troubleshooting-practice-evidence-ladder.svg)

- One account often sees several subscriptions; a command against the wrong one returns nothing, which reads like a finding.
- The activity log records control-plane writes only: an empty result says nothing about the data plane.
- Two settings explain many messaging incidents: a lock shorter than processing time means a second worker gets the same message, and a low max delivery count dead-letters too early.

## Act

Thirty minutes in a sandbox subscription, on a failure you did not build. Run the opening in order, writing each answer with its UTC time, then make one predicted change.

```bash
az account show --query "{sub:name,tenant:tenantId}" -o table
az monitor activity-log list --start-time 2026-10-20T08:00:00Z --end-time 2026-10-20T08:30:00Z \
  --query "[].{t:eventTimestamp,op:operationName.localizedValue,who:caller}" -o table
az servicebus queue show -g drill-rg --namespace-name drill-bus -n orders \
  --query "{lock:lockDuration,maxDelivery:maxDeliveryCount,dlq:countDetails.deadLetterMessageCount}"
az role assignment list --scope "$(az keyvault show -n drill-vault --query id -o tsv)" -o table

```

Fix at the narrowest scope: `Key Vault Secrets User` on the vault, not a broad role on the resource group. For a fired alert, open its action group and confirm a receiver exists. Verify by replaying the user's action.

## Keep watch

After each drill, record minutes to the right subscription and the right resource, changes made without a prediction, and the scope of every role you granted. The scope column should shrink toward single resources over the weeks.

## Exercise

Drill the lock duration with [The same order is processed twice](https://shakeride.com/challenges/the-same-order-processed-twice?ref=shakeride.com), then a narrow RBAC fix with [A service can no longer read its secret](https://shakeride.com/challenges/a-service-can-no-longer-read-its-secret?ref=shakeride.com).

Related: [AWS troubleshooting practice](https://shakeride.com/guides/aws-troubleshooting-practice/), [Google Cloud troubleshooting practice](https://shakeride.com/guides/gcp-troubleshooting-practice/).