Azure Service Bus Namespace
Does ZopNight manage Azure Service Bus Namespace?
Service Bus namespaces on the Premium tier reserve dedicated messaging units that bill continuously, independent of message volume. A Premium namespace retained in a non-production environment carries a heavy fixed cost. ZopNight records tier and entity context via Resource Graph and surfaces tier-downgrade opportunities from 60 days of message-volume metrics.
Rules that fire on Azure Service Bus Namespace
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery and cost visibility only. |
Service Bus provides enterprise messaging with queues and topics, with Premium tier billed per messaging unit reserved. Premium namespaces retained in non-production environments carry a heavy fixed cost.
Messaging units make Premium a fixed cost
On the Premium tier, a Service Bus namespace reserves dedicated messaging units that bill continuously: capacity is bought, not metered, and a namespace passing a handful of test messages pays the same as one running at full throughput. Lower tiers track usage far more closely, which is why the tier decision, not message volume, sets the bill for most namespaces. Once a messaging unit is reserved, every idle hour is a paid hour.
Namespace and entity context ZopNight gathers
Discovered via Azure Resource Graph with tier and entity context. Azure Monitor metrics spanning 60 days show message volume, Cost Management billing attributes spend, and tier-downgrade opportunities surface in review. Service Bus is not a schedulable type: stopping a message broker means dropping or delaying the traffic it exists to broker, so ZopNight treats namespaces as rightsizing targets rather than on/off ones.
Premium namespaces stranded outside production
The dominant leak is a Premium namespace in dev, QA, or staging, created to mirror production behavior during a migration or load test, then simply kept. The messaging units reserved there bill at the full fixed rate through months of near-idle traffic. Second is over-scaled production, where units added for a seasonal peak were never stepped back down. Third is the fully abandoned namespace whose producing and consuming applications were both retired, identifiable by message metrics that have been flat at zero for weeks.
Verifying namespace tier in the portal
Azure portal → Service Bus lists every namespace alongside its pricing tier. For a Premium namespace, the Scale blade shows the messaging-unit count, and the Overview’s message charts make a stranded namespace obvious against sixty days of nothing.