The Office 365 Groups Naming Policy is now generally available. The policy has taken nearly two years of preview to not get very far, but at least it’s now an official part of the service. Microsoft considers the naming policy to be an Azure Active Directory Premium feature. Many customers might think differently, especially because the naming policy must be implemented through PowerShell and can easily be mimicked through PowerShell. And of course, Exchange Online’s distribution list naming policy is free.
Microsoft announced that the era of favorites and following is over for Teams. The new way is to show or hide teams and configure notifications for channels. Apparently, people found the old terminology confusing. Hopefully the new world of Show/Hide and Channel notifications will be more reassuring.
In a sign of how automation based on signals gathered by Office 365 will emerge to help administrators do a better job, the preview of the new Admin Center offered to create a DLP policy to protect some sensitive information that I had clearly overlooked. Well-intended as the portal was, its efforts to create the new policy failed. That’s not really important – it’s the glimpse into the future which is.
New data about the number of Slack and Workplace usage gives the chance to compare how Microsoft is doing with Teams. And the answer is that things seem to be going well, largely because Teams is growing off the huge Office 365 base. With 155 million users (the last figure) and 3 million more added monthly, Teams has a lot more to go after in the Office 365 installed base.
If you work with Office 365 through PowerShell, you probably have your own script to connect to the various services. If you don’t want to write your own script, you can download one from GitHub or the TechNet Gallery. This article covers two that you might like to try, including one with a GUI to choose which Office 365 services it should connect to.