
ComplianceOne's Client Advisory: Action Recommendations Following the Recent Microsoft 365 / Azure Service Outage
The recent Microsoft service outage, which affected Outlook, Teams, SharePoint, authentication services, Defender and related cloud services, highlights the operational and regulatory risks of relying on a single third-party technology provider. This advisory sets out the actions we recommend all Licensed Corporations (LCs) take to assess the impact on their business, address any gaps, and meet the SFC’s expectations on operational resilience, third-party dependency management, business continuity and incident reporting.
I. Business Continuity Plan (BCP)
LCs are required to document, test and remediate their BCPs. We recommend the following:
Complete a formal BCP test before 31 December 2026 if none has been conducted in 2026 to date.
Include a “critical cloud or identity provider unavailable” scenario in the test, as the recent outage demonstrates that such an event is a realistic supervisory concern.
Ensure the test covers, at a minimum:
Loss of email, Teams, SharePoint, Defender and Multi-Factor Authentication (MFA);
Break-glass administrator access that is independent of the primary tenant;
Fallback client communication through approved voice, SMS or secure channels;
Regulatory filing and deadline management; and
Restoration of electronic data storage provider (EDSP) and regulatory records within the defined Recovery Time Objective (RTO) and Recovery Point Objective (RPO).
Identify the business functions affected, including trading, order routing, pricing and valuation, settlement, market data, regulatory filings, client communications, recordkeeping, AML/KYC and supervision.
Determine whether any client orders, disclosures or regulatory submissions were delayed or failed.
Document the scenario, participants, timeline, actual RTO/RPO achieved, failures identified, responsible owners and remediation dates.
As best practice, have both the Manager-in-Charge of IT (MIC-IT) and the Compliance Officer review and approve the BCP test results.
II. Notification and Active Communication
LCs are expected to communicate promptly with clients and key service providers when operations are disrupted.
Clients
Proactively notify clients where services are delayed, reports are missed or client-facing functions are affected.
Use pre-approved fallback channels, such as sms, non-Microsoft secure email, telephone or a client portal.
Key service providers and vendors
Notify custodians, brokers, administrators, market data providers, EDSP vendors and the firm’s cloud provider.
Confirm each vendor’s incident status, estimated time of recovery and whether any sub-processors were affected.
Obtain written confirmation of any Service Level Agreement breach and the vendor’s remediation commitments.
III. Recordkeeping
Recordkeeping obligations continue during an outage. All business communications conducted through fallback channels must be preserved, as set out below.
Channel | Recommended Action |
Recorded voice (landline / mobile) | Archive in accordance with the normal retention policy. |
Approved SMS / secure messaging | Ensure messages are automatically captured in the firm’s archive. |
Fax | Retain transmission logs and copies. |
Online meetings (approved tools) | Save the recording and transcript to the archive. |
Temporary group chats | Use only approved and supervised platforms, and export to the primary archive as soon as practicable. |
IV. Post-Incident Look-Back Review
LCs should conduct a post-incident review addressing the following questions:
Did the BCP operate effectively, and were the RTO and RPO met? |
Were clients and service providers updated in a timely manner, and was there any off-channel communication? |
Were all business communications captured and retrievable? |
Were any SFC or other regulatory deadlines missed? |
Were any security gaps identified? |
V. Regulatory Notification (Para. 12.5 of Code of Conduct)
LCs should notify the SFC immediately if any of the following or other breaches of or non-compliance with legal or regulatory requirements has occurred:
Trigger | Example |
Missed regulatory filing or deadline | FRR filing or transaction report |
Inability to access or preserve regulated records | EDSP inaccessible or backup failure |
Disruption to supervision, AML or valuation processes | Orders left unmonitored or delayed pricing |
Client detriment or unreconciled instructions | Trade error or miscommunication |
Use of an unapproved channel resulting in a breach | Use of personal email for client orders |
References
1. Operational resilience and remote working
VI. How we can help?
Our team consists of experienced professionals with deep expertise in compliance, risk management, and policy review and development. We can accurately identify gaps between the regulatory expectations outlined in the relevant circulars and your company’s existing policies and procedures.
With a thorough understanding of the complexities of regulatory requirements, we provide tailored solutions and analyses to meet your specific needs and address any material deficiencies. Our expertise ensures that your company maintains full compliance with regulatory standards while comprehensively elevating your compliance practices to a higher level.
If you have any questions, please feel free to contact our compliance support team at any time.
[End of ComplianceOne's Client Advisory: Action Recommendations Following the Recent Microsoft 365 / Azure Service Outage]
For more details, please click on the title of the topic above.
=================================
~ Make It Right Today, Better Tomorrow ~
=================================
The Newsletter is for general information purpose only and is not intended to constitute legal or other professional advice.
For enquiries, please email to support@complianceone.hk or WhatsApp us at (852) 95164607.
Unit 1605, 16/F, West Tower, Shun Tak Centre,168-200 Connaught Road Central,
Sheung Wan, Hong Kong
Tel: (852) 39550277 www.complianceone.hk
