BCN Hosted - Notice history

Microsoft have confirmed that the incident has been fully mitigated and resolved.

Latest update from Microsoft as services begin to recover.

Azure Front Door - Connectivity issues - Observing recovery

Starting at approximately 16:00 UTC on 29 October, 2025, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue.

Current status:

We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement.

Customer configuration changes will remain temporarily blocked while we continue mitigation efforts. We will notify customers once this block has been lifted.

Some customers may also have experienced issues accessing the Azure management portal. We have failed the portal away from AFD to mitigate these access issues. Customers should now be able to access the Azure portal directly, and while most portal extensions are functioning as expected, a small number of endpoints (e.g., Marketplace) may still experience intermittent loading problems.

At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. This means we expect recovery to happen by 23:20 UTC on 29 October 2025. We will provide another update on our progress within two hours, or sooner if warranted.

Although we are seeing signs of recovery and have an estimated timeline, customers may also consider implementing existing failover strategies using Azure Traffic Manager to redirect traffic from Azure Front Door to their origin servers as an interim measure.

Learn more about Azure Front Door failover strategies for AFD: https://learn.microsoft.com/en-us/azure/architecture/guide/networking/global-web-applications/overview

This message was last updated at 19:57 UTC on 29 October 2025

Latest Update

Azure Portal Access Issues

Starting at approximately 16:00 UTC, we began experiencing Azure Front Door issues resulting in a loss of availability of some services. In addition. customers may experience issues accessing the Azure Portal. Customers can attempt to use programmatic methods (PowerShell, CLI, etc.) to access/utilize resources if they are unable to access the portal directly. We have failed the portal away from Azure Front Door (AFD) to attempt to mitigate the portal access issues and are continuing to assess the situation.

We are actively assessing failover options of internal services from our AFD infrastructure. Our investigation into the contributing factors and additional recovery workstreams continues. More information will be provided within 60 minutes or sooner.

This message was last updated at 16:57 UTC on 29 October 2025

Latest update from Microsoft

Azure Portal Access Issues

Starting at approximately 16:00 UTC, we began experiencing DNS issues resulting in availability degradation of some services. Customers may experience issues accessing the Azure Portal. We have taken action that is expected to address the portal access issues here shortly. We are actively investigating the underlying issue and additional mitigation actions. More information will be provided within 60 minutes or sooner.

This message was last updated at 16:35 UTC on 29 October 2025

The vast majority of devices have been remediated. Any remaining activities will be tracked through individual tickets.

Q&A SECTION

Q: What steps have been taken so far to investigate and remediate the issue?
A: BCN have worked directly with SonicWall and have mobilised a taskforce to identify, and rectify any affected devices.
This will take time as there are a larger number of devices affected however we are working around the clock and prioritising devices by their risk factor.

Q: Has our device been affected?
A: Yes - if you received an email regarding this from BCN, your device has been affected. You will receive confirmation from BCN once your device has been remediated.

Q: What further actions are planned to ensure full resolution and protection?
A: SonicWall have provided instruction on the steps taking to remediate the issue, these can be found here - Remediation Playbook. BCN will perform these steps on your behalf.

Q: What can my company do in the meantime to reduce the risks?
A: BCN recommend disabling SonicWall SSLVPN until you have received confirmation that your device has been remediated. This will impact any remote users who rely on SSLVPN to access work resources and as such BCN have not made this change by default however if you wish to disable SSLVPN please respond to this email to let us know.

Q: Will you let us know when our device has been remediated?
A: Yes - BCN will contact you to confirm upon completion.

Impacted clients have been contacted as BCN mobilise engineers to commence remediation as per the guidelines from SonicWall.