Collaboration has been and will continue to be one of the important business advantages that the Cloud can deliver to an organisation. Collaboration can be thought of as not just connecting people to one another and improving their day to day working practices, but also enabling and encouraging collaboration between people and data.
Black Marble can support your move to the cloud for collaboration services between people and data. We can help your organisation realise the full potential of people to people collaboration using services such as SharePoint and, in particular for this white paper, Microsoft Teams. Our approach will help you identify how Microsoft’s collaboration solutions can improve your ways of working, whilst helping you visualise your end goal.
I recently noticed that some of the Microsoft Teams that we had in use exhibited different behaviour to others that had been created more recently. ‘Recently’ (for varying definitions of ‘recent’) created Teams allowed users to edit and delete their messages, whereas a few older Teams did not. The older Teams were all created very early during our rollout of Teams, when Microsoft Teams itself was relatively new.
Checking the Teams messaging policies showed that the correct settings were in place to allow users to edit and delete their messages:
It appeared that these settings were not however being applied for the legacy Teams. Checking in the individual Team settings showed that these were overriding the global settings applied:
Note also that in the above screen shot, the ‘Owners can delete all messages’ setting was also unchecked, although this turned out to be the only Team for which this was the case.
I could go through each Team individually and manually check the Team settings, however PowerShell allows us to perform the same actions quickly. The following PowerShell checks for the user Team settings being mis-configured and corrects the settings: