Availability zone enabled for notification hub even when explicitly disabled

Question

Availability zone enabled for notification hub even when explicitly disabled

Thomas Boucard 0

I created a notification hub without availability zone:
User's image

It started a deployment with zoneRedudancy Disabled:
User's image

Then it create a notification hub with availability zones enabled: User's image

How to deploy a notification hub with the parameter I requested ?

Bhargavi Naragani 1,535 Reputation points Microsoft External Staff

2025-03-05T18:20:31.8+00:00

Hi @Thomas Boucard,
Just checking in to see if the above information helped. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Bhargavi Naragani 1,535 Reputation points Microsoft External Staff

2025-03-06T17:09:52.5233333+00:00

Hi @Thomas Boucard,
Just checking in to see if the above information helped. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Sampath 925 Reputation points Microsoft External Staff

2025-03-12T10:18:35.2666667+00:00
Hello @Thomas Boucard,

From this MSDOC You can only enable availability zones and Geo-disaster recovery on new namespaces. Because Notification Hubs doesn't support the migration of existing namespaces, you can't disable zone redundancy after enabling it on your namespace.

we can use Azure Traffic Manager to route traffic but Azure Notification Hubs cannot be directly added as an endpoint in Azure Traffic Manager because Notification Hubs are not exposed as a typical web service with a public DNS name or IP address that Traffic Manager can route traffic to. Traffic Manager primarily works with web-based services and applications, including:

Azure Endpoints (such as Web Apps, VMs, Load Balancers)

External Endpoints (IPv4/IPv6, FQDNs, on-prem services)

Nested Endpoints (Traffic Manager profiles within profiles)

Refer to this MSDOC for more details on Traffic Manager endpoints.

Alternatives:

Create a New Notification Hub with Availability Zones: You can set up a new Notification Hub in a namespace that supports availability zones. This ensures resilience against data center failures. You would need to migrate your existing data and configurations to the new hub.

Alternative Azure Services: Depending on your requirements, you might consider using other Azure services like Event Grid or Service Bus, which offer more robust disaster recovery options.

If the answer is helpful, please kindly upvote it so that other people who faces similar issue may get benefitted from it. Let me know if you have any further Queries.

1 answer

Your answer

Bhargavi Naragani 1,535 Reputation points Microsoft External Staff

2025-03-05T18:20:31.8+00:00

Hi @Thomas Boucard,
Just checking in to see if the above information helped. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Bhargavi Naragani 1,535 Reputation points Microsoft External Staff

2025-03-06T17:09:52.5233333+00:00

Hi @Thomas Boucard,
Just checking in to see if the above information helped. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Sampath 925 Reputation points Microsoft External Staff

2025-03-12T10:18:35.2666667+00:00

Hello @Thomas Boucard,

From this MSDOC You can only enable availability zones and Geo-disaster recovery on new namespaces. Because Notification Hubs doesn't support the migration of existing namespaces, you can't disable zone redundancy after enabling it on your namespace.

we can use Azure Traffic Manager to route traffic but Azure Notification Hubs cannot be directly added as an endpoint in Azure Traffic Manager because Notification Hubs are not exposed as a typical web service with a public DNS name or IP address that Traffic Manager can route traffic to. Traffic Manager primarily works with web-based services and applications, including:

Azure Endpoints (such as Web Apps, VMs, Load Balancers)

External Endpoints (IPv4/IPv6, FQDNs, on-prem services)

Nested Endpoints (Traffic Manager profiles within profiles)

Refer to this MSDOC for more details on Traffic Manager endpoints.

Alternatives:

Create a New Notification Hub with Availability Zones: You can set up a new Notification Hub in a namespace that supports availability zones. This ensures resilience against data center failures. You would need to migrate your existing data and configurations to the new hub.

Alternative Azure Services: Depending on your requirements, you might consider using other Azure services like Event Grid or Service Bus, which offer more robust disaster recovery options.

If the answer is helpful, please kindly upvote it so that other people who faces similar issue may get benefitted from it. Let me know if you have any further Queries.

Answer 1

Bhargavi Naragani 1,535 Microsoft External Staff

Hi @Thomas Boucard,

It seems that even though explicitly configured the zoneRedundancy parameter to "Disabled" at deployment time, the Notification Hub still had availability zones enabled. there are few things you can do to troubleshoot and fix this.

Double-check the deployment template and parameters to make sure that zoneRedundancy is actually set to Disabled. Occasionally, even though the UI indicates the correct value, the actual deployment script may override this. example JSON config:

{
  "type": "Microsoft.NotificationHubs/namespaces/notificationHubs",
  "properties": {
    "zoneRedundancy": "Disabled"
  }
}

Availability zones can be enabled automatically based on where you deploy the notification hub. Ensure that the region you've chosen has zone redundancy support and defaults to being enabled. The supported regions can be found here: Azure Regions with Zone Redundancy.

If you deployed with an ARM template, check the zoneRedundancy parameter supplied at deployment:

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "parameters": {
    "zoneRedundancy": {
      "type": "string",
      "defaultValue": "Disabled"
    }
  }
}

If Notification Hub is already created with availability zones turned on, and you want to modify this option, you may have to redeploy it. Zone redundancy settings are not currently editable after resources are created.

Create and Manage Azure Notification Hubs
Azure ARM Template Reference

If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.

Let me know if you have any further Queries.

Thomas Boucard 0

Here is the deployment template:

{
    "$schema": "http://schema.management.azure.com/schemas/2014-04-01-preview/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
        "namespaceLocation": {
            "type": "String"
        },
        "namespaceName": {
            "type": "String"
        },
        "notificationHubName": {
            "type": "String"
        },
        "sku": {
            "type": "String"
        },
        "tags": {
            "defaultValue": {},
            "type": "Object"
        },
        "replicationRegion": {
            "defaultValue": "default",
            "type": "String"
        },
        "zoneRedundancy": {
            "defaultValue": "Disabled",
            "type": "String"
        }
    },
    "resources": [
        {
            "type": "Microsoft.NotificationHubs/namespaces",
            "apiVersion": "2023-10-01-preview",
            "name": "[parameters('namespaceName')]",
            "location": "[parameters('namespaceLocation')]",
            "sku": {
                "name": "[parameters('sku')]"
            },
            "properties": {
                "replicationRegion": "[parameters('replicationRegion')]",
                "zoneRedundancy": "[parameters('zoneRedundancy')]"
            },
            "resources": [
                {
                    "type": "notificationHubs",
                    "apiVersion": "2023-10-01-preview",
                    "name": "[parameters('notificationHubName')]",
                    "location": "[parameters('namespaceLocation')]",
                    "dependsOn": [
                        "[concat('Microsoft.NotificationHubs/namespaces/', parameters('namespaceName'))]"
                    ],
                    "tags": "[parameters('tags')]",
                    "sku": {
                        "name": "[parameters('sku')]"
                    },
                    "properties": {
                        "name": "[parameters('notificationHubName')]"
                    }
                }
            ]
        }
    ]
}

zoneRedudancy is correctly disabled in default and it is not overrided. The notification hub created from this template still have Availability zone enabled

Share via

Availability zone enabled for notification hub even when explicitly disabled

1 answer

Your answer