Availability zone enabled for notification hub even when explicitly disabled

Question

Availability zone enabled for notification hub even when explicitly disabled

Thomas Boucard 20

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 6,130 Reputation points Microsoft External Staff Moderator

2025-03-04T21:00:09.15+00:00
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.
Bhargavi Naragani 6,130 Reputation points Microsoft External Staff Moderator

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 6,130 Reputation points Microsoft External Staff Moderator

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.

Thomas Boucard 20

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

Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-13T15:50:44.41+00:00

Hello @Thomas Boucard, Could you please review the comments above?
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-14T06:42:57.8266667+00:00

Hello @Thomas Boucard,
We still have not heard back from you. Could you please check the comments above?
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-17T03:52:01.52+00:00

Hello @Thomas Boucard, We still have not heard back from you. Could you please check the comments above?
Thomas Boucard 20 Reputation points

2025-03-19T09:19:25.92+00:00

Hello which region can I use to have this feature disabled in Europe ?

And how is it acceptable to put additional hidden cost on a customer without any way to know it on deployment as the customer has the possibility to turn off this feature ?
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-19T14:22:21.6066667+00:00
Hello @Thomas Boucard

You can use these regions in Europe to have Availability Zones (AZs) disabled:

Germany West Central (You can turn off AZs)

North Europe (You can turn off AZs)

Switzerland West (AZs are already off by default)

From this MSDOC Microsoft Azure provides Availability Zones for Notification Hubs, with a charge of $350/month across all tiers . However, Availability Zones feature will be automatically enabled / disable based on the regions.
Thomas Boucard 20 Reputation points

2025-03-20T16:49:09.6466667+00:00

Thank you for this, it seems to solve the current issue.

Accepted answer

0 additional answers

Your answer

Bhargavi Naragani 6,130 Reputation points Microsoft External Staff Moderator

2025-03-04T21:00:09.15+00:00

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.
Bhargavi Naragani 6,130 Reputation points Microsoft External Staff Moderator

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 6,130 Reputation points Microsoft External Staff Moderator

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.
Thomas Boucard 20 Reputation points

2025-03-11T14:09:57.7266667+00:00

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
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-13T15:50:44.41+00:00

Hello @Thomas Boucard, Could you please review the comments above?
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-14T06:42:57.8266667+00:00

Hello @Thomas Boucard,
We still have not heard back from you. Could you please check the comments above?
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-17T03:52:01.52+00:00

Hello @Thomas Boucard, We still have not heard back from you. Could you please check the comments above?
Thomas Boucard 20 Reputation points

2025-03-19T09:19:25.92+00:00

Hello which region can I use to have this feature disabled in Europe ?

And how is it acceptable to put additional hidden cost on a customer without any way to know it on deployment as the customer has the possibility to turn off this feature ?
Sampath 3,750 Reputation points Microsoft External Staff Moderator

2025-03-19T14:22:21.6066667+00:00

Hello @Thomas Boucard

You can use these regions in Europe to have Availability Zones (AZs) disabled:

Germany West Central (You can turn off AZs)

North Europe (You can turn off AZs)

Switzerland West (AZs are already off by default)

From this MSDOC Microsoft Azure provides Availability Zones for Notification Hubs, with a charge of $350/month across all tiers . However, Availability Zones feature will be automatically enabled / disable based on the regions.
Thomas Boucard 20 Reputation points

2025-03-20T16:49:09.6466667+00:00

Thank you for this, it seems to solve the current issue.

Answer 1

Hello @Thomas Boucard,

The issue has nothing to do with the deployment script you shared, as the behavior remains the same with both the Portal and the script.

In the Italy North region of Azure, you might see an option to turn zone redundancy on or off in the portal. However, even if you try to disable it, Azure still keeps it on by default. This is because Azure has rules to make sure services stay reliable and protected from failures. So, even though the setting looks like you can change it, Azure automatically keeps zone redundancy enabled to ensure everything runs smoothly.

If you find that zone redundancy is enabled despite disabling it in the portal, it means Azure enforces this for the Italy North region by design.

Some regions, like France Central or Poland Central, have zone redundancy enforced at the UI level, meaning you can’t even toggle the setting. In contrast, Italy North allows toggling in the UI but still enforces zone redundancy in the backend. If you need complete control over this setting, you may want to deploy your resources in a region where zone redundancy can be fully disabled.

You can use these regions in Europe to have Availability Zones (AZs) disabled:

Germany West Central (You can turn off AZs)
North Europe (You can turn off AZs)
Switzerland West (AZs are already off by default)

From this MSDOC Microsoft Azure provides Availability Zones for Notification Hubs, with a charge of $350/month across all tiers . However, the Availability Zones feature will be automatically enabled or disabled based on the regions and the above condition.

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.

Share via

Availability zone enabled for notification hub even when explicitly disabled

0 additional answers

Your answer