The End of Teams Following and Favorites

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.

Advertisements

New Office 365 Admin Center Offers to Create DLP Policy

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.

Teams User Count Outpaces Slack and Workplace

Teams and Slack competitive data

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.

Configuring PowerShell for Office 365

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.

Automating Office 365 with PowerShell and Flow

PowerShell is hugely useful when the time comes to automate Office 365 processes. Other tools exist that can help, including Flow. Maybe it’s the right time to consider Flow, especially when it is highly capable of knitting together different Office 365 components to get work done.

The Great SharePoint Online Recycle Bin Fallacy

If you’re interested in deploying backups for SharePoint Online, you might be doing so to prevent data loss through accidental user deletion. However, Office 365 retention labels and policies can help prevent accidental deletion too. And the best thing is that retention policies and labels are part of Office 365 E3, so you don’t have to pay more to get protection.

Office 365 Sensitivity Labels: Auto-Label and Updated Client

Microsoft released an update for the unified labeling version of the Azure Information Protection client needed for Office 365 sensitivity labels, which now boast auto-label support. Solid progress is being made to move sensitivity labels to the point where they are considered to be generally available, probably later this year. In the meantime, pay attention to the premium features like auto-label which require more expensive licenses.

New Information Protection Service Plans for Office 365

Azure Information Protection and Office 365

Microsoft announced that the Office 365 E3 and E5 plans will receive new Information Protection licenses. They’re preparing for the introduction of sensitivity labels and the increased use of encryption to protect access to content in Office 365 apps like SharePoint Online, Exchange Online, OneDrive for Business, and Teams. You don’t have to do anything to prepare for the new licenses, but it’s nice to know what they are and how the licenses are used.

Publishing News in Office 365 with the SharePoint Online News Digest

SharePoint Online supports the ability to create and publish a news digest from news items published on a site (or sites associated with a hub site). It’s a great way to spread information within an Office 365 tenant.

Analyzing the Teams Outage of 18 February 2019

Teams problem TM173756

Microsoft Teams suffered its first major worldwide outage on 18 February 2019. Users reported a failure to connect because Teams couldn’t authenticate them. The Post-Incident report for TM173756 revealed an issue with the Azure Key Vault. What’s more interesting is that the issue affected users in multiple Office 365 datacenter regions, which is not good.