Service Bus Tiers: Basic vs Standard
Overview
Azure Service Bus provides two primary pricing tiers - Basic and Standard - each designed for different use cases and requirements. Understanding the differences between these tiers is essential for making cost-effective architectural decisions. While Basic tier offers simple queue functionality at a lower cost, Standard tier unlocks advanced messaging patterns like pub/sub with topics.
What You'll Learn
- Comparing the features and capabilities of Basic and Standard tiers
- Understanding when to use each tier
- How to upgrade or downgrade between tiers
- Making informed decisions based on your messaging needs
Choosing Between Tiers
Your choice depends on your requirements:
- Basic Tier - Best for simple queue messaging, learning, and low-cost prototypes
- Standard Tier - Required for pub/sub patterns, message sessions, and advanced features
Comparison Table
| Feature | Basic | Standard |
|---|---|---|
| Price | Lower | Higher |
| Queues | ✓ | ✓ |
| Topics | ✗ | ✓ |
| WebSockets | ✗ | ✓ |
| Auto-forwarding | ✗ | ✓ |
| Sessions | ✗ | ✓ |
| Duplicate Detection | ✗ | ✓ |
| SLA | 99.9% | 99.9% |
When to Use Basic Tier
Good For:
- Simple queue-based messaging
- Low message volume
- Cost-sensitive projects
- Learning/poc projects
Not Good For:
- Pub/Sub patterns (need topics)
- High-throughput scenarios
- Advanced features needed
Pricing Example (Pay-as-you-go)
- Basic: ~$0.005 per 10,000 operations
- Standard: ~$0.015 per 10,000 operations
When to Use Standard Tier
Good For:
- Pub/Sub with Topics
- Multiple subscribers
- Message sessions
- Duplicate detection
- Auto-forwarding
- High-scale applications
Features:
- Topics & Subscriptions - One publisher, many subscribers
- Message Sessions - Process related messages in order
- Duplicate Detection - Auto-detect and discard duplicates
- Auto-forwarding - Forward messages to another queue/topic
How to Change Tier
Via Portal
- Go to Service Bus Namespace
- Click Pricing tier in left menu
- Select Basic or Standard
- Click Save
Via CLI
# Create with Standard tier
az servicebus namespace create \
--resource-group myrg \
--name mynamespace \
--sku Standard
Migration Considerations
- No downtime - Upgrade from Basic to Standard is instant
- Downgrade - Possible but review queue size limits
- Message format - Same format across tiers
Decision Guide
Need Topics/Subscriptions?
YES → Standard Tier
NO ↓
Need High Throughput?
YES → Standard Tier
NO ↓
Budget Constrained?
YES → Basic Tier
NO → Standard Tier
Next Steps
- Learn about Connection Strings & Authentication
Azure Integration Hub - Beginner Level