Maintaining call quality with Microsoft Teams is a process, not a onetime event. Network engineers and Microsoft Teams application owners need to be vigilant in preserving optimal call quality to ensure audio, video, and screen-sharing always remain satisfactory for end-users.
And vigilance is just as important before the pandemic as it is during the pandemic no matter where your users are working from. In some ways its more important today when working from home.
In this blog, we cover how the Microsoft Teams Call Quality Dashboard (CQD) combined with the audio/video synthetic transaction monitoring improves this maintenance process.
Teams Audio, Video and Messaging Synthetics
Once Microsoft Teams has been adopted for business collaboration, service owners will need a plan for ongoing monitoring and maintenance. At a minimum they will need to stay on top of the call quality with frequent visits to the Call Quality Dashboard. Proactive synthetics should be a part of everyone's Microsoft Teams monitoring strategy. Key, high-level benefits of proactive synthetic testing of Microsoft Teams include:
■ Network scenario what-if, testing and experimentation with no impact to the end-users
■ Faster network change management and root-cause capabilities
■ Immediate detection of outages before they impact end-users
■ Crowd-sourced benchmarks for networking jitter, network congestion, dropped packets and more
■ Network modeling of different topologies like SDWAN, VPN, Proxy, and Wi-Fi access points
By utilizing a proactive monitoring solution alongside the Teams CQD, professional network engineers can generate monotonic, Teams Audio and Video sessions which assist with diagnostics and Teams call quality maintenance. This improves productivity through multiple ITOps teams across multiple functions. Ultimately it improves business networking and productivity.
Better Together, Synthetics and the Call Quality Dashboard
Data for the CQD is collected in Near-Real-Time (NRT) and typically takes about 30-60 minutes before it is loaded. Synthetics can send data to its servers in real-time and contribute data to the CQD. This provides the best of both worlds; proactive monitoring from Synthetics with long term call classification from Microsoft in the Teams CQD.
A single sensor for monitoring Microsoft Teams Audio/Video streams can operate alongside any workload, physical or virtual computer. Monitoring can easily be deployed alongside a user's home or corporate machine if the home ISP or VPN connection is suspected.
Once deployed, Teams sensor will begin immediately collecting network and Teams telemetry, uploading it to monitoring servers in addition to the Call Quality Dashboard for data collection. The quality of experience (QoE) data that clients send to Microsoft 365 or Office 365 is the same from the synthetic Teams sensors. Importantly, this means no waiting weeks for enough real user samples to be generated for conference or peer-to-peer calls. Immediately benchmark and compare network telemetry. Immediately capture CQD data 24×7 for each sensor location and each network configuration.
Easy Quality of Service (QoS) What-If Scenarios
Quality of Service (QoS) for Microsoft Teams is critical for optimizing audio and video streams. When configured properly end-to-end in a network, QoS policy and settings enable network traffic from Microsoft Teams to be prioritized versus other traffic on the network. Voice, video, and screen share streams get dedicated ports of network bandwidth.
But Quality of Service configuration can be tricky to establish and ensure is operating well. Often new network components are introduced, settings lost or changed, and possibly new routing introduced. Ensuring QoS settings are properly established and maintained is another continuous process that is made easier by the Call Quality Dashboard and Exoprise together.
Armed with Teams synthetic sensors, network engineers can adjust QoS shaping and receive immediate feedback from analytics as well as Call Quality stream classification built into the CQD from Microsoft. Without synthetics, administrators are forced to wait for long periods of time to collect enough samples to ensure end-to-end QoS is in place. Additionally, without synthetics there is a potential to more severely impact end-users during Teams calls.
For QoS to be effective, changes need to be made consistently and throughout the organization because any part of the call or network path can degrade QoS policies and priorities. This includes applying settings to all user PCs or devices, network switches, routers, gateways, and proxies. Typically, these changes are made and coordinated across various teams which leaves more possibility of introducing errors. Customers typically experience savings throughout the year with QoS implementation.
Crowd-Sourced Network and Tenant Benchmarks
Wonder how your network or Teams user experience stacks up? With crowd source monitoring for Microsoft Teams, IT teams can instantly benchmark the Microsoft Teams digital experience and see how the network measures up against other enterprise customers.
The Value of Synthetics: Know Before That Important Teams Call
Knowing ahead of time about dropped calls, inability to connect with the Azure infrastructure or incidences of jitter, packet loss and high latency is critical to ensuring maintaining employee and business productivity. While the near-real-time collection and stream classification of the CQD is admirable, there are things that the CQD cannot provide:
■ Real time alarming for call failures and dropped calls
■ Alert notifications for poor network performance such as increased jitter, packet loss or Round-Trip Times (RTT)
■ Proactive notifications in advance of Microsoft Teams conference calls
■ Incident management integration with Microsoft Teams monitoring
■ Hop-by-hop contextual information about where in the network the problem exists
Service Availability from Every Vantage Point
While the CQD is great for stream classification it doesn't provide for availability metrics from each vantage point; branch office, network topology and user location. Utilizing synthetic Teams sensors from critical locations to capture accurate uptime and reliability statistics and compare to internal Service Level Objectives (SLOs) and Service Level Agreements.
Modern complex systems are easy to develop and deploy but extremely difficult to observe. Their IT Ops data gets very messy. If you have ever worked with modern Ops teams, you will know this. There are multiple issues with data, from collection to processing to storage to getting proper insights at the right time. I will try to group and simplify them as much as possible and suggest possible solutions to do it right ...
In Agile, development and testing work in tandem, with testing being performed at each stage of the software delivery lifecycle, also known as the SDLC. This combination of development and testing is known as "shifting left." Shift left is a software development testing practice intended to resolve any errors or performance bottlenecks as early in the software development lifecycle (SDLC) as possible ...
Overwhelmingly, business leaders cited digital preparedness as key to their ability to adapt, according to an in-depth study by the Economist Intelligence Unit (EIU), looking into how the relationship between technology, business and people evolved during the COVID-19 pandemic ...
Robotic Data Automation (RDA) is a new paradigm to help automate data integration and data preparation activities involved in dealing with machine data for Analytics and AI/Machine Learning applications. RDA is not just a framework, but also includes a set of technologies and product capabilities that help implement the data automation ...
There is no one-size-fits-all approach to changing the experience of employees during a pandemic, but technological innovation can have a positive impact on how employees work from home as companies design their digital workspace strategy. The IT team supporting this shift needs to think about the following questions ...
Downtime. It's more than just a bar on the Rebel Alliance's base on Folor. For IT Ops teams, downtime is not fun. It costs time, money and often, user frustration. It takes more than the Force to handle incidents ... it takes an intergalactic team. An effective incident management team is made up of people with many different skill sets, styles and approaches. We thought it would be fun to map the heroes of IT Ops with Star Wars characters (across Star Wars generations) based on their traits ...
Vendors and their visions often run ahead of the real-world pack — at least, the good ones do, because progress begins with vision. The downside of this rush to tomorrow is that IT practitioners can be left to ponder the practicality of technologies and wonder if their organization is ahead of the market curve or sliding behind in an invisible race that is always competitive ...
According to a new report, Digital Workspace Deployment & Performance Monitoring in the New Normal, 82% of respondents had changes in their digital workspaces due to the pandemic ...
There are a few best practices that DevOps teams should keep in mind to ensure they are not lost in the weeds when incorporating visibility and troubleshooting programs into their systems, containers, and infrastructures. Let's dive into these best practices ...