Manage live components in Teams

Live components in Teams chat offer a new way to ideate, create, and make decisions together. Send a component—like a table, task list, or paragraph—where everyone in your chat can edit inline and see changes as they’re made. This means you can gather ideas and feedback from your team while holding fewer meetings and minimizing the need for long chat threads.

Get tasks done faster together. Crowd-source an agenda, track a group's action items, or take notes collectively. These are just a few scenarios made easier with live components.

Share components. In this release, you can share live components into different Teams chats. Recipients can edit from wherever they are and see updates instantly no matter where the changes were made. In future releases, live components will be supported in Teams meeting notes and channels, Outlook, and eventually across all Microsoft 365 applications.

Start in chat, build from there. Every component you create from Teams chat is automatically saved to a file in OneDrive. So, you might begin collaborating in chat then later move to the file, where you have a larger visual space for editing and can add as many components as you like.

Clients and platforms

Available on Teams apps on Windows, Mac, Linux, iOS, and Android.

Starting in Early September, live components will be available globally. In late September, it will be available for Government Community Cloud Mod (GCC).

Settings management

Live components are built with Microsoft Fluid Framework supported across Microsoft 365 suite and controlled from SharePoint Online and not from the Teams admin center.

You'll need the latest version of SharePoint Online PowerShell module to enable or disable all Fluid Experiences across your Office 365 tenant. Microsoft Fluid Framework defaults to ON for all targeted release tenants. Because live components are designed for collaboration, the components are always shared as editable by others, even if your tenant is set to default to view-only for other file types. See the Learn more link next to the setting for more details.

Checking if the Fluid Framework is enabled through the SharePoint Online PowerShell Cmdlet

  1. Connect to SharePoint Online PowerShell

  2. Check if Fluid Framework is enabled by running the Get-SPOTenant cmdlet without any arguments.

  3. Verify the value of IsFluidEnabled is true.

Enabling the Fluid Framework through the SharePoint Online PowerShell Cmdlet 

  1. Connect to SharePoint Online PowerShell

  2. Enable Fluid using the cmdlet Set-SPOTenant -IsFluidEnabled $true 

    The change will take a short time to apply across your tenancy. 

The feature will be available on Teams Windows Desktop, Mac, iOS, Android. When enabled, users will see a new option for inserting live components in the message compose experience for these clients.

Disabling Fluid Framework through SharePoint Online PowerShell Cmdlet

  1. Connect to SharePoint Online PowerShell.

  2. Disable Fluid using the Set-SPOTenant cmdlet Set-SPOTenant -IsFluidEnabled $false. 

    The change will take a short time to apply across your tenancy. 

If you need to re-enable this capability, you can use SharePoint Online PowerShell Cmdlets.

C:\\WINDOWS\\system32> Connect-SPOService
cmdlet Connect-SPOService at command pipeline position 1

Supply values for the following parameters:
Url: <>
PS C:\\WINDOWS\\system32&gt; set-SPOTenant -isFluidEnabled $false
PS C:\\WINDOWS\\system32&gt;

Known limitations

  • Creating a table or a task list as the first component after the Teams app is restarted may take some extra time.

  • Other chat members will receive an email notification when mentioned with an at (@) symbol. (At-mentions notifications in the Teams activity feed will be available soon.)

  • Searching for live components within Teams search will return a link to the component in, not the chat message itself.

  • Live components are disabled in federated chats and enabled for regular chats with a Guest account using Azure B2B.

  • While you can share a component in Teams channels and other Microsoft 365 apps, recipients get a link in most places at this time. Inline editing is planned for more experiences in the future.

Storage of .fluid files

How .fluid are stored?

Live components created in Teams are backed by a .fluid file stored in the creator’s OneDrive for Business. Being a file in OneDrive for Business means that users can create, discover, and manage live components (.fluid files) as easily as any Office document.

Users can search for content in .fluid files from and OneDrive for Business. .fluid files work with data governance features like eDiscovery, auditing, reporting, and legal hold.

.fluid files will now appear on and OneDrive for Business, such as in the Recent and Recommended areas. .fluid files can be restored to previous versions from OneDrive for Business.

Chat participants must have a OneDrive account to create live components. Without a valid OneDrive account, chat participants might still be able to collaborate on a component created by other users who have a valid OneDrive account, but cannot create their own.

Moving a .fluid file from OneDrive to a SharePoint site will result in the live component failing to load in Teams chat.

What happens if the owner of the file leaves the company?

OneDrive retention policies apply to .fluid files just as they do to other content created by the user.

How are .fluid files shared?

Live components can be inserted in Teams chat or copied from one chat to another. (Live components aren't yet supported in channels.) They default to the tenant’s existing permissions, but users can change permissions before sending to ensure everyone has access.

Opening components from Teams chat in offers share functionality at the top of the window, similar to the sharing options offered for other Office documents.

What if a .fluid file becomes corrupted or damaged?

Version History allows you to review and copy from previous versions of the file.

What apps can open and edit .fluid files?

.fluid files can only be opened as links in your browser, such as, and as live components in Teams chat. If downloaded, they can't be opened again without first uploading them back to OneDrive for Business or SharePoint Online.