Microsoft Teams

Azure Active Directory External Collaboration Policy Now Generally Available

by Tony Redmond

Office 365 makes it easy to collaborate with external users through Office 365 Groups and Teams, both of which use Azure B2B Collaboration. In fact, collaboration is so easy that users might be carried away and share with all and sundry, including your competitors. Which is why it's nice to have a policy to control sharing with certain domains that works for applications like Groups, Teams, and Planner.

SharePoint Online, Groups, Regional Settings, and Pacific Time

with 1 Comment by Tony Redmond

Office 365 Groups are the reason why many SharePoint Online sites appear in tenants. If you're on the Pacific coast of the U.S., the regional settings are OK. But anyone else in the rest of the world who uses the SharePoint browser interface will see times and dates in that instead of the local format. You can change the regional settings for a site, and now you can make sure that new sites have the right settings.

Why the Office 365 Group Expiration Policy Needs Help

by Tony Redmond

It is nice to have an Azure Active Directory Expiration Policy for Office 365 Groups, but it's not so good that the policy functions exclusively based on age. Another problem is that administrators have no way of knowing when groups will expire. So we take out PowerShell, write a script, and hey presto, we have a report. We still need to solve the problem of creating a policy that functions based on activity rather than age, but that's another day's work.

Why PowerShell is a Core Skill for Office 365 Administrators

by Tony Redmond

PowerShell is a critical skill for Office 365 tenant administrators. A knowledge of PowerShell allows you to fix things that Microsoft leaves undone in apps like Exchange Online, SharePoint Online, and Teams. Sure, black holes exist for PowerShell (like Planner) and it is slow to process thousands of objects, but there's nothing like a little script for getting things done.

The Evolution of Microsoft’s Collaboration Story for Office 365

by Tony Redmond

Since Office 365 appeared in 2011, Microsoft's collaboration story has varied according to whatever technology is available. Originally based on Exchange and SharePoint, it's gone through Yammer, Office 365 Groups, and now Teams. You'd be forgiven for being confused by the frequent changes in the strategy du jour. And now we have inner and outer loops to consider, at least according to Microsoft's favorite collaboration slide. Here's my take.

Monitoring the Removal of Office 365 Groups (and Teams)

by Tony Redmond

Owners of Office 365 Groups can delete groups if they want. Some don't like this as it means that SharePoint site collections, teams, and plans are removed. The simple membership model used by Office 365 Groups is the cause, and while you cannot stop owners deleting their groups, you can take action to detect and recover deleted groups if necessary.

How a Free Version of Teams Might Work

by Tony Redmond

Microsoft might be working on a free version of Teams to take on Slack. As it turns out, not many technical changes are needed to transform the full enterprise version of Teams as available inside Office 365 into a limited version that Microsoft can make available for free, leveraging its existing consumer office services like Outlook and OneDrive.