Update on the partial outage affecting incoming email and other UO services:
Emails sent to affected accounts. During the outage (mainly on Tuesday), many emails sent to affected accounts bounced. However, other messages ended up in a limbo state within our systems. The process to deliver the latter set of emails into people's mailboxes has now kicked off. Those messages may appear new.
Incoming email flow. Restored for most affected users early Wednesday, June 7. Restored for remaining users early Thursday morning, June 8.
Teams private channel access. If you've lost access to private Teams channels, the owners or members of those channels can restore your access. If that's not possible, then submit a ticket at Microsoft Teams support.
Teams custom tags. Affected accounts that are missing from manually created tags in Teams can be manually added back.
Teams calling. Service has been restored. If you're still not seeing your dial pad, then log out of Teams and log back in again.
Summary. This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others. Service has been restored except as noted above.
Update on the partial outage affecting incoming email and other UO services:
Incoming email flow. Restored for most affected users late on Wednesday, June 7. Restored for remaining users early Thursday morning, June 8.
Emails sent to affected accounts. During the outage (mainly on Tuesday), many emails sent to affected accounts bounced. However, other messages ended up in a limbo state within our systems. We're working on a process to deliver the latter set of emails into people's mailboxes.
Teams private channel access. If you've lost access to private Teams channels, the owners or members of those channels can restore your access. If that's not possible, then submit a ticket at Microsoft Teams support.
Teams custom tags. Affected accounts that are missing from manually created tags in Teams can be manually added back.
Teams calling. Service has been restored. If you're still not seeing your dial pad, then log out of Teams and log back in again.
Summary. This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others. Service has been restored except as noted above.
Update on the partial outage affecting incoming email and other UO services:
Incoming email flow. Restored for most affected users late on Wednesday, June 7. Restored for remaining users early Thursday morning, June 8.
Emails sent to affected accounts. During the outage (mainly on Tuesday), many emails sent to affected accounts bounced. However, other messages ended up in a limbo state within our systems. We're working on a process to deliver the latter set of emails into people's mailboxes.
Teams private channel access. If you've lost access to private Teams channels, the owners or members of those channels can restore your access. If that's not possible, then submit a ticket at Microsoft Teams support.
Teams custom tags. Affected accounts that are missing from manually created tags in Teams can be manually added back.
Teams calling. Service has been restored. If you're still not seeing your dial pad, then log out of Teams and log back in again.
Summary. This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others. Service has been restored except as noted above.
Update on the partial outage affecting incoming email and other UO services:
Incoming email flow was restored for affected users late on Wednesday, June 7. Staff will monitor the service. If you're still have this problem, please submit a ticket at email and calendar help.
Emails sent to affected accounts during outage. We'll plan to provide an update on the fate of these messages once more information becomes available.
Teams private channel access. Affected accounts must be manually added back to any private channels. UO staff recommend working with other members of those channels to get your access restored. If that's not possible, then submit a ticket at Microsoft Teams support.
Teams custom tags. Affected accounts may be missing from manually created tags in Teams. They must be manually added back to those tags.
Teams calling. UO staff are doing cleanup to ensure service is restored to any remaining affected accounts.
Dropbox. Access has been restored for all but two affected users.
Microsoft services. Access has been restored.
UO Service Portal. Logins have been restored.
Summary. This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others. The primary reprocessing to restore affected accounts has completed. UO staff continue monitoring the situation.
Update on the partial outage affecting incoming email and other UO services:
Incoming email flow. We've received several reports this morning of inbound emails from non-UO senders being rejected. UO staff are investigating. If you're still have this problem, please submit a ticket at email and calendar help.
Emails sent to affected accounts during outage. We'll plan to provide an update on the fate of these messages once more information becomes available.
Teams private channel access. Affected accounts must be manually added back to any private channels. UO staff recommend working with other members of those channels to get your access restored. If that's not possible, then submit a ticket at Microsoft Teams support.
Teams custom tags. Affected accounts may be missing from manually created tags in Teams. They must be manually added back to those tags.
Teams calling. UO staff are doing cleanup to ensure service is restored to any remaining affected accounts.
Dropbox. Access has been restored for all but two affected users.
Microsoft services. Access has been restored.
UO Service Portal. Logins have been restored.
Summary. This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others. The primary reprocessing to restore affected accounts has completed. UO staff continue monitoring the situation.
Update on the partial outage affecting incoming email and logins to many UO services:
We've received several reports this morning of inbound emails from non-UO senders being rejected. UO staff are investigating. If you're still have this problem, please submit a ticket at email and calendar help.
We'll plan to provide an update on the fate of email messages sent to affected accounts during the outage once more information becomes available.
For anyone who has lost access to certain Teams channels, UO staff recommend working with other members of those channels to get your access restored. If that's not possible, then submit a ticket at Microsoft Teams support.
The primary reprocessing to restore affected accounts has completed. UO staff continue monitoring the situation.
UO staff are doing cleanup to ensure Teams calling is restored to any remaining affected accounts.
Dropbox access has been restored for all but two users.
All affected accounts should now be able to log in to the UO Service Portal and to access Microsoft services, such as UOmail, Teams, and others.
This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others.
Update on the partial outage affecting incoming email and logins to many UO services:
We've received several reports this morning of inbound emails from non-UO senders being rejected. UO staff are investigating. If you're still have this problem, please submit a ticket at email and calendar help.
We'll plan to provide an update on the fate of email messages sent to affected accounts during the outage once more information becomes available.
For anyone who has lost access to certain Teams channels, UO staff recommend working with other members of those channels to get your access restored. If that's not possible, then submit a ticket at Microsoft Teams support.
The primary reprocessing to restore affected accounts has completed. UO staff continue monitoring the situation.
UO staff are doing cleanup to ensure Teams calling is restored to any remaining affected accounts.
Dropbox access has been restored for all but 32 users. UO staff are working to restore their access.
All affected accounts should now be able to log in to the UO Service Portal and to access Microsoft services, such as UOmail, Teams, and others.
This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others.
Update on the partial outage affecting incoming email and logins to many UO services:
For anyone who has lost access to certain Teams channels, UO staff recommend working with other members of those channels to get your access restored. If that's not possible, then submit a ticket at Microsoft Teams support.
The primary reprocessing to restore affected accounts has completed. UO staff continue monitoring the situation.
We'll plan to provide an update on the fate of email messages sent to affected accounts during the outage once more information becomes available.
We've received a few reports this morning of inbound emails from non-UO senders being rejected. UO staff are investigating.
UO staff are doing cleanup to ensure Teams calling is restored to any remaining affected accounts.
Dropbox access has been restored for all but 32 users. UO staff are working to restore their access.
All affected accounts should now be able to log in to the UO Service Portal and to access Microsoft services, such as UOmail, Teams, and others.
This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others.
Update on the partial outage affecting incoming email and logins to many UO services:
The primary reprocessing to restore affected accounts has completed. UO staff continue monitoring the situation.
We've received a few reports this morning of inbound emails from non-UO senders being rejected. UO staff are investigating.
UO staff are doing cleanup to ensure Teams calling is restored to any remaining affected accounts.
All affected accounts should now be able to access Microsoft services, such as UOmail, Teams, and others.
We'll plan to provide status updates on the following when more information becomes available:
Dropbox license restoration for about 570 affected accounts.
Next steps for people who've lost access to certain Teams channels.
The fate of email messages sent to affected accounts during the outage.
UO Service Portal login restoration.
This outage was inadvertently caused by vendor maintenance on our Duck ID system the evening of Monday, June 5. About 4,600 active accounts were affected. Services impacted included UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others.
Update on the partial outage affecting incoming email and logins to many UO services:
About 4,600 active accounts are affected.
Services impacted include UOmail, Teams, and other Microsoft services, as well as the UO Service Portal, Dropbox, and possibly others.
All affected accounts should now be able to access Microsoft services, such as UOmail, Teams, and others, with a few caveats:
Some people are reporting that they've lost access to certain Teams channels. UO staff have requested Microsoft's help to resolve this.
Other Microsoft services may simply take time to fully restore (30 minutes or longer). If you initially get an error message saying you don't have a license, try again in a few minutes.
Processing to restore Teams calling service for about 1,600 people has been completed.
Affected accounts may still be unable to receive some email messages. Processing to restore inbound mail flow is taking much longer than expected. We don't have an estimate of when it will finish. (We will provide more information later about the fate of messages that were sent during the outage.)
Affected users are still unable to log in to the UO Service Portal. Processing to restore access is taking much longer than expected. To reach tech support, please contact the Technology Service Desk by phone (541-346-4357) or live chat. Please note that support volumes are currently high.
About 570 people lost Dropbox licenses. Processing to restore service may now be complete or nearly so.
This outage was inadvertently caused by yesterday's (June 5) vendor maintenance on our Duck ID system.
We plan to provide further updates tomorrow (Wednesday, June 7).
