Newsbytes.PH reported that the advisory gave neither a restoration timetable nor a list of affected PJ365 services beyond Outlook. DZRH separately reported the same warning, adding that the Court was coordinating with Microsoft and would provide further updates as necessary. These are two accounts of the same disruption, rather than separate judiciary outages.
What the Court’s warning does—and does not—establish
The immediate concern is slower communication and transaction handling. However, neither report announces suspended hearings, unavailable filing systems, or changes to case deadlines. They also provide no alternative contact procedure or confirmation of whether messages sent during the disruption were delivered, queued, or lost. Those questions remain unanswered by the reported advisory.
That distinction matters: a warning about delayed responses is not evidence that every judiciary service is offline. The Court’s statement establishes an impact on PJ365 and Outlook, but does not quantify the number of affected users or transactions.
Microsoft’s broader service disruption
According to Newsbytes.PH, Microsoft acknowledged problems primarily involving Exchange Online. The company said servers had unexpectedly become unavailable, increasing pressure on the remaining infrastructure, and described recovery efforts involving server restoration and traffic redirection. That account describes an availability problem; it does not establish a cyberattack or a final technical root cause.
Microsoft’s public service-health snapshot, timestamped 00:56 UTC on November 13, listed service degradation for Microsoft 365 business or enterprise services and Microsoft consumer products. That corroborates a wider disruption, but does not establish when PJ365 would recover or which individual judiciary functions were affected.
A useful first check for Microsoft 365 administrators
For IT teams investigating similar symptoms, Microsoft’s documented first step is to check service health before spending time troubleshooting individual computers. The company provides an organization-specific incident view in the Microsoft 365 admin center.
Administrators with an appropriate role, including Service Support admin or Helpdesk admin, can:
- Sign in to the Microsoft 365 admin center.
- Open Health > Service health.
- Select the relevant active issue to inspect its affected services, user impact, latest update, and recovery status.
If the admin center cannot be accessed, Microsoft directs administrators to its public service-status page. If an organization is experiencing a problem that is not listed, the service-health dashboard also provides Report an issue. These are Microsoft’s general administrative procedures, not special instructions issued by the Supreme Court.
Finally, recovery in progress is not the same as recovery complete. Microsoft distinguishes “Restoring service” from “Service restored,” with the latter indicating that corrective action has returned the service to a healthy state. For organizations communicating with affected users, that is a useful boundary: report the documented impact and recovery status, rather than promising normal service before it has been confirmed.