Update - We are continuing to investigate this issue.
Mar 20, 15:48 MDT
Update - Both Polycom and Microsoft have created dedicated environments for testing this issue to try to determine the root cause of the packet loss. In the meantime, we are both exploring potential mitigations to circumvent this in the interim.
Mar 8, 14:22 MST
Update - We're looking into the network path to pinpoint the source of potential packet loss. In addition, we're preparing to capture a recurrence of the issue for fresh data to analyze.
Feb 25, 18:38 MST
Update - The investigation is ongoing, meanwhile, we are preparing to capture a recurrence of the issue in order to pinpoint the source of potential packet loss within Microsoft's network infrastructure. Next update by 6pm Mountain time today.
Feb 25, 12:09 MST
Update - We've determined that the previously identified portion of Microsoft infrastructure that facilitates traffic balancing in the affected environment is not a contributing factor to the intermittent impacts. We're verifying the health of additional network devices in the affected path to isolate the cause of the problem. Next update: February 25, 11am Mountain.
Feb 22, 16:19 MST
Update - We continue to work on this topic with Microsoft and will provide another update in 2 hours.
Feb 22, 14:15 MST
Update - We're continuing our investigation with Microsoft into the network path of affected traffic. We're also working to validate whether a degraded portion of Microsoft infrastructure tasked with balancing request traffic may be contributing to this problem. Next update by: Friday, February 22, 2019, at 2:00 PM Mountain. LY173946 has been updated with the same details.
Feb 22, 11:19 MST
Update - We're continuing to identify the origin of the packet loss which, due to the intermittent impact of the issue, is taking more time than initially expected. We will continue investigating overnight (NALA hours) and will provide an update in the morning.
Feb 21, 18:30 MST
Update - Due to the intermittent nature of the issue, it is taking longer than expected to isolate the specific cloud infrastructure responsible for the packet loss. Microsoft continues to review network traces to identify the cause of the issue.
Feb 21, 16:37 MST
Update - We are still investigating this topic. Note, Microsoft is also posting updates with known impacted tenants via their Service Health Dashboard under: LY173946.
Feb 21, 14:11 MST
Investigating - Video endpoints connected via RealConnect for O365 (Skype for Business) interop calls may experience intermittent video and/or audio issues. We are investigating this with Microsoft.
Feb 21, 11:42 MST