Listview command set button Integration from Sharepoint into Teams Desktop

Hi @Steven Emmett,

Thank you for posting your question in the Microsoft Q&A forum.

According to your concern, this is confirmed as an expected behavior since ListView Command Sets don't appear in Teams views of lists/libraries. SPFx ListView Command Set buttons aren’t consistently supported in the Teams desktop experience when a SharePoint list/library is viewed within Teams (especially in the Files/SharePoint-hosted views). I have found many posts from different community note this behavior as a known limitation for Teams’ file/list rendering, which explains why it can work in SharePoint and sometimes in Teams for the web, but not in Teams desktop. You can refer to:

• ListView Command Set not available in Microsoft Teams File Tab · Issue #8724 · SharePoint
• azure - My SPFX ListView Command Set Not Showing in Microsoft Teams but Visible in SharePoint Online

(This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.)

Therefore, the suggested and most reliable approach is to use "Open in browser"/"Open in SharePoint". If your users need the button, this is the most dependable option that keep the list pinned in Teams but have users open it in a real browser when they need the command. When list opened in SharePoint, the command set button will appear and work normally.

If you need further assistance regarding this issue, I recommend posting your scenario in the Microsoft SharePoint · GitHub. This forum is dedicated to SharePoint/SPFx and is actively monitored by experienced users, Microsoft partners, and engineers who can provide detailed guidance and share best practices.   

Apologies for redirecting you to a different community as I'm forum moderators, my primary role is to guide users toward the appropriate resources and support channels and the category you initially posted in primarily focuses on Microsoft 365-related topics, therefore I may not have the depth of expertise needed for your questions.    

Thank you for your patience and understanding throughout this process. If you have any concerns or questions in the future, please don’t hesitate to reach out. Not only will I be happy to assist you, but all moderators in the Q&A forum will also do their best to provide support and guidance.  

I hope everything gets sorted out soon. Wishing you a fantastic day ahead.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".   

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread

The behavior is likely caused by how the site is loaded inside the new Teams desktop client rather than by the ListView Command Set or the flow itself.

In the new Teams desktop client, tabs that host websites or SharePoint pages can fail to load or behave differently from Teams for the web if:

1. The site is blocked from being embedded in other sites (X‑Frame‑Options / CSP restrictions).
2. Conditional Access policies are applied that affect how the content is rendered inside the Teams desktop container.

When this happens, parts of the SharePoint UX (including modern command bar extensions such as ListView Command Sets) might not render or behave as expected in the Teams desktop shell, even though they work:

• Directly in SharePoint in a browser, and
• In Teams for the web (which is effectively a browser experience).

Workarounds based on the documented behavior:

1. Use “Open in browser”
   • In the Teams desktop tab that hosts the SharePoint list, use the Open in browser option (banner/button) to open the list directly in the browser. The ListView Command Set button should appear and function there.
2. Use a dedicated SharePoint app tab
   • Instead of adding the list via a generic Website tab, add it using the SharePoint Pages (or SharePoint) app so that Teams uses the native SharePoint integration rather than a raw website frame. This can avoid some of the embedding and policy issues that block UI elements.
3. Review Conditional Access and embedding restrictions
   • If Conditional Access is enforced, review the policies as described in the Teams troubleshooting guidance for tabs. Policies that require specific client conditions can cause the Teams desktop shell to block or alter how embedded SharePoint content loads, which in turn affects custom commands.

If the button is visible and works in:

• SharePoint in the browser, and
• Teams for the web,

but not in the Teams desktop client, the issue is almost certainly related to how the SharePoint page is embedded/loaded in the desktop client (embedding headers or Conditional Access), not to the ListView Command Set or Power Automate integration itself. Using Open in browser or a dedicated SharePoint tab is the supported workaround.

References:

• A website doesn't load in the new Teams desktop client