Microsoft Teams

Microsoft is notoriously careful at giving out usage numbers for different Office 365 workloads.We know what the overall count is and now we have numbers for SharePoint Online and Teams. Some glances into a handy crystal ball and some inspired guesswork allows us to calculate likely numbers for Exchange Online, Yammer, and Planner and paint a more comprehensive picture of what’s happening inside Office 365.

OneDrive for Business is responsible for how sharing works within Office 365. Big strides are being made to achieving consistency across all the Office 365 apps and new some tricks are coming along too, like being able to link to a PowerPoint slide, requesting people to upload files to a folder, or using the URL in a browser as a link. All good stuff.

The Office 365 Substrate is a poorly understood part of Microsoft’s Cloud Office system. The substrate is a critical part of enabling services that run across different applications like Exchange Online, SharePoint Online, Teams, and so on. Functionality like search, information protection, data governance, and eDiscovery is a lot harder when you have multiple moving parts. The substrate gives cohesion and coherence to what could otherwise be a tangled mess.

If you work with Teams through PowerShell, you’ll know that you sometimes need to open the Skype for Business Online module. It’s a royal pain in the rear end to deal with two inconsistent modules. It would be much neater if everything was gathered into one coherent module. However, that’s not going to happen much before Skype for Business Online retires in 2021. In the interim, here are seven sets of policy cmdlets that you’ll probably need to use to assign policies to multiple users at one time.

Microsoft’s Teams application has added seven million daily active users in four months but the growth will not be slowing down anytime soon.

Everyone got very excited when Microsoft introduced private channels for Teams. Which is nice. The hard work of understanding the technology and managing its introduction now begins, so in this article we look at how to control the creation of private channels and what to do once private channels are out there in use. Some planning is always good, and mastering private channels will take preparation. Let’s begin!

Because this is the best reason to go to Florida, this special edition of Short Takes looks at the biggest announcements from Microsoft Ignite 2019.

Microsoft launched private channels for Teams at the Ignite conference. This article describes the architecture and structure of private channels and discusses their intended usage. In a follow-up, I’ll go into how to create and manage private channels in a Teams deployment and discuss some of the issues you should consider when using this new feature.

Microsoft made a ton of Office 365-related announcements at their Ignite conference in Orlando. Here’s a summary of the key news for SharePoint, Exchange, Stream, Teams, Yammer, and Outlook. More information will emerge during the week, so stay tuned for more coverage as news emerges.

SharePoint Online now boasts the ability to rename site URLs, which seems good, but not so good when you discover that the new URL breaks the connection with Teams. The fact that this happens is revealed in Microsoft documentation and it’s been a problem since the beta testing of the site rename function. Microsoft seems curiously disinterested in fixing the problem as quickly as they should have. A case of attention distracted elsewhere?