Teams Device Health Monitoring and Reporting

By -

 Microsoft have snuck in a nice new feature into the Teams Admin Center (TAC).

We now see a new Notifications and Alerts menu tree and below this Rules.


When we go in here, we find only a single Default Device State Rule with no option to create any new rules (yet at least...)

When we edit this rule, we can see that we now have an option to monitor specific devices (think meeting room devices, collaboration bars etc.. here)



Under Device users we click on +ADD then enter the name of the account, or accounts if you are monitoring multiple devices, associated with the device, such as the resource account.


Then under Actions we can choose either Channel alert - to have a nice alert sent to our Teams Channel OR Webhook to use webhooks for alerting.

Finally ensure to select Active then Save.

Once set up this will take maybe 15 mins to replicate and set up. Then once a device has gone offline, the alert will be sent "Immediately", however it seems to take between 5-10 mins of polling interval for a device to report back to the TAC in the first place.

Its still a great feature to use.

The alert will come in to your chosen Teams Channel like this:


What I recommend you do is to create a new Alerts channel in your Team. This way you can also then set the notifications from your client to notify you on All Activity.



I imagine Microsoft will provide us with more options in the near future under this new menu so watch this space!

More details on Microsoft page here.

Comments

  1. OliviaDecember 14, 2023 at 9:42 AM

    Great post!

    ReplyDelete
  2. VictoriaDecember 14, 2023 at 2:31 PM

    Great insights on Teams device health monitoring and its potential impact! If you're intrigued by the intersection of health monitoring and technology, this article (https://www.cleveroad.com/blog/remote-patient-monitoring/ ) delves deeper into the realm of remote patient monitoring, offering a broader perspective on the evolving landscape.

    ReplyDelete

Post a Comment

Popular posts from this blog

Unassigned Numbers in Microsoft Teams using Audiocodes SBC

By -
Image
Unlike Skype for Business, Microsoft Teams does not natively support the handling of Unassigned numbers in the system. So if someone leaves your organisation and you remove the number from them and someone tries to call it, the call will drop. Technically, Teams will return a "404 Not Found" back to the SBC and back on to the telco. What we can do here is to then assign the 404 error to a Route, change the Destination Number (to a call queue or to your main Reception number for example) and route it back to Teams. To do this there are a few simple steps: Step 1 – Create an Alternative Reasons Set Step 2 – Configure existing Teams IP Group to use the SBC Alternative Routing Reason Set Step 3 - Create new IPG Step 4 – Create a new route in IP-to-IP Routing Step 5 - Manipulate Numbers Step 6 – Test  Step 1 – Create an Alternative Reasons Set The first thing we need to do is create an " Alternative Routing Set ", we find this under Setup >> Signaling & Media &
Read more

Skype for Business Edge Server replication troubleshooter

By -
Image
Many times in Skype for Business/Lync the main issue I come across is the deployment is that the edge server(s) fails to replicate. We see this when we run the command in Skype for Business Management Shell : Get-CsManagementStoreReplicationStatus and we see that the edge servers have False and no LastStatusReport or ProductVersion is shown as below. There are a number of things which can cause this and I am going to list them here. Try them in order here as this will contain the most common to the least common issues I found. Ø   Routing Ø   Firewall rules Ø   DNS suffix Ø   DNS (Local and LAN) Ø   Registry entries for SCHANNEL Ø   Certificates A check we can use to see if the replication is working can be done by trying to connect to the following URL from the Front End Server whish hosts the CMS: https://edgeinternalfqdn.domain.ie:4443/Replicationwebservice You should get the following screen: Without this response there is an issue,
Read more