Announcement: Skype for Business Online Call Quality Dashboard updates (April 26th 2017)
Hi, I wanted to let everyone know about a recent update to the Skype for Business Online Call Quality Dashboard. We've recently deployed an update to the data model that powers the dashboard. This includes a few bug fixes and a couple of changes to address user feedback: IP Address dimensions now are shown using standard IPv4 or IPv6 notation. No more dashes! CallSetupFailureReason dimension has been remapped to easier to understand and more admin actionable classifications. Refer to https://support.office.com/en-us/article/Dimensions-and-measures-available-in-Call-Quality-Dashboard-in-Skype-for-Business-Online-e97aeeee-9e43-416f-b433-9cdd63d8874b?ui=en-US&rs=en-US&ad=US for more details. The following dimensions have been removed: MediaStackVersion FirstWifiSignalStrengthValue SecondWifiSignalStrengthValue FirstWifiBatteryChargeValue SecondWifiBatteryChargeValue Notes: If you have built custom detailed reports using filters using either an IP Address dimension such as SecondSubnet or CallSetupFailureReason you may need to manually update these filters. There may be very slight changes in stream counts with this new more accurate data model. If you see any dramatic delta in the data shown in the reports, please reach out to support. The WiFi dimensions that have been removed have alternative dimensions available such as SecondWifiSignalStrength. Refer to https://support.office.com/en-us/article/Dimensions-and-measures-available-in-Call-Quality-Dashboard-in-Skype-for-Business-Online-e97aeeee-9e43-416f-b433-9cdd63d8874b?ui=en-US&rs=en-US&ad=US for details. These data model changes also help enable some new upcoming reports. More to come :) /williamCall Quality Dashboard descriptions of dimensions and measures published
Hi, We've recently published an article describing all of the dimensions and measures exposed in Skype for Business Online Call Quality Dashboard. https://support.office.com/en-US/article/Dimensions-and-measures-available-in-Call-Quality-Dashboard-in-Skype-for-Business-Online-e97aeeee-9e43-416f-b433-9cdd63d8874b This article provides descriptions of the dimensions and measures, example values, typical reasons why a dimensions may be blank, explaination about the first and second endpoint concepts and explaination about the data types used in CQD. Feel free to post any questions or asks for further clarification about the fields exposed on CQD. thanks! /william Note: A couple of dimensions and measures around call setup failure reasons are being updated and added to CQD in the very near future. This article reflects these upcomming changes.
Using Azure Lighthouse and Azure Monitor for SAP Solutions to view telemetry across Multiple Tenants
Azure Monitor for SAP Solutions allows for telemetry data collection from Azure infrastructure and databases running SAP in one central location and for visually correlating telemetry data to illustrate the health of the SAP on Azure estate. Combining Azure Monitor for SAP Solutions with Azure Lighthouse allows for the creation of dashboards to show telemetry data across multiple subscriptions or even multiple Tenants.(CDR/QoE) data for Call quality performance - reporting trends and details
I am very interested to understand to hear the <pings> out there - you who use the data from Lync or Skype on-prem's QoE database - whether you consume it in it's raw format in the manner of a data scientist, or consume it through a 3rd-party-developed reporting app in the manner of a customer-experience-support analyst / investigator. Is it just me or does the SfBO reporting still leave something to be desired? There is some elementary reporting, but I am not seeing anything that matched Lync/Skype Monitoring Reports. There is a mountain of meta-data in the QoE database. Is that getting left behind? Microsoft did a good job creating simple report-query-templates in the Monitoring Report server that could render 80% of what most Telecom Managers would expect their team to know from a platform. And for the other 20%, ALL the data was simply... available at the customer's disposal (and/or a partner's disposal). For Voice Engineers, Support Analysts, and Service Owners, this was a dream come true. Performance data at our fingertips. Now, with Skype for Business Online, I seem to bottom out on report category / type templates that I am otherwise accustomed to leveraging in the Monitoring Reports. And I hear partners are unable to get access to the Call Analytics API, so this tells me - simply - that in Skype for Business Online, there is some data I am no longer able to access, that I would like to access. @ Microsoft: Are there still developments happening in this space? I would like to see the SfB Online window unlocked for me to get into my QoE data, so that I (or a partner) can render the data in more relative context, with custom filtering. Some of that data can be used to prove Skype is not the root cause of an issue. Next, I would like to also understand the product team's vision of reporting call quality - for calls made in Microsoft Teams. I guess you have a challenge... because the boil-the-ocean expectation is that we will see all platforms (Skype on Prem + Skype Online + Teams...) to be rendered into a one-report-viewing experience. Right? ;-) What is the road map and pending enhancements for CQD and/or Call Analytics, in general? Where / when does Teams sit on that roadmap? And... Will a customer be able to render their own meta-data or be restricted from it?
Windows updates on SRS V2 with Intune
I am having issues with Windows updates on my SRS V2 SP4's. They are managed in Intune, have maintainance windows set and auto reboot configured up, but after an update is pushed to them through Windows update they seem to not apply the update properly. The end result is that the morning after the device is not on the network and not avaialble for use. Normally a reboot fixes it, but i want to get to the root of the problem. Has anyone experienced something similar or know how to stop the issue?Dynamically route alerts to the right team.
Hello folks, After a discussion with a customer where they were expressing their “displeasure” with the number of alert notifications that the IT department was receiving from environments that were not critical but still in need of monitoring. I started thinking about how we could dynamically decide when, where, how, and to whom these alert notifications are sent. Then I remembered an interview with Aditya Balaji (PM for Azure Backup) where we discussed Azure Backup Alerts and monitoring and I remembered that in his demo they were using a Logic App to manage the delivery of alert notifications. I decided to try it and see if I could produce a way to limit the number of action groups in Azure monitor alerting while enhancing the “decision” flow of how the notifications are handled. Here’s what I came up with.Billing Reports for Phone System
Hi, Hoping to tap into the real-world experiences of Skype for Business IT Pros and get your honest feedback... :) We've been working with some select customers on a Billing Reporting solution for Microsoft Phone System. Now, we'd love to get feedback from a wider audience to understand how to make it better! Walkthrough video: More info at https://hubs.ly/H0b4F4b0 and any questions let me know. All feedback really welcomed and appreciated, thanks. -tom
