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. Most messages in the latter category were delivered into people's mailboxes in a process completed around 12:30 p.m. today. UO staff are now doing another round of extended processing to ensure all affected users receive such emails. Depending on your email program, the messages may appear with either today's date or the original send dates.
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:
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 completed around 12:30pm today (Thursday, June 8). Those messages may appear new, or may appear in date order.
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:
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 completed at 12:21pm. Those messages may appear new, or may appear in date order.
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:
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 completed at 12:21pm. 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:
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 completed. 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:
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 early 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. The process to deliver the latter set of emails into people's mailboxes has now kicked off.
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 early 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.
