Microsoft has released the Communities app for Teams. The app integrates Yammer into Teams as a pinned app or in a channel tab. The pinned app mode is most functional, even if the channel mode includes a Share to Channel option. Overall, it’s a nice integration, which begs the question as to when the same might be done for OWA?
If you receive a notification about Yammer conversations in OWA, you might notice that you can now do all sorts of new things to interact with Yammer while remaining in OWA. It’s part of Microsoft’s effort to make Yammer more relevant and accessible to people who prefer to communicate through email. And the nice thing is that the approach works well.
Microsoft says that the migration of Yammer storage for new files in SharePoint will restart in June and finish worldwide by the end of July. That’s great, but the migration of existing files is a manual process that can only be described as tiresome and error-prone. But it adds to the allure of Yammer and increases its prestige in the ranks of Office 365 apps. Or maybe not.
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.
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.
Office 365 changes all the time, which is good because it keeps the Office 365 for IT Pros writing team busy and happy. Discussions this week included Microsoft’s response to a Dutch DPIA, the effect large Teams have on Yammer, how Exchange Online validated a fix to a security problem, and graphics to help understand the components of the Microsoft 365 E3 and E5 plans.
After being accused of bias against Yammer, I thought about whether this is true. But it’s not bias – it is frustration that Yammer remains so detached from the rest of Office 365 six and a half years after Microsoft bought the technology.
Encrypted email is becoming more common within Office 365. Things usually flow smoothly when sending protected messages to email recipients, but other Office 365 recipient types like Teams and Yammer might not be able to handle protected email.
The “Yammer Vision” session at last week’s Ignite conference was interesting. At least, I thought it was because it showed signs of a new willingness and direction to make Yammer a better citizen of the Office 365 ecosystem. Time will tell whether the grand plans succeed.