Can not create new Notification Hubs/Namespaces via Portal or CLI

Question

question

ChrisNelson-5085 asked Apr 12, '22 SnehaAgrawal-MSFT commented Apr 18, '22

Can not create new Notification Hubs/Namespaces via Portal or CLI

I have been trying all day to create a new Notification Hub & Namespace, both using the CLI and Azure Portal. Every time (except once), they always fail. When I do az notification-hub namespace show, the "provisioningState": "Failed" is always returned. In the Portal UI, the Location is also empty. I can't use the Portal to change anything (get 404 errors when I try to save). I try to delete the incomplete resource, and it seems to go away, but within 5 minutes later, it suddenly shows back up in my resource group (so I can't actually delete them).

Is there some service issue going on? I've tried multiple resource groups, multiple subscripts, different Azure accounts--all with the same result.

azure-notification-hubs

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SnehaAgrawal-MSFT · Apr 13 at 06:55 AM

Thanks for reaching here! Could you please confirm if there is Any policy applied at your org level.
Also check if you are able to create other resource’s through portal in case Azure account issue.

I am able to create notification hub, Could you please confirm which region you are trying to deploy?

Also, Check this detailed official document for all the steps to be followed:

Please note that Notification Hubs requires version 2.0.67 or later of the Azure CLI. Run az version to find the version and dependent libraries that are installed. To upgrade to the latest version, run az upgrade.

Let us know.

0 ·

Answer 1 · 2022-04-14T02:10:09.333Z

ChrisNelson-5085 answered Apr 14, '22 SnehaAgrawal-MSFT commented Apr 18, '22

Thank you for the reply. When I tried again this morning, doing the exact same steps (our build server failed, along with manual processes) and everything started working. So I will chalk this up as an issue on the Azure side yesterday since it was across user accounts, subscriptions, regions and tool chains. The same exact steps that failed yesterday are now working today.

So, we can consider this resolved. It is unfortunate we don't know what truly happened, and I still have zombie Notification Hub Namespaces that I can't delete (since they were corrupted during the creation process it seems). I delete them, and within 5 or so minutes they reappear. I delete the resource group they are part of, and they and the resource group reappear. I've tried deleting from CLI and Portal with same result. Oh well, that is less of a concern.

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SnehaAgrawal-MSFT · Apr 18 at 04:32 PM

Thanks for sharing details, you may try deleting using REST which deletes an existing namespace. Please note this operation also removes all associated notificationHubs under the namespace.

Let us know.

0 ·

question