With Teams, we have a number of things we can do to keep our Team up to date. This includes group chats, conversations in channels, meetings, notifications, mentions, and adding content to the Wiki. Another way is by leveraging what are called connectors to deliver content from apps such as Twitter and Yammer into the conversation tab of the Team channel. Twitter, for example, is used by millions for posting and interacting with messages. Yammer is an enterprise social networking service for broadcasting one to many communications within the business. Both are places users and organisations post news and status updates first. Now, the benefit of setting up connectors to Twitter and Yammer is that members of the Team no longer have to scour them and jump around between all these different Twitter pages and Yammer groups to get the updates they need - we can simply bring them all into a feed! A great time saver.
Document collaboration and co-authoring (when we work at the same time) is one of the core functionalities of Teams. We have the ability to do this seamlessly whether it is our Word Documents, or Excel Spreadsheets, or PowerPoint presentations, knowing that they are stored in a single place and are accessible from anywhere on any device. However, there may be times where there is a single owner for the Teams documents or we simply need to create documents for viewing purposes only, limiting other members of our team from making changes. Controlling documents in channels and who can edit them is very straightforward, and many issues resulting from unauthorized changes can be easily prevented
Teams is the collaboration hub for our needs. We can chat, we can share files and we can create wiki's to share our knowledge to the Team. Another way we can collaborate is with video. As a Microsoft Certified Trainer, I can add sites such as Pluralsight and Udemy as Web Tabs within the Team, but I can also build video channels with my own content and make this easily available. Creating channels are also effective in scenarios such as introductory videos, meetings and if I saw a great video on a site like YouTube, but don't want the team members to go specifically to that site. It's all about bringing the rich content to them.
Controlling who can create Teams is based upon who can create Office 365 Groups. Whether this is right or wrong is a matter for debate and opinion - some believe this is necessary for reasons such as Teams sprawl; others believe it limits productivity, agility and pushes others back into the use of Shadow IT.
I am off to Vegas on Friday - second time lucky to go to #MSInspire! As you may have guessed most of the sessions I will be attending will be on Microsoft Teams. I am not going to lie here - I have very much planned this from the start and you can follow me throughout the conference as I post on Twitter and blog on this site.
Mail is in the genes of the organisation I work for. To this day it still has one of the largest Hosted Exchange platforms in the country and some of the very best Exchange engineers in the business. I find these Exchange engineers - meaning those dedicated to Exchange management on a day to day basis, some of the most deeply passionate people I have met in all of IT. They love what they do - absolutely mad for it. I encourage anyone to talk to them about DAG's or SMTP Configuration, or TNEF, or Delegate Permissions, or Mailbox Protocols, or SmartHost integration, or Replay Queues, or RAID, or Jetstress or least cost routing paths.
We all love Microsoft Teams. Day in and day out, you'll see us evangelising it on social. On forums such as the Tech Community we help others with enquiries and issues. We run user groups. We write blogs. We speak at events. We vote and create uservoices. We ask all the questions we can think of at that time on the community AMA's.