If you have been following this long running series, it probably comes as little surprise that I love video. I love videos which are genuinely interesting and jam packed with useful content, well produced and palatable in terms of their length. Yet the one problem I have is that I do so much focus work these days that I always forget to check for updates and so I often end up missing out on some really great content. Of course, there was a period I used to check them. I used to spend too much time checking them every other day, regularly switching out of context which often took me out of the focus work I was doing
Last week, it was announced in the Message centre (MC204830) that the Twitter connector for Teams had been retired as of 21/02/2020. This was a feature that I loved, and one that I had previously blogged about. Connectors still work for Yammer - and for many other apps and RSS but Twitter? Per the announcement, it now needs to be integrated via Power Automate. The good news? It can be done, the benefits are exactly the same as connectors - members of the Team no longer have to scour Twitter accounts to get the updates they need, and we also have the benefit of getting hands on with Power Automate. The bad news? It probably isn't as simple as the Message centre makes out and some functionality is lost. Whether Power Automate will replace connectors as we move forward? I don't know - but it certainly makes sense in terms of having all of your automation and flows sitting neatly beside one another
Analyse, Act and Automate. Buzzwords these may be - but the importance of the Power Platform is real. About a year ago, I was sitting in a meeting in Dublin discussing Microsoft 365 with a partner whose business was built upon Power Apps. As much as I was impressed with the app on the IPad they'd recently developed after their receptionist left, it was the dawning on how they viewed Microsoft 365 through the prism of applications. It's very easy to narrate a story on Microsoft 365 around Security, Teamwork or the modernization of devices (three narratives Microsoft typically use today). But I had never considered doing that based upon apps. Never even entered my head.
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.
In my personal experience, it is not just IT Pro's who want to keep up to date with roadmaps and have an understanding of whats coming to the platforms they manage. Enthusiasts and evangelists are often eager to see new features that they may be able to leverage or rave about to their partners and customers. Support always wants to know what's coming down the pipe in order to prepare for what they see are inevitable issues. Finance loves anything which can lead to greater ROI and save money - and CEO's often like to know they got it right.