Skip to content

Playbooks

These playbooks give operators focused, symptom-first guidance for recurring Azure Storage incidents. Start with the targeted playbooks below when the failure mode is already known, then move into the broader access, performance, or security collections if you need deeper branching guidance.

mermaid flowchart TD A[Storage incident] --> B[Targeted playbooks] A --> C[Access playbooks] A --> D[Performance playbooks] A --> E[Security playbooks]

Targeted Playbooks

Playbook Primary symptom First things to verify
Blob Access Denied 403, blocked SAS, RBAC, firewall, or private access failures Identity path, SAS scope, firewall, DNS
Storage Throttling ServerBusy, 503, latency spikes, IOPS or throughput pressure Metrics, request distribution, concurrency
Replication Lag Issues Secondary reads appear stale or DR expectations are unclear Replication model, primary write health, failover readiness
Lifecycle Policy Not Working Tier moves or deletes do not happen on schedule Policy scope, blob age, recovery features

Access

Playbook Primary Symptom
Cannot Access Storage Account endpoint cannot be reached
Private Endpoint and DNS Issues private path resolves or routes incorrectly
File Share Mount Issues SMB or NFS mount fails
Public vs Private Access Confusion wrong route chosen between public and private access

Performance

Playbook Primary Symptom
Slow Upload / Download transfer throughput is unexpectedly low
Throttling and Performance Issues 429, 503, or burst-driven latency
Data Protection and Recovery Issues deleted or overwritten data needs recovery

Security

Playbook Primary Symptom
Authorization Failures 403 or data-plane permission failure
SAS and Token Issues SAS or token-specific rejection

See Also

Sources