Azure Notification Hub - Certain Hubs Completely "Locked Up"

Question

Azure Notification Hub - Certain Hubs Completely "Locked Up"

Westfall, Nathan 0

I've got a really strange issue. I have two hubs in Azure Notification Hub that are "locked up". What I mean by this, is the SDK and API get timeouts trying to register new devices and I can't create new Access Policies in the Azure Console.

I wrote a test project that does a simple connect and register with the .NET SDK like our application is. It times out everytime we try it with one of these two hubs. If we switch hubs, it works immediately.

Both hubs that are "locked" are well below the devices and message limit, one of them being on the "Standard" tier.

Any guidance on what to do next? Can't figure out a way to get them running again... It's been over a day now.

Prabhavathi Manchala 1,055 Reputation points Microsoft External Staff

2025-04-25T23:22:36.8633333+00:00
Hi Westfall, Nathan,

It looks like some of your Azure Notification Hubs are completely unresponsive, with timeouts on SDK/API calls and issues even in the Azure Console. Since other hubs are working fine, the problem is likely specific to those affected hubs.

Possible causes include temporary service bugs, misconfigurations, or resource allocation problems. Outdated or faulty SDKs/APIs can also lead to registration failures.

Temporarily change the pricing tier (e.g., from Standard to Free and back) to refresh the backend and resolve locked states without losing data or configurations.

Please check the Azure Status Page to see if there are any ongoing issues with Notification Hubs.

Please Ensure your access policies are properly configured and not mistakenly revoked.

Use the Azure Notification Hubs REST API to test device registration and identify any errors.

Restart the affected hubs from the Azure Portal to fix temporary issues.

https://learn.microsoft.com/en-us/azure/notification-hubs/notification-hubs-push-notification-registration-management#example-code-to-register-with-a-notification-hub-from-a-backend-using-an-installation
Westfall, Nathan 0 Reputation points

2025-04-26T01:50:55.95+00:00

@Prabhavathi Manchala I tried all of the steps you provided with no luck. The only one I couldn't do is Restart the affected hubs from the Portal, as I could not find a way to do this. Is their documentation on that?
Prabhavathi Manchala 1,055 Reputation points Microsoft External Staff

2025-04-30T17:03:33.6066667+00:00

Hi Westfall, Nathan,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. 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.
Prabhavathi Manchala 1,055 Reputation points Microsoft External Staff

2025-05-02T16:57:54.6166667+00:00

Hi Westfall, Nathan,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. 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.

1 answer

Your answer

Prabhavathi Manchala 1,055 Reputation points Microsoft External Staff

2025-04-25T23:22:36.8633333+00:00

Hi Westfall, Nathan,

It looks like some of your Azure Notification Hubs are completely unresponsive, with timeouts on SDK/API calls and issues even in the Azure Console. Since other hubs are working fine, the problem is likely specific to those affected hubs.

Possible causes include temporary service bugs, misconfigurations, or resource allocation problems. Outdated or faulty SDKs/APIs can also lead to registration failures.

Temporarily change the pricing tier (e.g., from Standard to Free and back) to refresh the backend and resolve locked states without losing data or configurations.

Please check the Azure Status Page to see if there are any ongoing issues with Notification Hubs.

Please Ensure your access policies are properly configured and not mistakenly revoked.

Use the Azure Notification Hubs REST API to test device registration and identify any errors.

Restart the affected hubs from the Azure Portal to fix temporary issues.

https://learn.microsoft.com/en-us/azure/notification-hubs/notification-hubs-push-notification-registration-management#example-code-to-register-with-a-notification-hub-from-a-backend-using-an-installation
Westfall, Nathan 0 Reputation points

2025-04-26T01:50:55.95+00:00

@Prabhavathi Manchala I tried all of the steps you provided with no luck. The only one I couldn't do is Restart the affected hubs from the Portal, as I could not find a way to do this. Is their documentation on that?
Prabhavathi Manchala 1,055 Reputation points Microsoft External Staff

2025-04-30T17:03:33.6066667+00:00

Hi Westfall, Nathan,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. 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.
Prabhavathi Manchala 1,055 Reputation points Microsoft External Staff

2025-05-02T16:57:54.6166667+00:00

Hi Westfall, Nathan,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. 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.

Answer 1

Hi Westfall, Nathan,

Thanks for the update, you're right—there’s no way to restart a Notification Hub from the Azure Portal, and the issue seems to be that your hubs are stuck in a locked backend state, isolated to those two.

To fix this, create a new Notification Hub, copy the settings from the old one, and update your app to use the new hub. Devices will re-register automatically when the app runs again, ensuring no data loss. Additionally, switching to the Installation model for registrations can help prevent similar issues in the future. 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.

Let me know if you have any further Queries.

Share via

Azure Notification Hub - Certain Hubs Completely "Locked Up"

1 answer

Your answer