Notification Hub namespace should use Standard or higher SKU
Medium
Azure
General
namespaces-notification-hub-namespace-standard
Applies to
Microsoft.NotificationHubs/namespaces
What CGPulse checks
A resource passes this rule when skuName must be one of ["Standard","Premium"]. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Upgrade to Standard or Premium SKU for enhanced security features and telemetry. In Azure Portal: Notification Hub namespace > Pricing tier > select Standard or Premium. See: https://learn.microsoft.com/en-us/azure/notification-hubs/notification-hubs-push-notification-overview
CLI
az notification-hub namespace show --ids "{id}" --query "sku.name" -o tsvBicep
// SKU cannot be changed — create new namespace with Standard tier
resource nhNamespace 'Microsoft.NotificationHubs/namespaces@2023-10-01-preview' = {{
name: '{name}'
location: resourceGroup().location
sku: {{
name: 'Standard'
}}
properties: {{}}
}}Terraform
resource "azurerm_notification_hub_namespace" "{name}" {
name = "{name}"
resource_group_name = "{rg}"
location = var.location
namespace_type = "NotificationHub"
sku_name = "Standard"
}
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related Azure rules
- Action Group should be enabled
- Activity Log Alert should be enabled
- AKS cluster logs should be sent to Log Analytics
- AKS cluster must enable RBAC
- AKS cluster must enable RBAC
- AKS cluster should be a private cluster
- AKS cluster should disable local accounts
- AKS cluster should enable Azure RBAC for Kubernetes