Service Status History

The UO community may experience problems with Teams, One Drive, and SharePoint due to a widespread service degradation, similar to this morning's, that is also affecting UOmail. The problems recurred around 1:15pm. Specifically, the search functionality may be unavailable in OneDrive and SharePoint, and a variety of Teams features may not be functioning correctly. Microsoft is sharing updates through its Microsoft 365 Status Twitter account.

Microsoft Teams, OneDrive, and SharePoint experienced unplanned service degradations today (Monday, June 5) from about 7:45am-8:45am Pacific Time. Exchange Online, the Microsoft service behind UOmail, was also affected.

Access to Microsoft 365 web applications was restored by the vendor around 11am PDT.

Microsoft reports that some web apps are not accessible this morning. They are working to restore full service. 

Since the recent transition to our new Duck ID platform, about 150 UO employee accounts have been affected by a small bug in routine account processing that unintentionally removed their Teams calling service. As of Friday, March 17, UO IT staff believe they've implemented a permanent solution to prevent more accounts from being affected, and that service has been restored for everyone who had been impacted. Anyone who is still experiencing the following problems in Teams should log out of Teams, then log in again to reactivate their service:

• Inbound calls to you are failing.
• Your dial pad has unexpectedly disappeared.
• When you try to call a non-UO phone number, the call fails and/or you get the following error message: "Couldn't complete the call. With your calling license, you can only call people within your organization. Talk to your IT admin to change your license."
• You're unable to participate in call queues that you belong to.

If logging out of Teams and back in doesn't solve the problem, please submit a ticket at Microsoft Teams support (select "Audio calling or Teams calling with dial pad").

Since the recent transition to our new Duck ID platform, about 150 UO employee accounts have been affected by a small bug in routine account processing that unintentionally removed their Teams calling service. As of Friday, March 17, UO IT staff believe they've implemented a permanent solution to prevent more accounts from being affected, and that service has been restored for everyone who had been impacted. Anyone who is still experiencing the following problems in Teams should log out of Teams, then log in again to reactive their service:

• Inbound calls to you are failing.
• Your dial pad has unexpectedly disappeared.
• When you try to call a non-UO phone number, the call fails and/or you get the following error message: "Couldn't complete the call. With your calling license, you can only call people within your organization. Talk to your IT admin to change your license."
• You're unable to participate in call queues that you belong to.

If logging out of Teams and back in doesn't solve the problem, please submit a ticket at Microsoft Teams support (select "Audio calling or Teams calling with dial pad").

UO staff have restored Teams calling service for all employees who were known to be impacted by ongoing problems with Teams calling. If you're experiencing any of the symptoms below, logging out of Teams and back in again should restore your service.

• Inbound calls to you are failing.
• Your dial pad has unexpectedly disappeared.
• When you try to call a non-UO phone number, the call fails and/or you get the following error message: "Couldn't complete the call. With your calling license, you can only call people within your organization. Talk to your IT admin to change your license."
• You're unable to participate in call queues that you belong to.

If logging out of Teams and back in doesn't solve the problem, please submit a ticket at Microsoft Teams support (select "Audio calling or Teams calling with dial pad").

UO staff continue looking for a permanent solution to prevent more accounts from being affected, working with our new Duck ID platform vendor to address this unintended side effect. Until a fix is in place, we will continue to proactively determine who is impacted each day and restore service for them.