University of Oregon Advises Cell Phone 911 Calls Amid Microsoft 365 Service Degradation

What the University of Oregon said​

The alert went out at noon on Nov. 12, 2026. The UO Alert's wording was short. Microsoft services, including email and Teams, are degraded. Use cell phones for 911 calls. It pointed readers to status.uoregon.edu. KPIC and KCBY each ran the same local report at 12:07 p.m. They are duplicate station pages, not independent confirmation, and both say some students and staff may have trouble reaching email and Teams.

The university's service-status page was more detailed. At 12:30 p.m. it listed Email and Additional Services as Partially Unavailable. At 12:31 p.m. it did the same for Microsoft 365. It also listed Telephones as Partially Unavailable at 12:30 p.m.

The status comment said Microsoft was still working on the issue. The university named these affected services:

• Email and calendars
• Teams
• OneDrive
• SharePoint
• Copilot
• "Others"

It also warned that UO voicemail may be affected.

What the 911 advice does and doesn't mean​

The sources do not say 911 is down. The university tells people to use cell phones for emergency calls, and it says voicemail and its Telephones category may be affected. The likely reason is a dependency. Many universities run telephony, voicemail and softphone features through Teams and Microsoft 365. I am inferring that from general industry practice. UO's status page doesn't explain the link.

So the instruction reads as a precaution. It tells people not to rely on a campus phone or a Teams-based line for emergencies while Microsoft is unstable.

What Microsoft reported​

Microsoft's public account of the incident differs in scope from UO's.

• Incident ID. The incident was logged as EX1550543. Per the same report, affected connection methods could include Outlook on the web, MAPI, Exchange ActiveSync and the REST API.
• Initial scope. Microsoft said it was investigating reports of users having trouble reaching Exchange Online mailboxes through multiple connection methods in the Americas. It later confirmed the issue may affect Microsoft 365 connectivity for users in any region.
• Mitigation. Microsoft said it had paused all deployments, was moving additional traffic off the affected infrastructure, and was restarting affected servers.
• Classification. The admin center classified the incident as a Service Degradation.
• Admin center trouble. Some users also had trouble reaching Microsoft's administrative portal during the outage. That limited admins' view of what was going on.

Microsoft's incident is about Exchange Online mailbox access. UO described broader degradation across its Microsoft environment. The evidence doesn't prove that the Exchange incident caused every affected UO service. It is plausible, because Microsoft 365 shares identity and connectivity layers, but nothing published confirms it. As of the reporting I reviewed, no root cause had been published for UO's own symptoms, and no restoration time had been given.

Downdetector counts also vary by outlet. One report cited complaints surging past 65,000 at one point, while KPIC's related national story cited more than 130,000 as of 2 p.m. EST. These are user-submitted figures and not a Microsoft measure of affected customers.

Practical takeaways for campus and enterprise IT​

1. Know your emergency alert channels. UO says alerts may be emailed to all @uoregon.edu accounts and posted on its Alerts page. People can opt in to text alerts through DuckWeb, by texting a campus code to 333111, or through the UOregon Mobile app. The codes are UOEUG, UOPDX and UOOIMB. UO advises choosing one sign-up method, because several methods can produce duplicate notifications. An email-only alert would be useless in an outage like this one.
2. Don't make Microsoft 365 the only path for emergency communication. Email, Teams, voicemail and softphones can fail together. Keep a separate channel for alerts, such as SMS or a mobile app.
3. Check tenant health in the right place. In the Microsoft 365 admin center, open Health > Service health and look for EX1550543 and any related multi-service entry. If the portal itself is down, fall back to Microsoft's public status channels.
4. Avoid needless client changes. Resetting profiles or reconfiguring Outlook during a service-side incident rarely helps and can add problems once service returns.
5. Keep the post-incident report. Microsoft's final write-up is what you'll need to explain the outage to leadership or compliance teams.

Bottom line​

The verified facts are limited but clear. A UO Alert at noon on Nov. 12 said Microsoft services were degraded and told people to use cell phones for 911. The university's status page listed email, Microsoft 365 and telephones as partially unavailable. Microsoft separately acknowledged an Exchange Online incident, EX1550543, that spread beyond the Americas.

UO's status page refreshes automatically, so it is the place to watch for restoration. This is also a reminder for any IT shop. Teams, voicemail and email share a lot of cloud plumbing, and your emergency plan shouldn't depend on all of it working.