BLOG
Microsoft 365 Outage Recovery: Cyber Risks, SLA Credits and What to Do Next
As Microsoft 365 services come back online, businesses face a quieter but more serious threat: the rush to catch up.
When a global outage hits, attention naturally falls on the moment things break. Emails stop, meetings fail and teams scramble for workarounds.
But the recent Microsoft 365 disruption is a reminder that the most dangerous period can come later, when services return and everyone tries to make up for lost time.
WHY RECOVERY IS THE RISK WINDOW
When email flow resumes after a long outage, messages don't necessarily arrive neatly. Hours of delayed mail can land at once, sometimes out of order, with replies appearing before the messages they answer. Inboxes fill, ticket queues swell and phones ring. Every team is under pressure to clear the backlog quickly.
That is exactly the environment fraudsters look for. A high-profile outage gives them a near-perfect set of conditions:
- Cover. A fake message is far easier to miss among hundreds of genuine, delayed ones.
- A believable story. Everyone expects messages about Microsoft following an outage, so "re-verify your account" or "reconnect Outlook" may not immediately raise eyebrows.
- Pressure. Staff are busy and want to clear the backlog quickly. Urgency is one of a scammer's most powerful tools.
- Broken routines. When Teams or email is unreliable, the usual quick check with a colleague becomes harder and people can be more likely to act alone.
- Confusion. Out-of-order emails make it harder to establish the context of a conversation, creating another opportunity for a fraudulent message to slip through.
None of this is unique to Microsoft. It's a technology-agnostic moment that could follow any major disruption, whether a cloud outage, ransomware attack, power cut or supplier failure.
"There are sharks out there looking for opportunities, and that opportunity is chaos," says Lee Doughty, Director of Security, Resilience and AI Practice at Intercity. "Whenever the focus is on restoring normality, that is the ideal time for predatory activity. That's why it's OK to take your time, and to tell your teams the same."
The risk isn't just technical. It's human: tired, busy people making quick decisions.
SCAMS TO WATCH OUT FOR
The tactics aren't new, but they are getting harder to spot.
- Phishing is the most familiar: an email pretending to come from someone you trust, such as Microsoft, IT, a supplier or a customer, designed to get you to click a link, open an attachment, hand over a password or approve a payment. Following an outage, be particularly wary of unexpected password resets, "service restored" notices or invoices presented as delayed messages.
- Vishing, or voice phishing, moves the same trick to the phone. A caller claiming to be IT support or Microsoft may offer to help "restore access" and ask for login details, an authentication code or remote access to a device. When other communication channels have been disrupted, a phone call can feel more credible.
- Smishing does it by text message: a short, urgent SMS with a link to "fix your account" or confirm details. On a mobile screen, fake links and sender names can also be harder to check.
- AI-powered scams are raising the stakes. Generative AI can help criminals create fluent and convincing phishing messages at scale, while synthetic voice and video technology can make impersonation more believable. That makes independently verifying an unusual or high-value request increasingly important.
The common thread is that each one exploits trust and urgency. That's why one of the simplest responses is also one of the most effective: pause.
THREE THINGS YOU CAN DO RIGHT NOW
1. Give people permission to slow down.
Being rushed is when mistakes happen. Leaders should say explicitly that accuracy matters more than speed during recovery. Five minutes checking an email is better than five days dealing with the consequences of an incident.
2. Communicate what you know, and only what you know.
Customers and partners don't need promises about things you can't control. They need honest, regular updates. Use alternative communication channels where necessary, keep a record of the disruption, decisions and business impact, and resist the urge to overpromise on timelines.
3. Verify everything.
Treat any unexpected request for a payment, change of bank details, login credentials or authentication codes as suspicious until it has been independently confirmed through a trusted contact.
Be particularly wary of unsolicited messages or calls claiming to be from Microsoft or offering a solution to problems associated with the outage.
DON'T FORGET THE PRACTICAL FOLLOW UP
There's another reason to keep a good record of what happened during an outage: you may need it afterwards.
If your organisation experienced disruption, it's worth recording the impact while the details are still fresh:
- Which Microsoft services were affected
- Approximately how many users experienced disruption
- How long you were impacted
- Whether there was any significant impact on your business
This matters because customers affected by a Microsoft service disruption may be eligible for service level agreement (SLA) credits, depending on the circumstances and the terms of their agreement.
Eligibility isn't automatic and Microsoft ultimately determines whether a service credit applies. If you think your organisation may have been affected, keep a clear record of what happened and speak to your Microsoft provider about the appropriate next steps.
The same principle applies more broadly to any major technology outage. Don't just record whether a service was unavailable. Capture when it happened, who and what was affected, and the impact it had on your organisation. That evidence can be valuable long after services have returned to normal.
RESILIENCE IS A MINDSET, NOT JUST A SYSTEM
Outages like this test how organisations respond under pressure, not just how their technology performs.
There are two parts to recovering well. The first is immediate: give people permission to slow down, question unexpected requests and avoid letting the pressure to catch up create another incident.
The second is what happens afterwards. Keep a clear record of the disruption and its impact, understand what worked and what didn't, and use that evidence to strengthen your response to the next outage.
"Saying sorry to a customer for a late reply is far better than saying sorry for a data breach," says James Pearse, CTO at Intercity. "Take your time, check everything, and keep talking."
Technology will fail from time to time. Resilience is about making sure that when it does, the pressure to recover doesn't create a bigger problem than the outage itself.