Initial Thoughts This new feature capability offered in the Teams Admin Center is a nice complementary option to monitor devices and alert Admins when they go offline.
A great use scenario is for Conference Room devices or Executive level phones and while it’s not preventative, it does help Admins to react fast when devices go offline whether at a individual or site level.
Configuration Validate permissions to create a Team/Channel
Introduction Webinar is a new feature in Teams designed for up to 1,000 attendees with the ability to use a registration form, all the built in meeting features and a hidden feature of a Microsoft list where automation could be leverage for added control. I discovered this feature from Steven Collier Youtube’s channel here -> https://youtu.be/0NAxfP6gulw
Two quick guides from Microsoft with all the features and usage.
https://www.microsoft.com/en-us/microsoft-365/blog/2021/05/11/introducing-webinars-in-microsoft-teams-easy-professional-webinars-to-engage-customers/ https://teamworktools.azurewebsites.net/assets/TeamsWebinarsGetStartedGuide.pdf Step by Step:
Issue Recently encountered an issue where IP Phones (Polycom CCX) were unable to register to Azure AD and would not appear in the Microsoft Teams Admin Center list of IP Phone devices. Most times this should not be an issue except if the company has Intune enabled and endpoint manager resctricting devices from registering due to compliance policies.
Solution I knew there were some recommendations to exclude these phones from any device compliance as it could create more harm than good and not gaining a full set of features for these devices since all software and firmware can be pushed through the teams admin center.
Request To mask outbound caller ID by location with the corresponding office number DID which is owned by their direct routing solution and assigned to an AutoAttendant Resource Account.
Procedure We are not going to cover in detail how to assign a Direct Routing DID to a Resource Account but high level steps:
Create new Resource Account through Admin Portal or through Powershell ( AutoAttendant or CallQueue ); Autoattendant in our case Assign the proper license to the Resource Account Assign desired number to the Resource Account through powershell only Set-CsOnlineApplicationInstance -Identity ResourceAccountAA@domain.
Introduction After my final thoughts on my article PSTN call records with Microsoft Graph I wanted to move this data to Microsoft Lists with Power Automate
The benefits are quite a few as expressed before :
More granular control over how the process is automated via Microsoft Graph Access leveraging all the possible queries and correlating information that Graph offers.
This process allows to run as a scheduled task or even as an Azure function.
This post is an exercise and all credit goes to this blog - script on Github by leeford-Get-TeamsPSTNCallRecords
Getting the Reports There are a couple of ways to retrieve basic information for PSTN calls whether is Microsoft’s dial plans or direct routing. The easiest way would be from the Teams’ Admin Center -> Analytics & Reports -> Usage Report.
We can see some basic PSTN call information like time, caller, type of call, destination, duration, etc but the interface is small and having to navigate up and down and left - right can be less desirable
