Following new support of Loop components for Teams channel conversations, it’s sad to discover that Loop component eDiscovery remains challenging two years after the first appearance of component technology in a Microsoft 365 application. eDiscovery can certainly find Loop components, but creating a seamless picture about their usage is harder than it should be.
A May 10 post reveals how Loop task list components can synchronize with Planner (using a roster container) to make the Loop tasks available to other apps like To Do. It’s the first implementation of Planner roster (or lightweight) containers, meaning that the containers holding tasks are not associated with a Microsoft 365 group. Everything seems to work very smoothly and the technology is available now.
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…
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.