Skip to main content

Deals You Can't Miss

1 Year Subscription

Fix for issue in deleting messages by Owner in Microsoft Teams

The Issue

We recently adopted Microsoft Teams as platform for Team Collaboration. As part of adoption there are various experiments that we do like trying out different third-party apps for productivity. In so doing these apps posts messages that might be noise for others and I wanted to delete these messages post uninstalling these apps. But alas, I couldn't delete the messages even though I'm wear the owner role (the other possible role being member) of the channel.

The Cause

Microsoft Teams by default disables this functionality, perhaps to preserve data integrity. 

As Administrator of Microsoft Teams however, you can change this default setting

The Solution

Step 1: Go to Microsoft Teams Admin Center and login as Admin for Teams.

Step 2: Go to Messaging Policies, and click Add button to create a new policy (you may call it Power-Owner, if you will) where you can turn on the option - "Owners can delete sent messages". See below snapshot for reference:

Step 3: After you save it, your policies table should look something like below:

Step 4: Click Manage users button that you can see in the table navigation to assign this Power-Owner (as I call it) to the select group of users.

Step 5: Take a break to go have a cup of Coffee/Tea, for the changes took more than a while to take effect. 

Step 6: And when you are back from your break, log-out from Microsoft Teams and log back in again. You should see the delete button against others messages as shown in the screenshot below:

Step 7: Celebrate for becoming a Power Owner who can delete others messages. Don't you forget, "With more powers, come more responsibilities!!.."

My Popular Posts

Ten Commandments of Egoless Programming

We are nothing but the values we carry. All through my life thus far, I tried to influence people around me with the virtues I value. Thanks to some good reading habits I had inculcated, and the fortune of being in good community of peers and mentors alike, I managed to have read some real good books. This post is about the 10 commands of egoless programming in Weinberg's book. I shall explain the commandments based on my experience here. So very many decades ago, Gerald M. Weinberg authored  The Psychology of Computer Programming . In it, he listed The Ten Commandments of  Egoless Programming , which remains relevant even today for us as not just programmers but as team-members. Weinberg is regarded as a pioneer in taking a people-centric approach to computing, and his work endures as a good guide to intelligence, skill, teamwork, and problem-solving power of a developer. When they appear to inspire and instruct, we find that they can apply to just about every business area, and e

Should I buy refurbished laptop from Amazon?

This post is based on my experience with and guess it to be true on all other platforms as well. At least you can check out and verify for these pointers before you make that decision to buy renewed/refurbished laptop on Amazon with your hard earned money. I see this question propping up in several forums and on many different occasions. In the recent past, I had my 5 year old dell laptop that gave up because its motherboard failed. One of the options that I had in my mind was to re-use the HDD and the 16GB DDR4 RAM of that old laptop in the one that I purchase next as secondary.  I had come to a conclusion that it is not worth buying a refurbished/renewed laptop at all. Why? For the following reasons, most of which I see as BIG #RedFlags: You got to remember that Amazon provides a platform for 3rd party sellers to sell their products as well. So in your search for refurbished laptops you wouldn’t want to choose some random 3rd party seller who Amazon doesn’t endorse. You cou

Multi-tenant Architectures

  Multi-tenancy Application Deployment Architecture could be modeled in 4 broad ways: Separate Apps & Separate Databases Shared Apps & Shared Databases Separate Apps & Shared Databases Shared Apps & Separate Databases There is no right or wrong here. It's about choice and consequence that you should consider taking into your business context and constraints. In this post I intend to jot down a some key points to keep in mind for each of these multi-tenant architecture. These are more of quick notes for my quick reference, a cheat-sheet of sorts when I have to make choices. And I guess this can come handy to you too in your wise decision making. Separate Apps & Separate Databases Easiest to implement from development and deployment stand-point. Just automate the deployment infrastructure for every tenant for quick set-up. Most expensive of all the models from infrastructure cost stand-point. Relatively longer deployment t