Microsoft Teams

Competition and Adoption Driving Microsoft to Linux Client for Teams

by Tony Redmond

Lots of hot air and fuss resulted when Microsoft confirmed on the Teams UserVoice site that they are actively working on a Teams client for Linux. Many Office 365 tenants will be bemused at the attention this topic received, but competition with Slack and the need to drive faster adoption in Teams deployments are compelling reasons for Microsoft to do this work. We can only hope that the project results in better Teams clients all round.

Exploiting the Graph When PowerShell Can’t Do Enough for Teams

with 2 Comments by Tony Redmond

Although Teams has a PowerShell module, its cmdlets can't get at some of the interesting information for team objects. But the Graph API reveals that information. Combining the Graph with PowerShell makes it possible to retrieve the information with just a little effort. A working example helps make the point, so here's a script to report the Teams channels with email addresses.

BitTitan Introduces Cross-Tenant Teams Migration

by Tony Redmond

Moving Teams between Office 365 tenants has been a challenge since the earliest days of Teams. Now a beta Graph API has allowed BitTitan to create the ability to transfer team settings and channel conversations between tenants. The migration isn't perfect, but it's a good start and will improve over time as BitTitan and other ISVs work out the best way to move Teams content around.

Petri Newsletter Sign-up
Tech Tuesday

Subscribe to Tech Tuesday, the latest insights from Petri.com for IT Pros.

    See All Petri Newsletters

    Controlling Communications Inside Office 365 Tenants with Information Barriers (Part 1)

    by Tony Redmond

    Office 365 Information Barriers allow organizations to erect logical firewalls between different user communities to ensure that regulatory and legal requirements are met. Teams and Exchange Online support Information Barrier policies, which replace Address Book Policies. Some work is necessary to get Information Barriers set up. We cover that work in this article and prepare the ground for deploying the policies to Teams.

    Slack Takes Aim at Teams Weaknesses

    with 3 Comments by Tony Redmond

    Slack's July 22 post reports some advances in their desktop client that seem to aim at reported weaknesses in the Teams desktop client. The best update is better protection against network outages. The other claims of 50% less RAM, 33% faster startup, and 10x better call joining need validation in the real world.

    Emailing Owners About Obsolete Office 365 Groups and Teams

    by Tony Redmond

    In February, I published a script to report the activity in Office 365 Groups and Teams. It is natural that some of those groups will be obsolete, so here's another script to email the owners of those groups. I know the script works because I tested it against 200 groups, but it's rough and ready and deserves some TLC from people who really know PowerShell.

    Email, Teams, and Expressing Reactions with Likes

    by Tony Redmond

    Microsoft introduced support for like reactions in OWA in 2015. Teams also supports likes, but it also supports other reactions to messages from sad to angry. Knowing how to use these reactions is a social minefield. On a serious notes, reactions are not currently stored in Teams compliance records in Exchange Online, which is a problem if people react to messages with likes.

    Teams Gets Urgent Message Capability for Personal Chats

    by Tony Redmond

    Microsoft is rolling out priority notifications for Teams, the ability for users to send urgent messages in chats so that the recipients get notified every two minutes until they respond. Office 365 tenants (except GCC) should see the new functionality in July. Tenants can control who gets to send urgent messages with messaging policies, and some user education would be good to help those allowed to send these messages understand when a message is truly urgent.