Decision #339AcceptedTrack · Product Operations3 min read
Microsoft outage disrupts African banks' email and customer service
Microsoft's November 12 outage disrupted bank email in Zambia and Namibia. Core banking stayed online, exposing the gap between service availability and operational resilience.

Context
The Microsoft 365 outage began on Thursday, November 12, and continued into a second day.
Stanbic Bank Zambia and Standard Bank Namibia kept banking services fully available while email failed.
Affected Microsoft 365 services included Outlook, Teams, SharePoint and Copilot.
Microsoft cited elevated service loads, unexpected server unavailability and failed automated health checks.
Stanbic Bank Zambia, Standard Bank Namibia and RHB Bank notified customers about email disruption.
Priya Raman
A Microsoft 365 outage that began on Thursday, November 12, has left banks in Zambia and Namibia unable to receive or respond to customer emails even as their core banking services remain fully operational.
Which banks were affected, and what stayed online?
- Stanbic Bank Zambia said the global Microsoft outage temporarily prevented it from receiving and responding to email. The bank kept all banking services available and referred customers needing assistance to its contact centre.
- Standard Bank Namibia reported the same email limitation. Banking services remained fully operational, and customers needing help were directed to its customer centre.
- RHB Bank notified customers of a temporary email disruption. It warned that responses to email enquiries could be delayed and asked customers with urgent requests to use alternative support channels.
The notices from Zambia and Namibia document a communications failure, not an interruption to core banking. Both banks kept their transaction services available while directing customers toward telephone or digital support when primary email infrastructure became unavailable.
What caused the outage, and why was recovery uneven?
Microsoft attributed the disruption to “elevated service loads” and “unexpected server unavailability” following failures in automated health checks. The disruption continued into a second day as failed server recovery prolonged the global outage. Recovery remained uneven as Microsoft worked to restore affected services.
The affected services included Outlook, Teams, SharePoint, Copilot and other Microsoft 365 products. When several become unavailable simultaneously, a company can lose business correspondence, internal and external meetings, document management and file storage across multiple departments at once. Complaints from businesses and users in several markets have shown how far routine operations depend on a relatively small number of global technology providers.
Where can transaction risk emerge?
Capital markets add a sharper timing constraint. Customer instructions, investment enquiries and transaction-related correspondence can be time-sensitive, so an unavailable email channel adds pressure to customer-service teams and operational processes. The bank notices identify this exposure as a risk rather than evidence of failed transactions.
Across Africa, cloud dependence extends to banking, capital markets, manufacturing, healthcare, oil and gas, and professional services. Cloud applications support approvals, customer engagement, document exchange and internal coordination. Access failures can delay approvals, interrupt customer support, slow negotiations and leave the execution of business instructions uncertain.
What should business continuity cover?
Business continuity arrangements work only when companies can use them without the failed provider. For Nigerian businesses, the outage supports four concrete provisions:
- Secondary email infrastructure that remains available when the primary service fails.
- Alternative virtual-meeting platforms for internal and external conversations.
- Offline access to critical documents when shared repositories become unreachable.
- Clearly defined procedures for handling customer instructions during a disruption.
Companies may also need to test these arrangements regularly rather than treating them as emergency provisions activated only after a disruption has occurred.
Operational resilience means sustaining essential operations when primary technology infrastructure becomes unavailable. Stanbic Bank Zambia, Standard Bank Namibia and RHB Bank directed customers to contact centres or alternative digital support channels, preserving a route to assistance when email failed.
Yet switching applications alone offers limited protection if alternative services depend on the same provider. Continuity testing must therefore establish whether fallback infrastructure remains independent, not merely whether another interface exists.
What should product teams measure next?
The full number of African companies directly affected remains unknown; the financial-institution notices demonstrate the potential reach of a global failure rather than provide a continent-wide total.
Cloud platforms improve efficiency and reduce infrastructure-management costs, but concentrating workflows on one provider also concentrates operational risk. The forward-looking standard for product teams is whether customers can still approve work, handle instructions and receive support when Microsoft 365 becomes unavailable—a capability that may matter as much as the technology investment itself.
via businessday.ng (Source)
More from Priya Raman
Show full bio
News editor covering money, funding and market shifts around product management at Roadmap File.
65 articles