Notification Service Issue, Cannot send push notifications (event test) and get credential info in azure notification hub

Question

Notification Service Issue, Cannot send push notifications (event test) and get credential info in azure notification hub

bfirkovskiy 25

We are currently unable to send push notifications due to a timeout issue.
This is affecting all environments, including production. It appears to be related to an issue on Azure’s side, which is causing delays and timeouts.

Logs when we try to get apple credentials:
{ "shellProps": { "sessionId": "69d73b1654834db9a8c1e6529eea0ec7", "extName": "Microsoft_Azure_NotificationHubs", "contentName": "APNSBlade" }, "error": { "message": "this._apnsCredential is not a function", "error": { "message": "this._apnsCredential is not a function", "name": "TypeError", "stack": "TypeError: this._apnsCredential is not a function\n at t._setCredsToFormElements (https://afd-v2.hosting.portal.azure.net/notificationhubs/Content/Dynamic/30lqZHZ9MKsN.js:1:10346)\n at https://afd-v2.hosting.portal.azure.net/notificationhubs/Content/Dynamic/30lqZHZ9MKsN.js:1:1415", "extension": "Microsoft_Azure_NotificationHubs" }, "code": null }}

bfirkovskiy 25 Reputation points

2025-06-03T10:22:14.1533333+00:00
Bhargavi Naragani 5,270 Reputation points Microsoft External Staff Moderator

2025-06-03T12:51:30.1+00:00

Hi @bfirkovskiy,

It seems like you're experiencing consistent failures across multiple environments (including Production) when Sending test push notifications, Retrieving Platform Notification System (PNS) credentials, Performing Authorization operations via Azure Notification Hub. These operations are showing Failed statuses with errors and timeouts, specifically tied to APNs (Apple Push Notification service) credential loading.

The error indicates a client-side JavaScript error within the Azure Portal UI, specifically in the Notification Hub blade that loads APNS credential forms. This is not an error from your configuration or app but appears to be an issue on Microsoft's end in the portal rendering logic.

Until Microsoft fixes this issue on their end, here’s what you can do:

You can manage your Notification Hub and APNS credentials without relying on the portal by using the Azure CLI or Azure REST API directly. Update or check credentials using:
https://learn.microsoft.com/en-us/rest/api/notificationhubs/
https://learn.microsoft.com/en-us/rest/api/notificationhubs/use-rest-api-backend
https://learn.microsoft.com/en-us/cli/azure/notification-hub?view=azure-cli-latest

If you haven’t already, we strongly recommend raising a ticket through the Azure Support portal so Microsoft can prioritize this issue: https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview

here's a message you can use:

We are experiencing issues with Azure Notification Hubs where viewing or updating APNS credentials throws a JavaScript error in the portal UI: this._apnsCredential is not a function. This is blocking push notification functionality across all environments. The issue appears to be in the portal blade for Notification Hubs. We request urgent assistance.

Check for ongoing service issues in your region: https://azure.status.microsoft/en-us/status

Hope this helps, if you have any further concerns or queries, please feel free to reach out to us.
Pook (Jirawat) 10 Reputation points

2025-06-03T13:52:02.99+00:00

I also got the same issue on C# SDK with following error, it just happened about 6 hours. Any comments?

Microsoft.Azure.NotificationHubs.Messaging.MessagingCommunicationException: The request has timed out after 0 milliseconds. The successful completion of the request cannot be determined. Additional queries should be made to determine whether or not the operation has succeeded..TrackingId:3f329a2f-87c6-48b6-becf-8ade69874df5,TimeStamp:2025-06-03T11:29:27.8002302Z ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 172.214.68.125:443

   at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)

   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)

   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)

   --- End of inner exception stack trace ---
Yaroslav Burinskiy 0 Reputation points

2025-06-03T16:17:50.6633333+00:00

Got the same issue from Azure Notification Hub with HTTP Client Timeout.
Dashboard also says about zero activity for all hubs.
Bhargavi Naragani 5,270 Reputation points Microsoft External Staff Moderator

2025-06-03T17:39:58.2933333+00:00

Hi,
If you're deploying through east us region,

It appears there is an ongoing outage affecting Azure Notification Hubs in the East US region. You can track the status here: Azure Status Page.

We've reached out to the product team for more details and will keep you updated here. Apologies for the inconvenience caused.

Accepted answer

0 additional answers

Your answer

bfirkovskiy 25 Reputation points

2025-06-03T10:22:14.1533333+00:00
Pook (Jirawat) 10 Reputation points

2025-06-03T13:52:02.99+00:00

I also got the same issue on C# SDK with following error, it just happened about 6 hours. Any comments?

Microsoft.Azure.NotificationHubs.Messaging.MessagingCommunicationException: The request has timed out after 0 milliseconds. The successful completion of the request cannot be determined. Additional queries should be made to determine whether or not the operation has succeeded..TrackingId:3f329a2f-87c6-48b6-becf-8ade69874df5,TimeStamp:2025-06-03T11:29:27.8002302Z ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 172.214.68.125:443

at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)

at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)

at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)

--- End of inner exception stack trace ---
Yaroslav Burinskiy 0 Reputation points

2025-06-03T16:17:50.6633333+00:00

Got the same issue from Azure Notification Hub with HTTP Client Timeout.
Dashboard also says about zero activity for all hubs.
Bhargavi Naragani 5,270 Reputation points Microsoft External Staff Moderator

2025-06-03T17:39:58.2933333+00:00

Hi,
If you're deploying through east us region,

It appears there is an ongoing outage affecting Azure Notification Hubs in the East US region. You can track the status here: Azure Status Page.

We've reached out to the product team for more details and will keep you updated here. Apologies for the inconvenience caused.

Answer 1

Hi bfirkovskiy,

Please confirm that your notification hubs are working okay now. Yesterday I tested mine in East US and it seems to be working fine. Below is latest update as of this writing:

What happened?

Between 06:52 UTC and 21:45 UTC on 03 June 2025, a platform issue impacted underlying service instances impacting Notification Hubs in the East US region. Customers experienced errors when sending notifications to recipients hosted in this region. Notifications or registrations attempted during the impact window will not be recovered, as the compute layer responsible for storing them was unavailable.

What do we know so far?

We identified that the service instances responsible for processing requests had become unhealthy. This unavailability of the compute layer prevented customer notifications from being processed correctly, resulting in the service disruption described above.

How did we respond?

06:00 UTC on 03 June 2025 – We received an alert via internal service telemetry indicating Notification Hub availability degradation in the East US region.

06:52 UTC on 03 June 2025 – Customer impact began.

07:00 UTC on 03 June 2025 – We identified an Active cluster as not being able to serve the traffic in the East US region.

08:30 UTC on 03 June 2025 – Our team's investigation found that the issue was with service instances on unhealthy cluster nodes. We engaged other internal teams to work on mitigating efforts to get the cluster running again.

13:00 UTC on 03 June 2025 – After further investigation, a parallel mitigation workstream was begun to build a new cluster. Work also continued to recover the previous cluster.

20:41 UTC on 03 June 2025 – The parallel cluster was deployed and transitioned to an active status to handle Notifications and traffic in East US. Customers should have experienced increasing success from this point. Teams monitored closely to validate complete mitigation.

21:45 UTC on 03 June 2025 – After a period of observation and confirmation from customers, we confirmed that Notification Hubs service requests had returned to pre-incident levels and customer impact was mitigated.

What happens next?

Our team will be completing an internal retrospective to understand the incident in more detail. We will publish a Preliminary Post Incident Review (PIR) within approximately 72 hours, to share more details on what happened and how we responded. After our internal retrospective is completed, generally within 14 days, we will publish a Final Post Incident Review with any additional details and learnings.

To get notified when that happens, and/or to stay informed about future Azure service issues, make sure that you configure and maintain Azure Service Health alerts – these can trigger emails, SMS, push notifications, webhooks, and more: https://aka.ms/ash-alerts

For more information on Post Incident Reviews, refer to https://aka.ms/AzurePIRs

The impact times above represent the full incident duration, so are not specific to any individual customer. Actual impact to service availability may vary between customers and resources – for guidance on implementing monitoring to understand granular impact: https://aka.ms/AzPIR/Monitoring

Finally, for broader guidance on preparing for cloud incidents, refer to https://aka.ms/incidentreadiness

Please click Accept Answer if the above was helpful.

Thanks.

-TP

bfirkovskiy 25 Reputation points

2025-06-04T06:10:27.4466667+00:00

Yes, notification hubs are working okay now.
Thank you!

Share via

Notification Service Issue, Cannot send push notifications (event test) and get credential info in azure notification hub

0 additional answers

Your answer