The Groups section of the Azure Active Directory portal now includes a preview of a feature to configure the Office 365 Groups naming policy without going near PowerShell. Although those proficient with scripts and GUIDs will lament this sad reduction in standards, the normal administrator will welcome the chance to forget some obscure syntax.
Two Office 365 Message Center notifications bring news about an increase in the number of participants for a Teams group chat to 100 and improvements in shareable links for files. Moving the limit from 50 to 100 for a group chat makes these conversations more flexible. Adding permissions to the sharing links used by Teams gives users more control over how they share information with others.
One of the great things about Teams is the way that it orchestrates Office 365 resources like SharePoint Online sites. The downside is that a tenant’s valuable SharePoint storage quota might be absorbed by a profusion of Teams. To offset the problem, you can apply lower limits to sites belonging to Teams and the best approach is to use PowerShell for the job.
Microsoft commissioned Forester Consulting to write a total economic impact study of Teams. As you’d expect, the report says that Teams is a good deal. But like any consulting report, you need to question the findings and assumptions to figure out where the truth lies. In some cases, I simply disagree with the underlying logic for a conclusion. In others, I think the authors are mistaken. It’s up to you to make your own assessment.
Outlook Mobile clients can now schedule Teams meetings, even if your tenant isn’t using the newer version of Outlook’s mobile connection architecture. The Office 365 tenant setting for Skype for Business Online co-existence mode has to be configured to use Teams, and once everything is in place Outlook is happy to schedule Teams meetings.