Earlier this morning, Teams Call Queues were unavailable. Callers were receiving a fast busy signal and unable to reach queues. Microsoft has re-routed impacted Teams Call Queue traffic to restore service while they work on the issue, which has resulted in queues being available for calls again. Information Service staff continue to monitor.

We're receiving reports that calls into Teams Call Queues are not available. Callers receive a fast busy signal and are unable to reach the queue. Other calling such as person-to-person and Amazon Connect queues appear unaffected. Microsoft is working to restore service.

We're receiving reports that calls into Teams Call Queues are not available. Callers receive a fast busy signal and are unable to reach the queue. Other calling such as person-to-person and Amazon Connect queues appear unaffected. Information Services staff are engaged.

We're receiving reports that calls into Teams Call Queues are not available. Callers receive a fast busy signal and are unable to reach the queue. Information Services staff are engaged.

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.

A few employees are still having problems with Teams calling as an unexpected side effect of the recent Duck ID platform transition. Specifically, the impacted individuals may experience the following problems:

• 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 you're having such problems with Teams calling, UO staff can address them if you submit a ticket at Microsoft Teams support (select "Audio calling or Teams calling with dial pad"). UO staff also continue to proactively determine who is impacted and restore service for them. About 40 people are still affected.

In addition, UO staff continue looking for a permanent solution to prevent more accounts from being affected, working with our new Duck ID system vendor. This morning's intended fix didn't work as expected.