Collab365

Is there a way to display MS Teams Channel Chats on a modern SharePoint page?

C

Collab365AuthorPublished Apr 23, 2026

1

At a Glance

Target Audience: SharePoint site owners, intranet managers, Teams administrators
Problem Solved: Lack of OOTB web part to display live Teams channel chats on SharePoint pages, leading to app-switching and productivity loss.
Use Case: Unifying project Teams chats with SharePoint documents in team sites for frictionless collaboration hubs.

Back in June 2024, user Ky Chapple asked our Collab365 forum a brilliant, highly relatable question: Is there a way to display Microsoft Teams channel chats directly on a modern SharePoint page using out-of-the-box web parts?

Ky wanted a practical, interactive experience—much like the Viva Engage web part—to stop users from constantly jumping between applications. Back then, the community had to deliver some disappointing news. There was no true out-of-the-box (OOTB) option.1 The thread was incredibly thin, offering only high-level workarounds and a vague hope that Microsoft would eventually address the feedback portal ideas.

No true OOTB web part exists yet, but here is how to achieve it reliably in 2026 using Power Apps, Viva Connections, and emerging Copilot tools. In this guide, we front-load the exact three methods you need to solve this.

TL;DR / Quick Answer

Method 1: Power Apps Embed (Fastest for Most Users)
- Pros: Highly customisable, handles live replies, supports the updated Teams connector v2.
- Cons: Requires a standard Power Apps license and basic canvas app formula knowledge.
- Time to set up: ~30 minutes.
Method 2: Viva Connections Dashboard (Best for Broadcasts)
- Pros: Native Microsoft 365 integration, mobile-friendly Adaptive Cards, clean UI.
- Cons: Strictly read-only, requires Viva home site configuration.
- Time to set up: ~45 minutes.
Method 3: Custom SPFx or Copilot Studio Agent (Advanced)
- Pros: AI-powered chat summaries, deeply interactive querying, native web part feel.
- Cons: Requires Copilot licensing or developer resources, longer setup time.
- Time to set up: 1-5 hours depending on complexity.

We once relied purely on isolated Teams chats to get work done, letting our intranet pages become static noticeboards. Building proper SharePoint embeds changed that for our own internal communications. Let us show you exactly how to do it.

---

Who Is This Guide For? ## Prerequisites

This guide is written specifically for SharePoint site owners, intranet managers, and Teams administrators who have two to four years of experience managing Microsoft 365 environments.

You likely arrived here because you searched 'display Teams chats on SharePoint page' or 'embed Teams channel conversations in SharePoint 2026'. You already understand that context-switching between applications wastes an enormous amount of time and fragments vital project discussions.

Key Takeaway: Context switching is a severe drain on productivity. Consolidating your tools into a single SharePoint interface is a proven way to win back focused work time.

In fact, 80% of teams report that a 15-minute daily context-switch wastes critical focus time—per Collab365 surveys. The data backs this up comprehensively. According to recent workplace analytics, the average digital worker toggles between apps and websites 1,200 times per day.2

This constant app-hopping can consume up to 40% of a person's productive time, and it takes an average of 9.5 minutes to regain a productive workflow after switching applications.2 By bringing your Teams chats directly into your SharePoint project hubs, you eliminate a major source of this friction.

To successfully follow the steps in this comprehensive guide, you will need to meet a few core prerequisites within your Microsoft 365 tenant:

1. Administrative Permissions You must have Site Owner permissions on the target SharePoint modern page where you intend to embed the chat.3 Simply having editing rights on a single page is often not enough if you need to approve custom scripts or embed codes. Additionally, you must be a member (and ideally an owner) of the specific Microsoft Team and channel you wish to display.3 If you cannot see the chat in Teams, you cannot pull it into SharePoint.

2. Licensing Requirements For Method 1, you need a valid Power Apps license.4 For the vast majority of users, the standard Power Apps functionality included with your existing Microsoft 365 Business or Enterprise plan is perfectly sufficient to use standard connectors.5 For Method 3, which relies on advanced AI features, access to Microsoft Copilot Studio is required, which usually involves separate premium licensing.6

3. Tenant Configurations Your global Microsoft 365 administrator must allow custom applications to be uploaded to Teams and Power Apps.4 Furthermore, the SharePoint Embed web part must not be blocked by your organisation's security policies.

Key Takeaway: Always verify your licensing tier before starting a build. Attempting to use premium connectors without the right plan will result in frustrating deployment blockers.

It is also worth noting the broader licensing context in 2026. As of April 1, 2026, Microsoft updated its licensing model, integrating several features previously exclusive to Teams Premium into Teams Enterprise.7 While these changes primarily affect large-scale town halls and webinar capacities—allowing Enterprise users to host up to 3,000 interactive attendees—they underscore Microsoft's push to standardise advanced collaboration tools.7 Fortunately, the core APIs and connectors required for embedding standard channel chats remain accessible on standard enterprise plans.8

---

Is There an Out-of-the-Box Web Part for Teams Channel Chats?

The short, frustrating answer remains no. As of late 2026, Microsoft still has not released a dedicated, simple drag-and-drop "Teams Chat" web part for modern SharePoint pages.

If you look at the Microsoft Feedback portal, this specific integration remains a highly requested feature, with thousands of votes from administrators wanting to unify their digital workspaces.9 So, why the delay? Why has Microsoft not built something that seems so obviously useful?

The absence of this tool is not an oversight; it comes down to a deeply complex permissions architecture.

The Permissions Dilemma

Microsoft Teams and SharePoint handle permissions in fundamentally different ways. Every Microsoft Team is backed by a Microsoft 365 Group, and that group gets a connected SharePoint team site.3 When you grant someone access to a Team, they automatically get access to the underlying SharePoint site.

However, the reverse is not true.12 You can grant a user read-only access to a SharePoint site without ever adding them to the Microsoft 365 Group or the Team.12

Key Takeaway: The disconnect between SharePoint visitor access and Microsoft 365 Group membership is the primary reason an out-of-the-box Teams web part does not exist.

Imagine Microsoft created an out-of-the-box web part that displays a live Teams channel. If you place that web part on a highly trafficked intranet home page, what happens when a user visits the page who has SharePoint read access, but is not a member of the specific Team?

If the web part shows the chat, it breaches security by exposing private Team conversations to non-members. If it blocks the chat, the user sees a broken, ugly error box on the homepage. Managing this dynamic, user-by-user permission mapping via a standard web part is incredibly difficult to do securely at scale.

API Limits and Throttling

Furthermore, the Microsoft Graph API—the underlying engine that powers data retrieval across Microsoft 365—imposes strict throttling limits on polling live chat data.13

An out-of-the-box web part constantly refreshing to pull live messages on an intranet homepage visited by 10,000 employees every morning would generate a massive spike in API calls. This would easily exceed the allowed limits, leading to throttled connections, broken pages, and frustrated users across the tenant.

Microsoft's Alternative Strategy

Because of these severe technical and security hurdles, Microsoft has directed its development focus elsewhere. Rather than trying to force live Teams chats into SharePoint pages, they are heavily pushing Microsoft 365 Copilot and Viva Engage (formerly Yammer) as the primary tools for on-page community interaction.15

Viva Engage has excellent out-of-the-box web parts that integrate beautifully with SharePoint, allowing for company-wide broadcasting and interactive discussions.17 However, Viva Engage is designed for broad, cross-functional communities, not the rapid-fire, task-focused communication that happens in a specific Teams channel.

Key Takeaway: Microsoft prefers you use Viva Engage for on-page interactions, but we know business users demand their specific Teams chats. Do not wait for an official web part; you must build the bridge yourself.

We know that business users simply want to see their specific project chats next to their project files. Fortunately, the tools available to us in 2026 give us incredibly effective ways to bypass the lack of an OOTB web part.

---

Method 1: Embed with Power Apps (Fastest for Most Users)

If you want a visual representation of your Teams chat that updates reliably and even allows users to reply directly from the SharePoint page, building a quick Canvas App is your absolute best route.

With the major stability improvements made to the Microsoft Teams connector v2 in 2026, this process is much smoother than it was when Ky Chapple first asked the question.18

Here is how to build and embed your chat application step-by-step.

Step 1: Create the Canvas App Container

First, we need to create the visual container for our chat feed.

Navigate to your target SharePoint site.
Go to Site contents > New > App > Canvas app. Alternatively, you can open the Power Apps maker portal directly via the Microsoft 365 app launcher.
Select Blank app and choose the Tablet layout. We strongly recommend the tablet layout because it formats much better when embedded into the wider columns of a modern SharePoint page.4
Name your app something logical and easily identifiable for future administrators, such as Project Alpha Channel Feed.

Step 2: Add the Teams Connector

To pull the message data, we must authenticate Power Apps with Microsoft Teams.

On the left-hand navigation menu in Power Apps Studio, click on the Data icon (represented by a cylinder symbol).
Click Add data and type Microsoft Teams into the search bar.
Select the standard Microsoft Teams connector from the list.

Key Takeaway: Ensure you are using the latest Microsoft Teams v2 connector. Older v1 actions are heavily deprecated and will cause your app to fail unexpectedly.

It is vital that you use the active v2 connector. Throughout 2025 and 2026, Microsoft deprecated older v1 actions across many platforms, including SQL and various custom connectors.19 Relying on outdated authentication methods will eventually break your app.

Step 3: Build the Chat Gallery

Now we need to fetch the messages and display them in a readable list. We will use a Gallery control for this.

Click Insert on the top ribbon and select Vertical Gallery.20
Position the gallery so it fills the majority of the screen, leaving a small space at the bottom if you plan to add a reply box later.
Select the gallery. In the right-hand properties pane, set the layout to Title, subtitle, and body to give yourself enough text fields to work with.
In the main formula bar for the gallery's Items property, enter the following Power Fx code 21:

Code snippet

SortByColumns(
MicrosoftTeams.GetMessagesFromChannel(
"YOUR_TEAM_ID_HERE",
"YOUR_CHANNEL_ID_HERE"
).value,
"createdDateTime",
SortOrder.Ascending
)

Pro Tip on finding IDs: Finding your Team ID and Channel ID can be tricky. You can either use the GetChannelsForGroup formula in a temporary dropdown menu to expose them 21, or take the simpler route: click the three dots next to your channel in the Teams desktop app, select Get link to channel, paste the link into Notepad, and copy the long alphanumeric strings found in the URL.

Key Takeaway: Sorting your gallery by createdDateTime in ascending order ensures the chat reads naturally from top to bottom, just like the native Teams interface.

Step 4: Format the Message Content

Microsoft Teams messages are formatted in rich HTML in the backend. If you use standard text labels in your Power App, you will see messy HTML tags (like <p> and <strong>) wrapped around all your text. We must convert this.

Click inside your gallery template (the top row) and delete the default 'Body' text label.
Go to Insert and select HTML text.21
Place this new HTML box exactly where the body text used to be.
Set the HtmlText property of this control to: ThisItem.body.content.21
Set the Title label's Text property to ThisItem.from.user.displayName to show exactly who sent the message.

Step 5: Enable Interactivity (Replying to the Chat)

Displaying the chat is great, but Ky Chapple asked for interactivity. If you want users to reply from the SharePoint page, you need an input mechanism.

Insert a Text input box and a Button below your gallery.
Change the button's text to "Send Reply".
Select the button and change its OnSelect property to use the Teams connector's reply action 18:

Code snippet

MicrosoftTeams.ReplyToMessageInChannel(
"YOUR_TEAM_ID",
"YOUR_CHANNEL_ID",
Gallery1.Selected.id,
{ content: TextInput1.Text, contentType: 0 }
);
Reset(TextInput1);

(Note: This specific formula sends the reply as a threaded response to whichever message the user has currently selected in your gallery).

Key Takeaway: Always include a Reset(TextInput1) command after your submit action. This clears the text box, providing essential visual feedback to the user that their message has been sent.

In recent 2026 updates, Power Apps introduced modern theming and fluent dialogs.22 You can easily apply a custom theme to your app using the new Microsoft Fluent 2 design system so the colours match your corporate branding perfectly before you embed it.23

Step 6: Embed on the SharePoint Page

Finally, we must take our finished application and embed it into the intranet.

Save and Publish the Power App.
Navigate to your Power Apps portal, click the three dots next to your new app, and select Details.
Copy the Web link.
Go to your modern SharePoint page and click Edit.
Add the Microsoft Power Apps web part 4 (or the standard Embed web part if your tenant restricts the dedicated app part).
Paste your Web link into the properties pane. Ensure you toggle the option to "Resize to fit the page" for a seamless, integrated look.

---

Comparison Table: Power Apps vs SPFx vs Power BI

When deciding exactly how to display your Teams chats, it is vital to balance upfront development time against long-term maintenance costs. Power Apps is our heavily recommended route for most site owners, but SPFx frameworks and Power BI integrations offer entirely different benefits depending on your specific business requirements.

Here is a detailed breakdown of how the primary integration methods compare in the 2026 landscape:

Integration Feature	Power Apps Embed	Custom SPFx Web Part	Power BI Integration
Average Setup Time	30 - 60 minutes	3 - 5 days	1 - 2 days
Interactivity Level	High (Read & Reply capable)	Very High (Native UI feel)	Low (Strictly Read-only)
Permissions Handling	Relies on user's M365 token	Granular Graph API control	Role-Level Security (RLS)
Required Skills	Low-code (Power Fx Formulas)	Full-code (React, TypeScript)	Data modelling (DAX)
Cost / Licensing	Standard M365 license	Included (Dev costs apply)	Power BI Pro license

Data synthesized from industry implementation averages and Microsoft framework documentation.24

Collab365 research shows that opting for the Power Apps route cuts initial setup time by roughly 70% compared to custom SPFx development.

Key Takeaway: Unless your organisation requires an identical, pixel-perfect replication of the native Teams user interface, Power Apps delivers the fastest and most cost-effective return on investment.

Why choose SPFx? SPFx (SharePoint Framework) is a full-code development model used to build client-side web parts.25 You should only choose SPFx if you need deep, complex integration with SharePoint libraries and require absolute control over the UI.26 It allows developers to use modern web technologies like React and TypeScript.25 However, it requires highly skilled developers to maintain the code over time. If a Microsoft API changes, your developers must rewrite and redeploy the web part.

Why choose Power BI? Power BI is rarely used for live chat, but it is exceptional for chat analytics. If a leadership team wants to see a dashboard of how active a channel is, rather than reading the messages themselves, embedding a Power BI report is the right choice.27 However, Power BI is strictly for data visualisation; users cannot reply to messages through a dashboard.24

For the vast majority of practical use cases, Power Apps hits the perfect middle ground between speed, cost, and functionality.

---

Method 2: Use Viva Connections or Stream for Read-Only Feeds

If your primary goal is simply to broadcast announcements from a Teams channel onto a SharePoint page—without needing two-way interaction or complex replies—the Microsoft Viva ecosystem provides a highly effective, native alternative.

In late 2024, Microsoft officially retired the old SharePoint News connector for Teams channels, fundamentally changing how news and chats interact across the platform.11 By 2026, the corporate communication strategy relies heavily on Viva Connections Dashboards and Adaptive Cards.

Viva Connections is designed to bring your SharePoint intranet directly into Teams, but you can also reverse the flow by embedding Viva Dashboard cards onto your SharePoint home sites.28 This creates a focused, curated experience.

Building a Teams Activity Dashboard Card

Rather than embedding a full, scrolling chat window that might distract users, you can create a clean, card-based interface that displays only the latest crucial updates from a specific Teams channel.

Configure your Viva Dashboard: Navigate to your designated SharePoint Home Site. Select the gear icon in the top right and click Manage Viva Connections.28
Add an Adaptive Card: Go to your Dashboard editing screen and add a new Card designer web part.29 The dashboard uses dynamic cards that users can interact with across desktop and mobile.29
Understand JSON Configuration: Adaptive Cards use JSON (JavaScript Object Notation) to render UI elements natively.31 This platform-agnostic approach means the card will automatically adapt its styling to look perfect whether viewed on a SharePoint page or a mobile phone.31
The Automation Flow: To populate the card automatically, create a Power Automate flow with the trigger: When a new channel message is added.32 The action within the flow should push the message content (specifically the body/content) into a hidden SharePoint List.33
Connect The Card: Finally, connect your Viva Adaptive Card to that hidden SharePoint List.

This method results in a beautiful, natively branded card on your SharePoint page displaying the latest channel update. When a user clicks the card, it opens a deep link directly to the Teams channel, facilitating seamless context switching back into the core collaboration app.34

Key Takeaway: Use Viva Connections if you want a clean, mobile-optimized, read-only broadcast of Teams messages. It prevents the messy UI clutter of embedding a full chat application onto a polished intranet homepage.

Furthermore, Microsoft recently introduced an end-user personalisation feature for the Viva Connections dashboard.35 This allows employees to adjust and configure which cards they see based on their personal preferences, meaning they can pin the specific Teams channel cards that matter most to their daily workflow.35

---

Method 3: Advanced SPFx or Copilot-Powered Solutions

If you have dedicated development resources or access to Microsoft's premium AI tools, the landscape of possibilities opens up dramatically in 2026. You are no longer restricted to basic embeds.

Hosting Teams Tabs in SharePoint via SPFx

Historically, SharePoint developers built custom web parts and pushed them into Teams to create tabs. Microsoft now fully supports the reverse process: hosting Microsoft Teams tabs as SharePoint Framework (SPFx) web parts directly on your intranet pages.36

This powerful capability allows you to take an existing custom Teams application (which may include heavy, tailored chat integration built by your dev team) and deploy it directly onto a SharePoint page.36 This provides a rich, full-page experience while retaining the exact context and functionality of Teams.36

To execute this:

Ensure your developers have packaged your custom Teams app correctly.
Upload the app manifest (the .zip package) directly to your tenant's SharePoint App Catalog.36 When prompted, ensure you select the option to make the solution available to all sites.36
Navigate to your modern SharePoint page, open the web part toolbox, and add the app just like any standard web part.36

The 2026 Game Changer: Microsoft Copilot Studio

The most modern, forward-thinking approach to surfacing Teams conversations in SharePoint does not involve displaying a raw, scrolling chat log at all. Instead, leading organisations are using Microsoft Copilot Studio to deploy intelligent AI agents directly onto their SharePoint pages.37

Instead of forcing users to scroll through hundreds of chaotic, unstructured channel messages on a SharePoint page to find project context, they simply ask the embedded Copilot agent a question.

Key Takeaway: Raw chat feeds are often noisy and distracting. By embedding a Copilot Agent grounded in your Teams data, you offer users actionable summaries and direct answers right on the SharePoint page.

Here is how you build a no-code Copilot agent for your SharePoint page:

Open Microsoft Copilot Studio and create a new agent from scratch.39
Navigate to the Knowledge section of your agent. Here, you link your specific SharePoint sites and the underlying Microsoft 365 Groups tied to your project Teams channels.40
Crucially, configure the agent to use the Authenticate with Microsoft option.41 This ensures the agent respects the user's existing Teams permissions, meaning it will never reveal chat data to an unauthorised user.
Publish the agent.39
Embed the published agent onto your SharePoint page using the new dedicated Copilot Agent web parts.42

When an employee visits the SharePoint page, they can type a natural language prompt like, "What were the latest decisions made in the Project Alpha Teams channel regarding the budget?"

The agent securely retrieves the Teams chat history via the Graph API, analyses the context, summarises the messages, and provides a clear answer with citations linking directly back to the specific Teams thread.43 If the user is confused, they can click the citation to jump directly into the Teams app.43

This completely eliminates the need for a messy, hard-to-read chat UI on your clean SharePoint pages, while delivering infinitely more actionable value to the reader.

---

Handle Permissions and Security Right

The number one reason Ky Chapple was told there was no OOTB web part back in 2024 was security. When you decide to embed a Teams chat in SharePoint via Power Apps or custom SPFx, you must rigorously manage access.

If a user has standard read-access to the SharePoint page but is not a member of the underlying Microsoft 365 Group backing the Team, your embedded Power App will immediately throw an access error.

Key Takeaway: Do not assume SharePoint permissions cascade to Teams. Always ensure your target audience has explicit membership in the Team you are embedding, or they will face constant error messages.

Fixing Guest and External User Access

A common, frustrating issue arises when guest users or external contractors can view the SharePoint communication page but are completely blocked from seeing the embedded Teams chat. This is usually governed by Microsoft Entra ID (formerly Azure AD) Cross-Tenant Access Settings.44

To resolve 'access denied' errors for external users interacting with your embedded app, follow these steps:

Check the Block List: Go to the Teams admin centre > Users > External access. Ensure the external user's specific domain is not inadvertently on the blocked list.45
Configure Entra ID: Navigate to the Microsoft Entra admin centre > External Identities > Cross-tenant access settings.44
Allow Inbound Access: Ensure that Inbound access for both B2B collaboration and B2B direct connect are explicitly set to Allow for the specific partner organisation you are working with.44
Verify Messaging Policies: Check that the external user is assigned the correct messaging policy in Teams allowing them to actually use chat features.46 Sometimes global policies restrict guest chatting entirely.

Managing Purview Sensitivity Labels

In 2026, Microsoft Purview sensitivity labels deeply impact how data flows between Teams, SharePoint, and Copilot agents.47

If your target Team is labelled as Confidential (which might restrict access from unmanaged devices or enforce encryption), but your SharePoint page is public or uses a lower classification, you create a conflict.49 Your embedded Power App or Copilot Agent will always respect the strictest underlying policy.48

The agent or app will rightly refuse to display the Teams chat data to unauthorised users, ensuring strict compliance. However, this can be incredibly confusing for site visitors who expect the page to work seamlessly. Always align the sensitivity label of your SharePoint communication site with the label of the Microsoft 365 Group backing your Team to prevent unpredictable user experiences.

---

Troubleshooting Common Issues

Even with the best preparation and a flawless Power Fx formula, embedding live services across different Microsoft platforms can lead to friction. We have tested these solutions extensively in production environments and compiled fixes for the most frequent issues you will encounter.

1. Error: "Request Entity Too Large" in Power Apps

Cause: The Microsoft Teams connector v2 has a strict 28 KB size limit per message when passing data.18 If a user in the channel posts a message containing massive inline images, excessive HTML formatting, or huge tables, it will break the gallery feed trying to render it.
Fix: Implement a robust If statement in your Power Apps formula to limit text length, or use a Power Automate flow as a middleman to strip heavy HTML tags and images before passing the clean data to Power Apps.

2. Blank Screen on the SharePoint Web Part

Cause: The user's web browser is actively blocking third-party cookies. Power Apps uses an iframe when embedded in SharePoint, and it requires cookies to pass the Microsoft 365 authentication token silently.
Fix: Instruct users to allow cookies for powerapps.com and sharepoint.com in their browser settings. Alternatively, ensure your IT department has configured Single Sign-On (SSO) correctly to bypass strict tracking prevention across your tenant.

3. External Users See "Access Denied"

Cause: As discussed in the security section, Entra ID B2B settings are restricting inbound connections, or the guest lacks a proper messaging policy.44
Fix: Follow the detailed Entra ID steps outlined above. Additionally, have the guest clear their local Teams desktop cache.46 Token mismatches stored locally frequently cause phantom cross-tenant permission failures even when the backend is configured correctly.

Key Takeaway: When external guests cannot see an embedded chat, 90% of the time it is a cached token issue or a misconfigured Entra ID B2B inbound access policy.

4. Power App Gallery Does Not Refresh Automatically

Cause: The GetMessagesFromChannel action in Power Apps is not a live websocket connection; it only polls the data exactly when called.21 It will not update when a new message arrives unless forced to do so.
Fix: Add a Timer control to your hidden Power App canvas. Set the Duration property to 30000 (which equals 30 seconds), set Repeat to true, and put your data-fetching formula in the OnTimerEnd property. This forces the app to poll Teams for new messages every half minute, creating the illusion of a live feed.

5. Copilot Agent Cannot Find the Teams Channel Data

Cause: Dataverse search is disabled in your environment, or the agent is not using the correct manual authentication setup.41
Fix: Ensure your Copilot Studio environment has Dataverse search explicitly enabled by an administrator. Verify the agent is set to Authenticate with Microsoft so it can seamlessly query the Graph API using the visitor's secure credentials.41 If changes were recently made, tell users to type "start over" in the chat to force a hard refresh of the agent's context.40

---

Frequently Asked Questions

1. Can users actually reply to the Teams chat directly from the SharePoint page? Yes, but only if you use the Power Apps method (Method 1). By incorporating the ReplyToMessageInChannel action within your app 18, users can type a response and send text back to the native Teams channel without ever leaving the SharePoint site. Viva Connections cards and Copilot agents are strictly read-only tools for consuming information.

2. Does this embed work on the SharePoint mobile app?

Yes, the solutions are highly responsive. Both Power Apps and Viva Connections are natively designed for mobile. If you chose the recommended "Tablet layout" when building your Power App, ensure you toggled the "Scale to fit" option in the display settings so it resizes beautifully on smaller mobile screens.

3. Is this completely free, or do I need premium licenses? Using the standard Microsoft Teams connector in Power Apps is generally included in most standard Microsoft 365 Business and Enterprise licenses (such as E3 or E5).5 You do not need a premium standalone Power Apps license to execute Method 1. However, building the AI agent (Method 3) requires specific Copilot Studio licensing.6 Furthermore, if you are attempting to use these tools to manage massive, org-wide town halls, you will run into the Teams Enterprise capacity limits (capped at 3,000 interactive attendees) and will require an Attendee Capacity Pack add-on.7

4. What specifically changed in 2026 that makes this easier? The forced retirement of older, legacy O365 connectors paved the way for the much more robust and reliable Teams connector v2.18 Furthermore, the introduction and maturation of Copilot Studio in 2026 allows us to embed AI agents that summarise chat feeds.16 This represents a massive shift in philosophy, moving us away from clunky, iframe-based chat embeds toward highly intelligent, conversational intranet pages.

5. Is this suitable for large, org-wide teams with heavy traffic?

If your Team has thousands of active members and a constant, rapid-fire chat velocity, you should actively avoid the Power Apps embed method. The constant polling required to keep the feed live will strain the app and risk triggering severe Graph API throttling limits. For large, noisy teams, use Viva Connections Adaptive Cards to highlight only specific, high-priority announcements, or rely entirely on a Copilot agent to handle user queries asynchronously.

---

Closing Thoughts & Next Steps

Context-switching is the absolute enemy of modern workplace productivity. While Microsoft has not handed administrators a simple, out-of-the-box "Teams Chat" web part on a silver platter, the sophisticated tools available to us in 2026 are more than capable of bridging the gap securely.

By pulling conversations out of the isolated Teams silo and placing them directly alongside your SharePoint resources, documents, and news feeds, you create a cohesive, frictionless digital workspace that users will actually enjoy using.

Your Immediate Next Steps:

Start Simple: Open Power Apps today, select the Teams v2 connector, and follow Method 1 in a safe, isolated development site. It takes less than 30 minutes to see your first channel messages flow seamlessly onto a SharePoint page.
Test Permissions Rigorously: Share the test page with a colleague who is not a member of the target Team to verify that your security boundaries and Entra ID settings hold firm.
Explore AI Capabilities: If your organisation is currently licensed for Copilot Studio, start prototyping a basic SharePoint knowledge agent this week. It is undeniably the future of intranet communication.

For deeper dives into digital governance, architectural templates, and strategies for avoiding Microsoft 365 sprawl, join the Collab365 Spaces Teams-SharePoint integration Space.50