Loop components are now supported in OWA. The implementation is reasonably close to that of Teams chat, but has some essential differences due to the nature of email. The current state of Loop components mean that they are highly suited for internal communication but not for collaboration outside an organization.
Microsoft Loop components are available now in Teams chats and will soon become available in OWA. Loop components are a new way of collaborative working that some will find very attractive. However, under the covers, some compliance issues can block organizations from allowing the use of Loop components. This post explains the issues involved in eDiscovery and export of items containing Loop components.
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…
Whiteboard is the latest Teams-enabled app to use OneDrive for Business for its storage. It’s unsurprising and it’s a trend likely to continue, and it creates an administrative challenge in terms of how to handle deleted Microsoft 365 user accounts. The suggested approach of having a designated user review the information and retrieve what’s important is OK for documents but doesn’t work for app-linked content. Retention policies are a better option.
Announced at Fall Ignite 2021, the first implementation of Microsoft Loop components is in Teams chat. This functionality is available in preview and it’s very usable, providing everyone in the chat uses the right client and is enabled for preview. In this article, we review the functionality available through loop components and how the fluid files for the components are stored and shared.