On a Thursday afternoon in November, the email systems of Michigan's state government fell silent along with a much larger web of users across the country, as a widespread Microsoft 365 outage swept through Outlook, Teams and Copilot. It is the kind of event that reminds us how much of public work now rests on infrastructure owned by distant companies, where a fault in one place can halt a capital city's correspondence in an instant. As of the afternoon's reports, neither the cause nor the path to recovery had been named, and the state had asked only for patience while the larger system was ma
Microsoft Outage Cripples Michigan State Government Email Across Outlook, Teams and Copilot
Email had stopped working across state government.
Mark
Why does a Microsoft problem become a Michigan state government story?
Mimi
Because the state's email runs on Microsoft's platform. When Microsoft's service failed, the state's offices lost email along with it. The department's post just before 3 p.m. made that public.
Mark
What did the state actually tell people to expect?
Mimi
That responses to emails may be delayed, and that it would post updates when Microsoft restores its applications. It didn't promise a time.
Luke
Worth saying plainly: we don't know the cause. Microsoft said it was investigating and that the issue may affect connectivity for users in any region. That is not an explanation.
Mark
The numbers fell from 130,000 to about 68,000 between 1 and 3 p.m. Is that recovery?
Luke
Not necessarily. Downdetector counts user reports. A drop could mean services improved, or that people stopped reporting. And the state was still down at 3 p.m.
Mimi
Right, the two facts sit side by side. The national count was falling while Michigan's offices were still announcing trouble.
Mark
Teams and Copilot were hit too. Does that matter?
Mimi
It suggests the problem wasn't confined to one app. Thousands reported trouble with each, so offices likely lost more than email.
Luke
I'd keep that as an inference. The reporting says users reported problems with those apps. It doesn't say how Michigan's agencies were affected beyond email and Microsoft apps generally.
Mark
So what are we waiting on?
Mimi
A cause, a recovery time, and word from the state that email is flowing normally again.
Le Pouls
- Lansing's state offices went dark mid-afternoon as email stopped working across government, leaving staff unable to send or receive messages.
- Outlook reports on Downdetector surged to about 130,000 at 1 p.m., and though they eased to roughly 68,000 by 3 p.m., the disruption had not ended.
- Teams and Copilot faltered alongside Outlook, so the outage struck messaging and AI tools at the same time, widening the damage.
- Microsoft's status account confirmed a problem affecting connectivity in any region but offered no cause and no timetable for repair.
- The state's technology department promised updates once Microsoft restores service, and the wait for a root cause and full recovery continues.
On a Thursday afternoon in November, the email systems of Michigan's state government fell silent along with a much larger web of users across the country, as a widespread Microsoft 365 outage swept through Outlook, Teams and Copilot. It is the kind of event that reminds us how much of public work now rests on infrastructure owned by distant companies, where a fault in one place can halt a capital city's correspondence in an instant. As of the afternoon's reports, neither the cause nor the path to recovery had been named, and the state had asked only for patience while the larger system was made whole again.
Just before 3 p.m. on Thursday, the Michigan Department of Technology, Management and Budget posted a brief notice online. State offices, it said, were experiencing technical issues with email and other Microsoft applications. Across Lansing and throughout state government, messages had stopped moving.
The trouble was not confined to Michigan. A widespread outage across Microsoft platforms had reached users nationwide, and the state's email failure was one local face of a far larger disruption. The department warned that replies might be slow and promised updates once Microsoft restored its services, but it offered no timeline.
The outage tracker Downdetector offered a rough sense of the scale. Around 1 p.m., about 130,000 people had reported Outlook problems. By 3 p.m., the count had fallen to just over 68,000. Yet those are only user reports, not a full measure of who was affected, and they do not show whether service had truly returned.
Teams and Copilot were also failing, which made matters harder for an organization that relies on email, chat and shared tools all at once. Microsoft acknowledged the problem through its status account, saying it was investigating and had confirmed the issue could affect connectivity for users in any region. It had not yet identified a cause.
For now, the questions outnumber the answers: what triggered the failure, when full service will return, and how much backlog state offices will face once email resumes. The state has promised to keep people informed, and the coming hours will show whether that promise can be kept.
Just before 3 p.m. on Thursday, the Michigan Department of Technology, Management and Budget posted a short notice on social media. State government offices, it said, were "currently experiencing technical issues with email and other Microsoft apps." Across Lansing and the rest of state government, email had stopped working.
The cause was not local. A widespread outage affecting Microsoft platforms, Outlook among them, had knocked out the state's email systems. The department warned that responses to emails might be delayed and said it would share updates once Microsoft restored its applications. The notice did not give a timeline for recovery.
Michigan was one of many places affected. The Associated Press reported that users across the country had trouble with their email accounts and ran into errors across Microsoft's suite of apps. The state's problem was one local face of a much larger disruption.
The outage tracker Downdetector offered a rough measure of its scale. At 1 p.m., about 130,000 users had reported problems with Outlook. By 3 p.m., that count had dropped to just over 68,000. That is a meaningful decline, but the tracker counts user reports, not the number of people actually affected, and it does not say whether service had returned for those who stopped reporting. It also does not explain why the state's email was still down at the moment of its announcement.
Outlook was not the only service in trouble. Thousands of users also reported problems with Teams, Microsoft's workplace messaging app, and with Copilot, its AI assistant. For an organization like a state government, which can depend on email, chat and shared tools at once, the loss of several services together can be more disruptive than the loss of one.
Microsoft acknowledged the problem through its Microsoft 365 Status account. In a series of posts, the account said it was investigating reports of users experiencing issues. It also said it had "confirmed the issue may affect Microsoft 365 service connectivity for users in any region," language that points to a problem not limited to one area or customer. The posts, as reported, did not identify a cause.
What remains unanswered is a good deal. Neither Microsoft nor the state had said what triggered the outage, and neither had said when service would be fully restored. Michigan's technology department has promised updates when Microsoft brings its applications back. The things to watch are confirmation of a root cause, a recovery timeline, and whether state offices are able to work through the delayed email once service returns.
Citations marquantes
State government offices are currently experiencing technical issues with email and other Microsoft apps.— Michigan Department of Technology, Management and Budget
The issue may affect Microsoft 365 service connectivity for users in any region.— Microsoft 365 Status account
Envie de l'histoire complète ?
Lire l'original sur M Live Michigan ↗