I’ve released a blog post about auto dialing with Microsoft Teams in 2020. A user has commented that the tool AutoHotkey in Version 2.0 is not working any longer with my script. The script is written for AutoHotkey Version 1.0 and the publisher of the software changed the script language in the latest version. Therefor the user asked if I could write an updated script. For me, enough reasons to write an updated blog post about how to auto dial a phone number with Microsoft Teams.
In this blog post, I will guide you through the steps to connect an Audiocodes MediaPack to Microsoft Teams. This allows you to use your analoge phones with Microsoft Teams. Of course, it is not the cheapest solution and there are other options. But with Microsoft Teams, you can easily control and manage an analoge phone. For example, you can restrict outbound call destinations by assigning a voice routing policy. Or you can monitor the call quality for analog phone.
In this blog post you can learn how to connect Spectralink IP DECT system with Microsoft Teams. I write about the requirements, which Spectralink hardware is supported for connecting with Microsoft Teams and how to configure the IP DECT server.
Microsoft supports to connect your Spectralink IP DECT system with Microsoft Teams thanks to the new Microsoft Teams SIP gateway. It allows you to connect native, certified SIP devices to your Microsoft Teams platform. Since September 2022 certified IP DECT systems are also supported.
In this blog post you will learn how to customize the music on hold in your Microsoft Teams environment. Microsoft announced this feature to be deployed in September 2022 and it allows us to define an own music on hold.
You archive this by configuring the new policy Hold Music in the Microsoft Teams Admin Center. Because it is a Microsoft Teams policy, you have the choice to set a new music on hold globally for all users or to define a music on hold for individual users.
In my first blog post about how to manage ownerless Microsoft Teams, I wrote about the standard tools by Microsoft. In this blog post, I will give you some inputs how to use the Microsoft Graph API in combination with SharePoint Online and Microsoft Flow to find ownerless M365 groups and to stay informed about ownerless teams or Microsoft 365 groups.
I will use the Graph API to get a report about the existing Microsoft Teams. This dataset is filtered on ownerless teams and is written to a SharePoint list. When stored in the SharePoint list, you can extend the solution by triggering a Microsoft Flow to notify the service desk, for example.
A few weeks ago, Microsoft announced a new milestone for the Microsoft Teams phone system – the Microsoft Teams SIP gateway will support IP DECT systems soon. A few vendors are already known and one of them will be Poly and their IP DECT solution Rove. In this blog post, I will write about the configuration and how to setup the Poly Rove to work together with the Microsoft Teams SIP gateway.
In this first blog post of two, I will cover how to manage ownerless Microsoft Teams and Microsoft 365 groups using board tools from Microsoft. Ownerless Microsoft 365 groups or teams are quite common and often seen in the wild.
A few weeks ago, Martina Grom tweeted about a new feature in the Microsoft Admin Center to find these ownerless Microsoft 365 groups or Microsoft Teams. It allows active members to be notified by mail when the team, or rather the Microsoft 365 group, no longer has an owner. This tweet brought this feature to my attention.
I will show you this option and an alternative way to notify someone about ownerless teams, like the IT staff for example, by a scripted solution in a second post.
In this blog post I will give a short overview how to downgrade the Microsoft Teams module in your Azure Automation account. Why you should do this? Assume you have developed a solution for some Microsoft Teams automations. You are using the Teams PowerShell module in some of your scripts. After a few months running the solution very smoothly, you decide to upgrade the PowerShell module in your Automation Account. And from that time on, your scripts don’t work anymore. Microsoft updates version 2.3.1 to the current release and some command-lets or parameter changed. Of course, we can update our solution but it is better to get a working solution in a short period of time and to find a solution in a lab environment.
This week I had a Aha event and some fun with side effect by the Microsoft Teams App permission policy. The customer disabled third party apps and allowed only a few Microsoft apps. For testing purposes, the customer created a user-based app policy, allowed some third-party apps in this policy and assigned it to some specific user accounts. With one of these users, we started to create a new private Microsoft Teams, which should be enabled as org-wide teams afterwards. During testing we saw some nice side effects of the arrangement of the Microsoft Teams app permission policies and it took some time to find the root cause for it. So, I like to report it to you in this blog post.
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.