It's been a good week. I tend to measure things by whether I am playing offense or whether I am playing defense. This past week has been more offense. But it's good largely because after Teams Nation and NCE I am finally getting back to some sort of normality. That means I am beginning to have some bandwidth to do things such as the blog. In time, hopefully that'll mean other things such as the Tech Community too. So earlier this week I had a little flurry and explored a few different things such the ability to block folders and file sync in a team, disabling add shortcut to OneDrive, and utilising the keyword trigger in Power Automate to launch flows right out of a channel. To round off, I am going to take another look at Teams Policies, and configuring Messaging Extensions within App Setup Policies. Yes - the app policy doesn't just cover the app rail anymore. But my memory is, admittedly, a little hazy at this point. You've had the ability to install apps into Teams themselves via App Setup Policies for some time. Installing extensions? I can't honestly remember if this was always a part of it. Pinning extensions looks to have been added recently whilst I've been away. But it's no matter - I'll cover both. For the casual user of Teams what exactly are Messaging Extensions? Messaging Extensions allow users to interact with web services from the compose message area, the command box, or directly from a message. You should, for example, be familiar with the apps underneath the compose box in a channel or a private chat. Now, there is nothing revolutionary in this add. It's largely doing the same thing as has always been done with the app rail, except you now have the ability to do it for messaging extensions. The same pros and cons remain. Pros? Standardisation. Ease of Access. Not having to install if you choose to install. Cons. Too restrictive. Too rigid with changing work patterns and use of apps, the over-installation of apps into Teams which may never use them. But honestly it's all good fun. Maybe except if you have a few thousand Teams or few thousand users. But I don't
There may be an app your Team frequently uses. For the purpose of this article lets take this app to be Microsoft Flow where the Team is repeatedly adding Flows between apps such as Forms and SharePoint and Twitter and Powerapps across multiple Teams. They could always add Flow as a Tab to a particular Team, but with the increasing amount of Teams this wouldn't make much sense as the Team members would have to remember what Team, or - as is more likely - they are now adding Flow Tabs across multiple Teams which is littering Teams with Tabs which don't necessarily need to be there.