The most powerful Azure Storage Queue tool for VS Code. Browse, inspect, and manage every message in your queues — not just the first 32.
Why This Extension?
Azure's built-in tools limit queue peek to 32 messages. That's it. If your queue has thousands of messages and you need to inspect, debug, or move them — you're stuck writing scripts or guessing.
Azure Storage Queue Toolkit breaks that limit. Deep Peek scans your entire queue so you can see every message, search through them, and take action — all from your editor.
Key Features
Deep Peek — See All Your Messages
Azure's API caps peek at 32 messages. Deep Peek scans your entire queue using a safe two-phase approach: messages are temporarily received, collected, then immediately restored. You get full visibility without losing a single message.
Bulk Operations at Scale
Select and copy, move, or delete messages across queues — with no 32-message ceiling. Full queue scanning means you can operate on hundreds or thousands of messages at once.
Generate Test Messages
Create realistic test data directly in your queues. Choose from JSON, plain text, or XML formats with randomized sample data. Generate up to 1,000 messages in one shot — perfect for load testing and development.
Blob Storage Built In
Browse containers, upload and download files, preview content (text, JSON, images), manage metadata, and generate SAS tokens. Full blob management without leaving VS Code.
Production-Safe
Every destructive or high-impact operation shows a clear warning with details about what will happen. Visibility timeouts, message invisibility windows, and operation scope are explained before you confirm.
Complete Feature List
Queue Management
- Connect multiple Azure Storage accounts
- Create and delete queues
- View queue properties and metadata
- Queue analytics dashboard with health scores
- Auto-refresh at configurable intervals
- Favorites for quick access
Message Operations
- Peek Messages — View up to 32 messages (Azure limit)
- Deep Peek — Scan ALL messages in a queue (no limit)
- Send Messages — Send new messages to any queue
- Receive / Dequeue — Receive messages with visibility control
- Delete — Remove individual messages
- Clear Queue — Delete all messages at once
- Export to JSON — Save messages to a file
- Import from JSON — Load messages from a file
- Generate Test Messages — Create bulk test data (JSON, text, XML)
Bulk Operations
- Bulk Delete — Select and delete multiple messages
- Move Messages — Move selected messages to another queue
- Copy Messages — Copy selected messages to another queue
- All bulk operations scan the full queue (not limited to 32)
Blob Storage
- Browse containers with virtual folder navigation
- Upload and download blobs
- Preview blob content (text, JSON, images, hex for binary)
- Container management (create, delete, properties, metadata)
- Bulk delete blobs
- Generate SAS tokens for containers and individual blobs
- Copy blob URLs
Security & Access
- SAS token generation for queues and blobs
- Access policy management
- Connection strings stored in VS Code's encrypted secure storage
- No data sent to external servers — all Azure communication is direct
Getting Started
Requirements
- VS Code 1.85+
- Python 3.9+ (used for the backend — auto-configured on first run)
- An Azure Storage account connection string
Setup
- Install the extension from the VS Code Marketplace
- Click the toolkit icon in the Activity Bar (left sidebar)
- Click the + button to add your Azure Storage account
- Paste your connection string (Azure Portal > Storage Account > Access Keys)
- Explore — expand your account to see Queues and Blob Containers
Your connection string is stored securely in VS Code's encrypted storage and never leaves your machine.
Configuration
| Setting |
Description |
Default |
azureQueueExplorer.pythonPath |
Path to Python executable |
Auto-detect |
azureQueueExplorer.serverPort |
Backend server port |
5789 |
azureQueueExplorer.maxMessagesToDisplay |
Default messages to peek |
32 |
azureQueueExplorer.autoRefreshInterval |
Refresh interval in seconds |
30 |
How Deep Peek Works
Azure Queue Storage's peek API is hard-limited to 32 messages per call. Deep Peek works around this by:
- Receiving messages in batches (they become temporarily invisible)
- Collecting all messages with deduplication
- Restoring visibility immediately so no messages are lost
Messages are invisible for up to 5 minutes during scanning as a safety buffer, but are restored as soon as collection completes. The operation is safe for production queues, and a warning dialog explains the process before you confirm.
Privacy & Security
- All connection strings are stored locally in VS Code's encrypted secure storage
- No telemetry, analytics, or data collection of any kind
- No external server communication — the extension talks directly to Azure
- The Python backend runs locally on your machine (127.0.0.1)
Feedback & Issues
Found a bug or have a feature request? Open an issue on GitHub.
Azure Storage Queue Toolkit — Built for developers who need more than 32 messages.