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.
A very often requested feature in Microsoft Teams Phone System projects is auto dial. A user marks a phone number and is looking for a shortcut to initiate a phone call with Microsoft Teams to this marked number. Does it work, Thorsten, auto dial for Microsoft Teams?
To be honest: not directly out of the box. But based on an article from Frank Carius, I found a solution for this request.
In my latest project, I had the challenge to migrate an entire organization with 4.000 users from Skype for Business OnPrem to Micrsoft Teams in just two weeks. The customer planned to replace their current GoTo Meeting solution with Microsoft Teams. Of course, challenge accepted. During the migration I had to move the users from OnPrem to Skype for Business Online aka Teams. The migration to the cloud failed for some users with the message “An unknown error occurred while trying to roll back the user.” It took some time to resolve this error and this blog post is about it.
In the fourth and last episode of my series about Microsoft Teams notifications I have two topics: a short look into the future about an upcoming change in the Microsoft Teams client. And second, I will try to resolve some questions to some magic mails which arrives from time to time in your mailbox about missed activities in Teams.
In my third part of this series I write about the feature to tag a Microsoft Teams user for status or presence updates. If you do so, you will be notified when the presence for a tagged person change for example to available.
This is part II in my series about Microsoft Teams Notifications. Last week I started the series with an overview of the basic notification settings. Today, I will continue with the channel notifications in special. In this new blog post I will cover how to change the notifications of a dedicated channel.