🛡️ Premium Azure Service Bus namespace has no queues or topics🟢

• Contextual name: 🛡️ Premium namespace has no queues or topics🟢
• ID: /ce/ca/azure/service-bus/premium-namespace-without-entities
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: COMPLIANCE_POLICY
• Policy Categories: COST

Stats

not available

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 Azure Service Bus Namespace
  • 🔌 Azure Service Bus Namespace - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

This policy identifies Premium Azure Service Bus namespaces older than the initial 30-day deployment window that contain no current queues or topics.

Rationale

Premium namespaces reserve dedicated messaging capacity and incur capacity charges even when they contain no messaging entities. An empty namespace cannot carry messages through a queue or topic, so its reserved capacity is a strong indicator of avoidable spend.

Impact

An empty namespace may retain network, identity, authorization, disaster-recovery, or imminent deployment dependencies. Confirm ownership and architecture before deleting it or moving workloads.

Audit

This policy flags an Azure Service Bus Namespace as INCOMPLIANT if it is in the Succeeded provisioning state, uses the Premium SKU tier, was created more than 30 days ago, and has no non-disappeared related Azure Service Bus Queue or Azure Service Bus Topic records.

Remediation

Open File

Remediation

Verify the entity inventory directly in Azure before changing or deleting the namespace.

Verify the Finding

Azure portal

1. Open Service Bus namespaces and select the affected namespace.
2. Under Entities, confirm that both Queues and Topics are empty.

Azure CLI

List the queues and topics currently reported by Azure:

az servicebus queue list \
  --namespace-name {{namespace-name}} \
  --resource-group {{resource-group-name}} \
  --subscription {{subscription-id}} \
  --query "[].name" \
  --output tsv

az servicebus topic list \
  --namespace-name {{namespace-name}} \
  --resource-group {{resource-group-name}} \
  --subscription {{subscription-id}} \
  --query "[].name" \
  --output tsv

No output from either command confirms that Azure currently reports no queues or topics. If Azure contains entities that are absent from Cloudaware CMDB, resolve collection permissions or synchronization before proceeding.

Review Dependencies

Before remediation:

1. Confirm the namespace owner and whether a deployment is planned.

... see more

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 Cloudaware Framework → 💼 Waste Reduction			30		no data