Microsoft Azure Service Interruption

Microsoft has confirmed that the Azure Front Door issue has been fully resolved, and all related services have stabilized. Aderant services are now functioning properly and operating sustainably.

Microsoft is preparing a Root Cause Analysis (RCA), which we will share once it becomes available.

Thank you for your patience and understanding throughout this incident.

We are seeing improved performance across all affected applications globally as Microsoft continues their recovery efforts. While Microsoft continues to remediate nodes across all regions, we expect to see degraded performance while accessing applications including intermittent connection errors. Refreshing the application typically reroutes user traffic to a node that is functional. We are not anticipating any additional steps from end-users required for on-premise connector applications. Our team is continuing to monitor and will provide updates as we get them.

Following our previous update, Microsoft recovery efforts remain underway, with nodes being restored and traffic re-routed through healthy infrastructure.

As recovery continues, some requests may still encounter intermittent failures or reduced availability. Microsoft is gradually reloading configurations and rebalancing traffic across a large number of nodes to restore full operational scale. This process is intentionally gradual to ensure stability and prevent overload as dependent services recover. Strong signs of improvement are being reported across affected regions.

Microsoft remains on track for full mitigation by 7:20 PM EST on October 29, 2025, and will communicate if recovery is achieved sooner.

🔗 https://azure.status.microsoft/en-us/status

Our Cloud Operations team continues to monitor the impact on Aderant services and remains in close coordination with Microsoft.

Following our previous update regarding the Azure Front Door (AFD) and DNS-related service disruption, we want to share the latest developments from Microsoft.

Microsoft has now completed deployment of the “last known good” configuration. As a result, customers may have already begun to see signs of recovery. Microsoft continues to actively restore full performance. As this work progresses, service availability is expected to steadily improve anticipating full recovery by 7:20 PM EST on October 29, 2025.

https://azure.status.microsoft/en-us/status

Our Cloud Operations team remains in close coordination with Microsoft and continues to monitor the impact on Aderant services. We will provide additional updates as new information becomes available.

Restoration in Progress

Following our last update regarding the Azure Front Door (AFD) and DNS-related service disruption, we want to share the latest developments from Microsoft.

Microsoft has confirmed that the issue stemmed from an unintended configuration change within AFD. In response, they initiated a rollback to the last known stable configuration and temporarily blocked all configuration changes to AFD services. As of now, Microsoft is actively working to restore full performance by recovering nodes and routing traffic through healthy infrastructure. As progress continues, service availability is expected to improve, though you may see intermittent errors until full recovery. Microsoft is anticipating full mitigation within the next four hours.

https://azure.status.microsoft/en-us/status

Our Cloud Operations team remains in close coordination with Microsoft and continues to monitor the impact on Aderant services. We understand how critical these services are to your operations and appreciate your continued patience.

We will provide further updates as new information becomes available.

We are continuing to closely monitor the ongoing Azure Front Door issue. Microsoft is actively working to resolve the underlying problem, and we remain in regular communication with their engineering teams.

At this time, we are still awaiting the next update from Microsoft. We will share additional information as soon as it becomes available.

Thank you for your continued patience and understanding.

Microsoft has indicated that an inadvertent configuration change may have triggered the incident.

Microsoft has taken two key mitigation steps:
• Blocking all configuration changes to AFD services
• Rolling back to the last known good configuration state

There is no confirmed ETA for completion of the rollback. Microsoft continues to work toward full restoration, and we will share another update as information becomes available.

Microsoft has reported an issue with Azure Front Door affecting access to some services and the Azure Portal.
Microsoft has implemented mitigation steps and is continuing to assess recovery options.

We remain in close communication with Microsoft.

Further updates will be provided within 60 minutes or sooner.

We are continuing to actively engage with Microsoft regarding the ongoing Azure incident impacting our services. We will continue to provide updates as new information becomes available.

Thank you for your patience and understanding.

We are investigating a Microsoft Azure incident impacting multiple services. Our engineering team is actively working with Microsoft to identify the root cause and restore service.