Microsoft scam warning issued after global outage
Summarised from 2 outlets · Updated 16 Nov, 13:01 · Archive
Scammers are posing as Microsoft to steal login details following a global outage that disrupted services for 18 hours.
A global Microsoft outage lasting at least 18 hours on Thursday and Friday disrupted Teams, Outlook and Copilot, affecting emergency services, hospitals and councils across Norfolk. The Norfolk and Norwich University Hospital reported issues but said patient care was unaffected. Norfolk Constabulary experienced interruptions to online form submissions. By 12.30pm on Friday, Microsoft announced 'encouraging recovery progress in Europe' as services began to restore.
Scammers have already begun exploiting the disruption. HMRC has reported fraudulent calls from individuals posing as Microsoft staff, requesting HMRC usernames and passwords from people. Norfolk County Council Trading Standards has warned the public that Microsoft and HMRC will never request personal information or sign-in details via phone calls, texts or emails. The warning comes just days after the outage ended, targeting vulnerable individuals who may still be concerned about their accounts.
How it is being reported
- Urgent Microsoft scam warning issued in Norfolk just days after global outageNorfolk County Council Trading Standards has issued a Microsoft scam warning just days after a global outage that affected thousands in Norfolk.Norwich Evening News · 16 Nov, 12:30
- Urgent Microsoft scam warning issued in Norfolk just days after global outageNorfolk County Council Trading Standards has issued a Microsoft scam warning just days after a global outage that affected thousands in Norfolk.Eastern Daily Press · 16 Nov, 12:30
In this story: Norfolk County Council Trading Standards · Microsoft · HMRC · Norfolk · Norfolk and Norwich University Hospital · Norfolk Constabulary
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)