Teams Real Simple in Pictures: Disabling List Item Comments in the Web App and in Teams

It's been a bit of a mad week. Over the last five days I've spoken at Modern Workplace Conference Paris, the Microsoft Reactor in London and Microsoft 365 California. Awesome events with great organisers and every one a fantastic experience. Honestly, it's such a privilege given our situation, and if you came to see one of my sessions then thank you for your support and the time you've set aside. Now the subject of today is a question I got at the end of the Reactor session which I thought I would follow up on. The session was about Teams and Lists and the question was specifically, can you disable comments in Microsoft Lists? As I said in the session the answer is yes - at least in the web app. So this one is for you. And for anyone else reading why would we disable comments? Well, we may not want to have comments and conversations around List Items. We may find them too busy or too distracting. They may not, in our case, add value. So to start out there is two things you need to know about comments on Lists at the current time. Number one - comments on List Items in the web app are different from conversations on List Items in Teams. As shown below in the screen shots of the same item in the different experiences the comments are different and do not synchronise. Being that you can have two different sets of comments in the same item - that in itself is a reason to want to turn it off to avoid confusion. In addition the data isn't housed in the same place, the conversations in Teams are not housed in SharePoint where the List is. Number two. Disabling comments on List Items in the web app experience can only be done via Powershell and can only be done tenant wide - for all Lists. It's not as granular as being able to do it for specific Lists in specific Sites/Teams, however Microsoft do have future plans to introduce this. So you have to tread carefully here and understand this isn't the complete experience which we want - ideally it would be consistent across Teams and this raises the question? Does disabling it via the Shell for the core web app experience also disable it in Teams? Let's find out