Microsoft 365 Outage Delays Guelph and Wellington County Emails as Recovery Continues

What's confirmed locally​

GuelphToday and EloraFergusToday both reported on Friday, November 13. They are covering the same Microsoft incident and its effect on local governments. These are not two separate outages.

• City of Guelph: GuelphToday reports that the outage started hitting municipal services on Thursday, November 12, mostly email. A city spokesperson told the outlet that some functionality had returned. However, there may still be email delays or intermittent outages, so the city is not ready to say the disruption has ended.
• County of Wellington: Both outlets quoted a notice on the county website. It says email is still affected during recovery, which may reduce service quality, and that the county will post more updates as they become available.

The local reports don't say much beyond that. Neither municipality named other affected systems, gave a time for full restoration, or offered a different way to get in touch. EloraFergusToday covers only the county, so its report doesn't confirm anything about Guelph on its own.

Bottom line: Some service is back, nothing is fully fixed, and email is the main problem at both municipalities.

The bigger outage behind it​

Guelph and Wellington County are two of many organizations caught up in a much larger incident. According to Cybersecuritynews, a major Microsoft 365 outage disrupted cloud service access on November 12 and continued into November 13, 2026, as Microsoft worked to restore failing infrastructure.

On Thursday, Microsoft's status account said it was investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas. It pointed administrators to incident EX1550543 in the Microsoft 365 admin center. Cybersecuritynews reports that a wider update was later posted under MO1550821. It also reports that Microsoft said recovery actions are ongoing across affected Microsoft 365 infrastructure and progressing in phases.

Here is how the incident developed, according to several outlets:

• Scale: MacRumors reports that issues emerged on Thursday, November 12, with nearly 130,000 Outlook reports recorded on Downdetector shortly after 1 p.m.
• Exchange at the centre: MacRumors also reports that Microsoft's service health page warned that affected users may have trouble opening mailboxes through Outlook on the web, desktop, and mobile. Switching email apps won't fix this, because Exchange accounts accessed through other clients such as Apple Mail are also experiencing problems because the disruption involves Microsoft's underlying infrastructure.
• Other services hit: ABC7 lists the affected services as Exchange Online · Microsoft Teams · SharePoint Online · Microsoft Copilot 365 · Microsoft Defender XDR · Microsoft Planner · Microsoft To Do · Microsoft Intune · Microsoft Defender for Office 365. The System Design Academy explainer says Microsoft described the affected features as the ones that interact with Exchange Online and email services.
• Cause: Microsoft first blamed infrastructure "experiencing elevated load across multiple regions." CyberPress reports that Microsoft later clarified that the pressure did not come from increased traffic. Microsoft also said the servers we returned to service can become unresponsive again once they receive traffic; we're analyzing diagnostic data to determine what's triggering the behavior. System Design Academy notes Microsoft had not published a final root cause by 13 November.
• Not an attack, so far: System Design Academy reports that Microsoft said at 03:34 UTC on 13 November that there was no indication it was the result of malicious activity. Nothing in the local reports points to a cyberattack on either municipality.

Microsoft's phased recovery matches what Guelph and Wellington County are describing: some systems come back, some messages arrive late, and full recovery hasn't been declared. That doesn't mean the local status simply mirrors Microsoft's. The municipal statements are the best evidence of what's happening at those two councils. Microsoft's global notices are not.

Bottom line: This was an Exchange Online infrastructure failure that spread to other services. The root cause is still unconfirmed and Microsoft is recovering in stages, which is why the municipalities are seeing partial service.

What residents should do​

If you've emailed the city or the county since Thursday and heard nothing back, they probably aren't ignoring you. Your message may be stuck in a queue or may not have arrived yet.

1. Don't keep resending. Repeat emails add to the backlog. MacRumors reports that Microsoft has increased the email timeout window to 48 hours to help protect delayed messages while backlogs clear, so a delayed message may still arrive.
2. Call about anything urgent. For deadlines, permits or anything time-sensitive, use the phone number or other contact method listed on the municipality's official website. The local reports didn't name a specific alternative.
3. Look for updates. The county says it will post updates as they become available.

What IT administrators should check​

Smaller governments, schools and businesses with similar Microsoft 365 setups were probably dealing with the same problems this week. Here are some practical steps:

• Track both incident IDs. Check EX1550543 for mailbox connectivity and MO1550821 for the wider Microsoft 365 impact in the admin center's Service health section. CyberPress notes that Microsoft has not confirmed that every customer is affected, so check your own tenant instead of assuming.
• Working email doesn't mean everything works. Outlook may be fine while Teams, SharePoint, Planner or Intune features that depend on Exchange are still unreliable. Test each service your staff actually rely on.
• Check security tooling. CyberPress points out that Defender's Automatic Attack Disruption for device isolation is a cloud-correlated capability, so teams should verify that enforcement actions fired as expected. A gap in security automation during an outage deserves follow-up even if there's no sign of an attack.
• Tell staff and the public what's going on. Wellington County posted a notice on its website. Guelph gave a clear "not over yet" statement to reporters. Both approaches are better than staying silent, because they head off duplicate emails and frustrated calls.
• Prepare for the next one. Write down which teams lost which tools and for how long, and how people reached you when email was down. That record is useful when you review your outage plans.

Analysis: why it matters​

Many governments have moved to Microsoft 365 for good reasons: less server maintenance, built-in security, and fewer weekend patching jobs. The downside showed up this week. When Microsoft's shared infrastructure fails, a town in Ontario has the same problem as a large corporation and has to wait for the same fix.

To be fair, running Exchange on-premises didn't prevent outages either. It just meant your own team was responsible for fixing them. The practical lesson is to plan for cloud outages: keep phone lines and website notices ready as backups, and have clear public messages prepared. Guelph's careful "not over yet" message showed good judgment.

Bottom line: Guelph and Wellington County are recovering but not fully back to normal. Microsoft hasn't explained what caused the failure. Residents who need a reply quickly should phone instead of emailing again, and IT administrators should keep checking service health until Microsoft declares the incident resolved.