Microsoft has imposed further restrictions on some Office 365 services to release CPU cycles and other resources to allow end users to work. The major impact is felt by SharePoint Online, OneNote, and Stream, and consequently by Teams because it uses all of the above. We can expect restrictions to last until Microsoft manages to deploy additional resources in its Office 365 datacenters.
Office 365 Sensitivity Labels can now be applied to "containers" - Teams, Office 365 Groups, and SharePoint sites. Sensitivity labels replace the old text-only classifications that have been available since 2016. The labels don't affect the contents of the containers, but they can control some container settings, like whether a team allows guest access or if it's open to any tenant user to join. It's yet another development in the label and protection story for Office 365.
SharePoint Online is embracing Office 365 Sensitivity Labels to allow protected documents to be processed by indexing and available to content searches. The Office Online apps (Word, Excel, and PowerPoint) also support the application of sensitivity labels. The only disappointment is that the SharePoint Online and OneDrive for Business browser interfaces don't allow labels to be applied to documents.
Microsoft has made a preview of the Fluid Foundation available for Office 365 users to try out. The preview demonstrates how components can work together to share information quickly. It is very focused on SharePoint Online at present, but Microsoft plans to make intelligent fluid components available in Teams, OWA, SharePoint, OneDrive, and Office apps. The preview raises some questions, but that's the nature of the beast.
SharePoint Online document libraries keep 500 versions of files by default. The minimum recommended by Microsoft is 100. But why are so many versions kept? The reason is that it leads to better recoverability and underpins features like AutoSave and co-authoring. You might be tempted to reduce the number of versions, but why? I can't come up with a good answer.
A new SharePoint Online feature blocks access to newly uploaded files until Office 365 Data Loss Prevention processes the files to detect policy violations due to the presence of sensitive data. DLP processing for SharePoint Online can take several hours to reach new files, so enabling sensitive by default stops users inadvertently sharing sensitive content until DLP can process files. The downside is that you can't apply sensitive by default to individual sites. It's all or nothing...
The Brave Browser offers the prospect of speed and security. But how well does it work with the Office 365 browser apps? As it happens, pretty well, with some exceptions. Here's what I discovered when I test-drove Brave with OWA, Teams, SharePoint Online, Yammer, Planner, and Stream.
Designers working with Microsoft Forms can now include a file upload question type in their questionnaires, surveys, and other forms. It's a small but valuable change to Forms. Depending on the form type, the uploaded files are stored in OneDrive for Business or SharePoint Online.
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.
Cloudy attachments are an excellent way of sharing documents through email without attaching files. Behind the scenes, an anonymous link to the document is sent to recipients, who can then use the link to open, edit, or download the document (depending on the assigned permission). Office 365 tenant administrators don't have great visibility into what kind of anonymous sharing happens, but they can with a little bit of PowerShell and the contents of the Office 365 audit log.
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!
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?