Last week, many businesses across the Gulf found out what happens when email, chat and shared files all stop at once. A global Microsoft 365 outage that began on 12 November took down Outlook, Teams, Copilot and other services for more than 24 hours. Microsoft announced full restoration on 14 November.
It was not a cyberattack. According to Arab News, Microsoft said a fault introduced during an earlier network capacity upgrade surfaced after a more recent network change, and that the failure was unrelated to cyber activity. The company has said it will publish a full report.
For most businesses the outage was an inconvenience. For some it stopped work. That difference usually comes down to planning done before the outage, not during it.
What the outage showed
Arab News spoke to businesses and schools across the region. A few patterns stand out.
- Approvals stalled. In the UAE, one group moved some transactions to WhatsApp because financial approvals that needed several people depended on email.
- Customer service slowed. Small businesses that run orders and supplier communication through Outlook struggled to respond to customers.
- Some companies barely noticed. One firm whose sales and logistics run on a separate system reported that only email was affected. Another had alternative accounts with a second provider ready to use.
- Scammers saw an opening. Kaspersky warned that outages are a natural cover for phishing that imitates Microsoft or internal IT, with fake password resets, cloned login pages and help-desk callers asking for remote access.
Why local data centres are not the same as resilience
Gulf organisations have rightly paid attention to where their data is stored, and in-country cloud regions help with data residency, speed and some physical failures. But as Arab News points out, regional data centres can still depend on a provider's wider global services, including the services that let users sign in.
Knowing where your data sits is only part of the answer. You also need to know what is required to reach it, and what you would do if several of those services failed together. If your email, your sign-in and your recovery instructions all live with the same provider, an outage can take them all out at the same moment.
A continuity checklist for Microsoft 365 users
None of these steps requires leaving Microsoft 365. They make sure one outage does not stop the business.
- Agree a backup communication channel now. Decide which tool staff will use if Teams and Outlook are down, who sets it up, and what may and may not be shared on it. Without rules, an urgent workaround can let a fraudulent payment slip through.
- Keep a contact list outside Microsoft 365. Store key staff, customer and supplier phone numbers somewhere you can reach without signing in to Microsoft.
- Make sure critical files are available offline. Use OneDrive's offline sync for the documents people cannot work without, and keep a protected copy of key records.
- Keep recovery instructions off the failing system. Your continuity plan and IT runbooks are no use if they sit in SharePoint during a SharePoint outage. Keep a printed or separately stored copy.
- Have an emergency admin account ready. Keep at least one secured "break-glass" administrator account, documented and tested, so you can still manage your tenant when normal sign-in paths are in trouble.
- Write down how approvals work during an outage. If payments need email sign-off, agree a fallback that still records who approved what.
- Warn staff about outage-themed phishing. Give them a single, known source of status updates, and remind them never to share passwords or codes with anyone offering to "restore access".
- Ask your suppliers the right questions. When you review cloud contracts, ask about recovery-time commitments, how you will be kept informed during an outage, and how you would retrieve your data if you left.
Put a price on an outage
Spending on backup arrangements is easier to justify when you know what a day without email costs: delayed orders, unanswered customers and a backlog of work. Work out which services must keep running and which can wait, and focus your effort on the first group.
Microsoft's full incident report, when it arrives, will be worth reading. Use it to check your own arrangements against what actually failed.
If you would like help reviewing your Microsoft 365 setup, emergency access or backup arrangements, contact our team.