Service Status History
- Status >
- Microsoft Office 365
| Status | Comment | Updated |
|---|---|---|
| Partially Unavailable | Many people at the UO are currently unable to log in to Microsoft services, including UOmail, Teams, and others. UO staff believe that this is related to yesterday's (June 5) maintenance on our Duck ID system, separate from yesterday's widespread Microsoft service degradations. UO staff are working to restore access as quickly as possible, and have enlisted help from our Duck ID vendor.
|
|
| Partially Unavailable | 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.
|
|
| Info | 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. |
|
| Available | ||
| Available | Access to Microsoft 365 web applications was restored by the vendor around 11am PDT. |
|
| Partially Unavailable | Microsoft reports that some web apps are not accessible this morning. They are working to restore full service. |
|
| Available | ||
| Available |
|
|
| Info | 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:
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").
|
|
| Info | 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:
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").
|