Now that you are orientated, it's time to get to hands on and get into some teamwork! The first place to start is creating Teams and joining other Teams - how can we even begin to work in Teams if we aren't even part of them right? We'll then move on to creating channels - those defined sections of a team where we can chat and collaborate with other members. We'll cap this blog with 3 ways we can start a chat with the team. Chat is considered to be the core experience of Teams - and what most of us love doing!
Ok. Day one. You've just been told that you need to start using Teams. Your admin has installed it on your machine and has logged you in. You don't know where to begin. What is a Team? What is a channel? What is a tab? Let's get acquainted.
Imagine a scenario where someone in a Team wants to specifically start a conversation with just three or four people - a sub group - within the Team. Think of a project manager who wants to reach out to provisioning. A teacher who wants to reach out to learning assistants. A head coach who wants to reach out to assistants. A CEO who wants to reach out to sales. This individual targets specific people - but doesn't want to mention the whole team, the whole channel and doesn't want to go through the laborius process of mentioning each individual person. This is now possible with Tags. Tags let users communicate with a subset of team members without disturbing the whole in a targeted manner. Both owners and members (if enabled) can add one or multiple tags to a team member. The tags can then be used in @mentions by anyone on the team in a channel post or to start a conversation with only those people who are assigned that tag.
I can't believe that TeamsFest is nearly here - I really can't. It seems like only yesterday that Adam, Vesa and I started the call for speakers. This was back in december when we all felt like there was a certain luxury of time. Yet this year has been insanely busy - and I guess we should have known better given we did this back in October for Oktoberfest! Organising a conference has been one of the most rewarding things we've ever done. It's exhausting! - but there's nothing quite like it. That's why we wanted to do it again. We love Teams, we love the community, and we really wanted to bring some of the most passionate and best minds in the field together for a day of celebrating what it is that we love doing. If you love teams, love community and are thinking about joining us then here is 10 reasons why I think you should join us
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
A pipeline allows developers and DevOps teams to build and release reliable code into their test and production environments. If you know developers within the organisation or have developers on the team, you will probably know that they spend considerable amounts of time monitoring builds and releases. By integrating azure pipelines into Teams, the team will always know the latest status of the pipeline from within the same hub where they collaborate without switching context. They can set up and manage subscriptions for events directly from channels. They can approve or reject requests right from the browser, desktop app or while on the go using the mobile app.
In part 1, we explored adding Metadata to files in Teams through choice columns. This time around, we'll look at adding what is called managed metadata via the Term Store. In SharePoint, the Term Store can be thought of as a collection of term sets, each set containing metadata labels that can be used and applied to files in any SharePoint Site or Site Collection, so any Team or Channel. Therefore, they can be thought of as being managed centrally or 'managed metadata' unlike choice columns which are created on a site by site basis by members of the Team. This saves significant time for Team Owners and members who want to use the same metadata labels across Teams. Like choice columns, Managed Metadata is configured within SharePoint as opposed to Teams itself