Azure Notifications Hub Deployment Fails "Invalid property properties.zoneRedundant"

Kieran Jeffery 25

Hi,

I'm trying to deploy Azure Notifications Hub, But I just get this error:

{
  "code": "DeploymentFailed",
  "target": "/subscriptions/********/resourceGroups/*******/providers/Microsoft.Resources/deployments/Microsoft.Template-20240225125023",
  "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",
  "details": [
    {
      "code": "",
      "message": "Invalid property properties.zoneRedundant; Property at path properties.name cannot be changed; Property at path properties.region cannot be changed; Property at path properties.namespaceType cannot be changed"
    }
  ]
}

I am the owner, and all my permissions seem to be in order to do this...

VenkateshDodda-MSFT 18,441 Reputation points Microsoft Employee

2024-02-26T04:49:31.1933333+00:00
@Kieran Jeffery Thanks for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.

To reproduce this behavior, I have tried deploying the notification hub from the portal by enabling availability zones and disaster recovery checkbox as true and the deployment/create operation got failed with the above error.

I am checking with internal team on this and will update you here once I hear back from them,

Meanwhile, can you try creating the notification Hub and Namespace using either PowerShell cmdlets or through AzCLI cmdlets.

New-AzNotificationHubsNamespace (to create Notification hub Namespace) and New-AzNotificationHub (to create Notification Hub).

az notification-hub namespace create (to create Notification hub Namespace) and az notification-hub create (to create Notification Hub).

Hope this helps. let me know if you have any further questions on this.
Ville Viitaharju 0 Reputation points

2024-02-26T08:17:25.0433333+00:00

I have same problem, but I'm disabling availability zones and disaster recovery as currently they seem to be very expensive (in 14 days it has cost us $175 just being there and we are just testing it).

Is there way to make sure those are disabled with "az notification-hub namespace create"?

Documentation doesn't mention zones at all and notification hub documention says that "Availability zones are enabled by default if you choose a region that supports the feature. There will be associated costs."
VenkateshDodda-MSFT 18,441 Reputation points Microsoft Employee

2024-02-26T08:49:40.6833333+00:00

Ville Viitaharju As mentioned in this documentation, Notification hub enables availability zone by default once it is enabled and you cannot disable.

Regarding the disaster recovery you can modify to disabled/None from portal using Paired Recovery Region option in the overview of the Notification Hub as shown below.
Ville Viitaharju 0 Reputation points

2024-02-26T08:53:09.2333333+00:00

@VenkateshDodda-MSFT
So how I make sure I disable availability zone when creating new resource?
That feature is very expensive.

Currently portal doesn't work (throws same error as OP) and az command doesn't have any way to disable (or enable) it.
VenkateshDodda-MSFT 18,441 Reputation points Microsoft Employee

2024-02-26T09:27:51.8966667+00:00

Ville Viitaharju I have tested in one of our subscriptions, using the cmdlets az notification-hub namespace create and az notification-hub create I am able to create the notification hub with Availability zones as disabled and Disaster recovery getting paired to respective paired region.

Also, we see that cloud shell is using the Api Version 2017-04-01 and portal is using api version 2023-10-01-preview for creating the resources.
Kieran Jeffery 25 Reputation points

2024-02-26T10:53:22.6733333+00:00

Thank you @VenkateshDodda-MSFT I did already manage to get it set up through the Azure CLI by first creating the namespace, then the Notification Hub. Seems to me like the portal is trying to set them up at the same time and that's what's causing the issue. Might be worth trying to set up a notification hub in the portal to an existing namespace and see if that works ok.

Thank you

Accepted answer

VenkateshDodda-MSFT 18,441 Reputation points Microsoft Employee

2024-02-27T04:14:06.65+00:00

@Kieran Jeffery Thanks for your patience on this.

Upon deeper investigations over engineering team has identified a bug and a fix has been rolled out to mitigate this issue. I have tested and able to create the notification hub from the portal.

I would suggest you validate from your end as well.

I hope the answer helps. Please let me know if you have any further queries.

Please accept as Yes if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.
Please sign in to rate this answer.
Kieran Jeffery 25 Reputation points

2024-02-27T05:25:43.6833333+00:00

Good work!

I have tested it now and it seems to be working fine through the portal!

Thannk you. :)
Sign in to comment

Azure Notifications Hub Deployment Fails "Invalid property properties.zoneRedundant"

0 additional answers