A recent session at the Microsoft 365 conference offered some insight about the growth of SharePoint Online in both storage and sites. Adding 100 petabytes of storage monthly is a lot of data, but about a third of it could be consumed by Teams meeting recordings. And the 8 million sites created each month is large, but maybe not so big when you consider the reasons why Microsoft 365 tenants create sites. Teams, including private and shared channels, drives a lot of the growth in sites.
A new control in the SharePoint Online configuration is available to enable or disable Microsoft Loop components in Microsoft 365 apps, just in time for their introduction in OWA and Outlook for Windows. However, before we get all excited, there are some important issues with loop components when exported in eDiscovery search results that might make tenant administrators ponder. Just a tad…
A new sensitivity label setting is available (in preview) to control site sharing permissions for SharePoint Online sites. The new setting is an advanced setting, meaning that it can only be set using the PowerShell Set-Label cmdlet. It’s a welcome addition to the control sensitivity labels can exert over containers.
Sometimes useful features show up in a Microsoft 365 app long after they should have been there. This is the case of SharePoint Online’s document library dropdown menu, which is very helpful in navigating sites with multiple libraries. Unfortunately, not too many sites have multiple libraries because most are Teams-enabled and have a single library. Teams is another app where features show up after they should. The listing of the teams a user belongs to in the Teams admin center is a good example.
Microsoft is rolling out a new feature to allow users to move OneDrive shortcuts to shared or private folders. Although a nice upgrade, being able to move shortcuts is not the biggest OneDrive issue. What stops me using shortcuts is the clash between them and the OneDrive sync client. It seems like it should be an easy fix for Microsoft to apply, and when they do, I’ll happily move OneDrive shortcuts around.
A post by the Exchange development group tried to explain why mailboxes have SharePoint Online proxy addresses. It’s all down to the Microsoft 365 substrate, which needs the proxy addresses to ingest digital twins from SharePoint Online into Exchange Online for use by shared services like Microsoft Search. The upshot is that you can’t remove a mailbox permanently without some background processes kicking in to make sure that SharePoint is taken care of.
Microsoft has released a new set of over 1,800 fluent Teams emojis for use in chats and channel conversations. Soon you’ll be able to use Teams emojis as reactions in chats. Teams emojis are different from Windows emojis, but you can use the Windows emojis in channel names to highlight and emphasize the reason why the channel exists. All in all, the new emojis are a good thing and will be popular with many users.
An update to Microsoft Search means that search results available in SharePoint Online and Office.com now include Outlook and Teams messages. Microsoft has also updated Microsoft Search in Bing to include Outlook messages. All in all, these changes make Microsoft Search the go-to location when you need to find mailbox and Teams messages.
Microsoft Lists is now available in a preview for users with Microsoft Service Accounts (MSA). The preview is tagged as a lightweight version of the enterprise capabilities available in SharePoint Online. When generally available, we might see this as a premium consumer offering. In other news, an opinion says that Lists should replace Planner. I disagree, and say why.
SharePoint Online and OneDrive for Business will soon gain the ability to apply default sensitivity labels to document libraries. The feature is currently in preview and requires some complicated PowerShell to configure, but Microsoft is working on the GUI and expects to make the capability generally available later this year.
A new tweak to the sharing link dialog used by OneDrive for Business, SharePoint Online, and other Microsoft 365 workloads block downloads of video and audio files by default. This is probably what you want to happen as, unlike Office documents, when you share a video or audio file, it’s likely to be final content ready to be consumed rather than being worked on.
When SharePoint users share information, Office 365 captures events in its audit log. By analyzing the events, we can build a picture of how people share information. The sad thing is that the audit events logged when someone extends the validity of a sharing link doesn’t contain as much information as you might like. Even so, we can still analyze the sharing events to build a picture of what happens in an Office 365 tenant.
The SharePoint Online expiring access policy controls how long external users can use a sharing link. You don’t have to use this policy, but it’s a good idea to configure it. And once the policy is active, users will see notices when their sharing links approach expiration. The process to renew (extend) sharing links is quick and easy. And if you want even more protection, consider combining this policy with sensitivity labels.
Teams meeting recordings can contain a lot of confidential information. It’s a quick and easy task to create a Data Loss Prevention (DLP) policy to stop people sharing these files externally, In this post, we show just how simple the required policy is, and just how effective it is at stopping external sharing.
The SharePoint Online admin center displays an insight card for the number of unlabeled sites in the tenant. For some reason, many of the labels assigned to Microsoft 365 Groups and Teams had not reached SharePoint. Some PowerShell does the job to fetch the sensitivity label information from Exchange Online and update sites with the missing label information.
To help you recover from the blizzard of Microsoft 365 information released at Fall Ignite 2021, here are some notes about features and functionality you might have missed. Like any list created by a conference (virtual) attendee, it reflects my interests and what I was looking for. Feel free to disagree on the importance of any or all of the topics discussed here… and suggest some of your own in the comments.
The site property bag is SharePoint Online’s way to allow tenants to add custom properties. This is useful if you want to add custom properties for search purposes, which is what you might need to do to use the new adaptive scopes for Microsoft 365 retention policies to find and process SharePoint sites. In this article, we explain how to add values to the site property bag, and how to make sure that you don’t leave sites in a position where custom scripting remains enabled.
Users attempting to delete SharePoint Online files assigned Microsoft 365 retention labels are blocked. That is, until a change arrives in November to make SharePoint Online and OneDrive for Business behave in the same manner. It’s a good change because it avoid the scenario where users remove retention labels to delete files, which undermines the organization’s compliance strategy. Now, deleted items go into the preservation hold library and stay there until their retention period expires. My only complaint is that the control over the mechanism is not as simple as it should be, but that’s a small and relatively unimportant flaw in the overall scheme of things.
The preservation hold library is an important component of SharePoint Online retention processing. A change coming in November should simplify file handling and reduce the amount of storage taken up by retained files in the library. Basically, instead of storing multiple versions of a file, SharePoint Online will hold a single file containing all the updates. It seems like a good change to make. We’ll know more when it rolls out.
Microsoft has simplified Microsoft 365 administration by moving controls from the OneDrive for Business admin center into the SharePoint Online admin center. It’s a good step because the two workloads are really two sides of the same file and document management function within Microsoft 365. With many apps moving storage of their data to OneDrive for Business, its role is becoming increasingly important. Even so, OneDrive doesn’t deserve a dedicated management portal.
Adding the ability to search for spoken text in Teams meeting recordings is just one of the new features added after Microsoft moved storage for meeting recordings to OneDrive for Business. A new video viewer and support for 27 additional languages (some different variants of a base language) are also important developments. In this article, we explore how Exchange Online captures the text spoken in Teams meetings, how OneDrive for Business links the text with the video, and how Search can find spoken text from the transcripts.
The longstanding problem where the renaming of a Teams channel did not rename the folder in the SharePoint document library is being fixed. First flagged as an issue in 2016, this is one of the oldest bugs in Teams and it’s taken far too long for Microsoft to squash. The good news is that the fix will deploy in mid-September to close off the problem once and for all.
Microsoft plans to start removing the automatically-generated transcript of some Stream videos in September 2021. Only automatic transcripts are affected, and only if no one is looking at the video. If you’ve taken the time to edit a transcript or upload a manual transcript, Stream will leave these transcripts alone. It’s all part of the big plan to get Stream off its own Azure storage and onto SharePoint Online and OneDrive for Business.
In October 2021, Microsoft will enable the Azure AD email one-time passcode identity provider in tenants. SharePoint Online and OneDrive for Business will use the provider to control access for external people to its resources. The net effect is that Azure AD will create guest accounts for external sharing recipients. Even though guest accounts need to be managed, there’s lots of good reasons to use guest accounts, as we describe here.
The OneDrive for Business sharing control (also used by SharePoint Online) now shows thumbnails of the set of people who already have access to an item. The idea is to give owners of information an at a glance view of who has access. It’s a nice change which adds something that probably no one thought was missing, The little things add all the difference!
In September Microsoft will introduce a new auto-expiration feature for Teams meeting recordings stored in OneDrive for Business and SharePoint Online. By default, recordings will be moved to the recycle bin 60 days after creation (30 days for users with Office 365 A1 licenses). Tenants can control the default expiration period using Teams meeting policies while users can override expiration for individual files. And if you use retention policies to control Teams meeting recordings, their instructions take precedence over auto-expiration.
The latest version of the SharePoint Online PowerShell module reveals some new site properties to inform administrators if sites are connected to teams or even team channels (both private and shared). There’s also some changes coming to the SharePoint Online admin center, all of which are very useful in terms of tracking the sites used by Teams.
A change being made to SharePoint Online in August will make the deletion process for files with retention labels consistent with OneDrive for Business. The intention is to achieve consistency across the two browser interfaces and to remove a little friction for users who might become confused when they SharePoint Online stops them deleting labeled files. Everything will happen in August. We wonder if anyone will notice?
Auto-label policies are a good way to assign retention labels to important files stored in SharePoint Online and OneDrive for Business. The big problem is tracking the progress of auto-labeling. In this article, we explore how to use events logged in the Office 365 audit log to figure out what files are labeled and how long it takes the auto-label policies to process the files. The example explored here is an auto-label policy for Teams meeting recordings.
Microsoft is changing the SharePoint document library UI for sites used by Teams private channels to make sensitivity labels read-only and move a link into the command bar. That doesn’t sound so important, but it’s part of the preparation for the introduction of Teams Connect, aka Shared channels. It’s just a pity that the text of message center notification MC261534 was so confusing when it first appeared.
Two Microsoft 365 message center notifications covering Progressive Web Apps (PWAs) for OneDrive and Lists are interesting, but the news of the arrival of the new Nucleus synchronization engine within the OneDrive sync client (for Windows) is even more interesting. Together, the combination of PWAs and Nucleus make OneDrive and SharePoint data more accessible to users.
A preview for Sensitivity Labels show how they can use Azure AD authentication contexts and conditional access policies to protect SharePoint Online sites. Although you can link conditional access policies to sites with PowerShell, it’s a lot easier to make the connection through sensitivity labels. Any SharePoint Online site which receives a label configured with an authentication context automatically invokes the associated conditional access policy to protect its contents.
New PowerShell commands for sensitivity labels can configure default sharing link settings for SharePoint Online sites. Any site assigned a label configured for default sharing links inherits those settings within 24 hours. Also available is the ability to apply default sharing link settings at a per-document basis.
Microsoft will soon impose a limit on the number of PST versions kept by SharePoint Online and OneDrive for Business. PST files have no business being in cloud storage, so this is a reasonable step. People shouldn’t keep PSTs in SharePoint or OneDrive document libraries and organizations shouldn’t let them. In fact, you should block PSTs from OneDrive synchronization and make plans to eradicate these pesky files.
SharePoint site owners can teamify (team-enable) their site, which is nice, Now you can create channel tabs based on site resources during the team enablement process. It’s a nice new feature but you must remember that a new team only has a General channel, so site resources will end up in a place where they might necessarily not end up in the long run.
The latest update for sensitivity labels allows them to control the external sharing capability of SharePoint Online sites. It’s a powerful example of policy-based management in action and demonstrates just how useful sensitivity labels will be as Microsoft steadily builds out the set of controls available through labels.
Sensitivity labels are a great way to protect confidential documents stored in SharePoint Online. Sometimes the documents must be decrypted. This article explains how to build a PowerShell script which uses Graph API calls to navigate to a folder in a SharePoint Online document library and decrypt the protected documents found in the folder.
SharePoint Online and OneDrive for Business have a new sharing link control which highlights the permissions assigned to sharing recipients. It’s a minor tweak which is actually a pretty good idea as the last iteration of the sharing control buried permissions behind the scenes. And as we all know, permissions are important to IT resources.
A new preview feature allows the resources available to an Azure AD guest account to be reassigned to another email address. It’s a nice feature, but Teams has some problems with it at present. On the upside, everything works great with SharePoint Online and Planner, and we’re sure that Microsoft will fix the problem with Teams soon.
The OneDrive sync client is an important Microsoft 365 component which underpins features like autosave and coauthoring of Office documents. During the March 15 Azure AD outage, the client had a meltdown and removed all the local copies of files stored in a SharePoint Online folder, seemingly because it couldn’t authenticate. The problem was easily fixed, but it’s a bad example of handling what could be a transient authentication issue.