Co-Pilot - Adding Teams as a source knowledge is not available

Question

Co-Pilot - Adding Teams as a source knowledge is not available

ZTS 60

Adding Teams as a Knowledge source in Copilot Studio is not available even though it was in GA last June 2025 as per Use Teams chats as knowledge sources | Microsoft Learn. Please confirm if the is a known issue, needs to be configured or some environments ae region still not available.

0 comments

2 answers

Your answer

Answer 1

ZTS 60

We already have this information. Is this capability is currently only supported in the Agent Builder for M365 Copilot? Would this be updated?

Rin-L 17,575 Reputation points Microsoft External Staff Moderator

2025-08-12T10:45:15.87+00:00
Hi @ZTS,

Thank you for reaching out. Let me clarify each of your questions:

Is this capability currently only supported in the Agent Builder for M365 Copilot?

Not exactly. While the feature is officially available on both platforms, Agent Builder currently offers more reliable and immediate access to Teams as a knowledge source without requiring complex administrative setup.

Agent Builder is optimized for quick integration with Microsoft 365 data sources, including Teams.

Copilot Studio, on the other hand, requires proper tenant configuration, which many organizations have not yet completed.

Will this be updated?

Yes, Microsoft is actively working to bring feature parity between Agent Builder and Copilot Studio.

Teams integration is being expanded in Copilot Studio to match the capabilities of Agent Builder. You can refer to the roadmap here: New and planned features for Microsoft Copilot Studio, 2025 release wave 1 | Microsoft Learn

If you found this information helpful, marking the answer above as "Accepted answer" would be greatly appreciated. It helps others in the community discover useful information more easily.
ZTS 60 Reputation points

2025-08-13T14:14:35.86+00:00

Is there an ETA? could provide a ETA of when it will be available fully for Copilot Studio.
ZTS 60 Reputation points

2025-08-13T14:16:57.18+00:00

Do you have URLs reference for this statement " Not exactly. While the feature is officially available on both platforms, Agent Builder currently offers more reliable and immediate access to Teams as a knowledge source without requiring complex administrative setup. ?
Rin-L 17,575 Reputation points Microsoft External Staff Moderator

2025-08-14T10:54:40.4866667+00:00
Hi @ZTS,

Thank you so much for your follow-up question.

Based on my research, there is some information indicating that the “use Teams as a knowledge source” feature is available in:

Microsoft 365 Copilot (Agent Builder)

As documented here: Add knowledge sources to your declarative agent | Microsoft Learn

“You can configure agents to use Teams channels, meeting chats, group chats, and 1:1 chats as knowledge sources. You can choose to specify up to five links to channels, group, 1:1, or meeting chats to scope Copilot search, or you can allow your agent to use all the user’s Teams content…”

Microsoft Copilot Studio:

As described in: Use Teams chats as knowledge sources | Microsoft Learn

General availability: June 3, 2025 “With this update, you can add Teams knowledge sources as a URL endpoint or through a data source selector. This update supports messages that you share or send in channels, meetings, and group chats.”

These sources suggest that the feature is available across both platforms. If you have any additional insights or if I have misunderstood something, I would be truly grateful if you could share it.

In the meantime, since questions related to Copilot fall outside the scope of my direct expertise and support capabilities, I kindly recommend posting a new thread with the Microsoft Copilot tag.

This will ensure your question reaches the right experts who specialize in Copilot. They’ll be able to provide more accurate and detailed guidance. The reason I suggest posting under that tag is because our resources for testing Copilot are limited, and by posting there, you’ll be connected with the most qualified group of respondents. Other community members and partners who regularly follow the forums can also benefit from your question or contribute their knowledge.

Thank you for your understanding.

Answer 2

Hi @ZTS,

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

According to official Microsoft documentation, the Teams chats as knowledge sources feature for Copilot Studio is generally available and was released on June 3, 2025. This feature allows agents to use Microsoft Teams chat data, including chat history, meeting recordings and transcripts, shared files, and channel communications as knowledge sources.

The feature is generally available globally in regions where Copilot Studio is supported, including: United States, Europe, Asia Pacific, Australia, Brazil, Canada, India, Japan, Korea, Norway, South Africa, Sweden, Switzerland, United Arab Emirates, and United Kingdom.

Based on my research, there are several documented issues that may explain why Teams as a knowledge source is not appearing:

1. Administrative Configuration Required

Microsoft Graph connectors and enterprise data sources now require admin setup. Recent changes indicate that these connections must be configured by tenant administrators rather than individual makers.

2. Authentication and Permissions Issues

The feature requires proper authentication setup:

Makers cannot connect to Teams chats if they don't have meeting invites or aren't members of the team/channel
Agent users only receive responses from chats they can access
If permissions don't match, users get notified they cannot access the data source

3. Regional Data Residency Considerations

Teams data is stored in specific geographic regions, and there may be restrictions based on where your tenant's data is located versus where the Copilot Studio environment is hosted.

4. Licensing Requirements

To use this feature, users must have either:

A Microsoft 365 Copilot Chat license, or
An active Copilot Studio pay-as-you-go plan

Here are some ways you can try to check:

1.Check Administrative Settings:

Verify with your tenant administrator that Microsoft Graph connectors are enabled and configured properly. For your reference:

Microsoft 365 Copilot Connectors Overview | Microsoft Learn

Set up Microsoft 365 Copilot connectors in the Microsoft 365 admin center | Microsoft Learn

2.Verify Permissions:

Ensure you have proper access to the Teams chats, channels, or meetings you want to use as knowledge sources.

3.Confirm Regional Availability:

Check that your tenant's data location aligns with supported regions for this feature.

4.Review Licensing:

Confirm you have the appropriate Copilot Studio and Microsoft 365 licenses. Please refer:

Copilot Studio licensing - Microsoft Copilot Studio | Microsoft Learn

License options for Microsoft 365 Copilot | Microsoft Learn

5.Check for Service Issues:

There have been reported issues with knowledge sources not appearing or connecting properly.

For detailed guidance, refer to Microsoft’s official documentation: Troubleshoot enterprise knowledge sources - Microsoft Copilot Studio | Microsoft Learn

Thank you for your valuable time. I truly hope this information helps you better understand the root cause and explore the next possible steps toward resolving the issue.

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.

User's image

Rin-L 17,575 Reputation points Microsoft External Staff Moderator

2025-08-03T07:34:10.3233333+00:00

Hi @ZTS,

It has been a while and I am writing to see how things are going with this issue. Have you had a chance to check the replies provided? Any update would be appreciated.
Rin-L 17,575 Reputation points Microsoft External Staff Moderator

2025-08-04T07:12:12.1966667+00:00

Hi @ZTS,

I hope this message finds you well.

This is my second follow-up to check whether your issue has been resolved. I truly want to ensure your experience is as smooth as possible. If your problem is still ongoing or if you have faced any new difficulties, please share more details about the current steps you are stuck on. I am here and happy to provide further help whenever you need it.

While waiting for your response, I will continue tracking other customer questions on the forum to ensure everyone receives timely support. If you have additional questions, please feel free to tag my name in your reply so I can assist you promptly and more personally.

Looking forward to hearing from you soon.
M. Farid Retistianto 0 Reputation points

2026-04-02T09:56:09.1466667+00:00

Hi @Rin-L

I hope you do not mind me to following up this thread. I happened to work on this too, using Copilot Studio to build a declarative agent and found out that there is no access yet to Teams as knowledge as well.

I have license for the Microsoft 365 Copilot, within the country where this feature is available (Sweden), I can practically see Teams as source in Agent Builder and when I use the Copilot 365 directly on Web so that got us thinking what's left is the Admin permission.

Referring to the step provided previously here https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/deployment-overview, does it mean that the Admin would need to do the following?

Use the following steps to deploy a connector:

Sign in to the Microsoft 365 admin center.

In the left pane, choose Copilot > Connectors.

On the Connectors tab, in the left pane, choose Gallery, and select the data source you want to connect - so in this case Microsoft Teams would be present?

Enter a name to help users recognize the source in Copilot and search results. You can customize the default name.

Provide the URL of your data source. For example: https://your-organization-name.service-now.com.

Choose an authentication method to access the data source.

Deploy the connector to a subset of users for validation before a broader rollout.

Choose Create to deploy the connection. The connector begins indexing content using default settings.

And once the deployment is done, then it would be present in Copilot Studio?
Rin-L 17,575 Reputation points Microsoft External Staff Moderator

2026-04-05T12:03:54.8366667+00:00

Just to clear things up, there isn’t actually a need for an admin to deploy a Microsoft Teams connector through the Microsoft 365 admin center here. That deployment flow is designed for Copilot connectors that pull data from outside of Microsoft 365, like ServiceNow or Salesforce. Because Teams is already part of the Microsoft 365 ecosystem, you won’t find a “Microsoft Teams” option in the connector gallery, and there’s no separate step required to add it.

In Agent Builder within Microsoft 365 Copilot, Teams chats and meetings are treated as a native knowledge source. They’re available out of the box and always respect the user’s existing permissions. So if Teams content isn’t showing up or can’t be used in Copilot Studio on your side, it’s much more likely related to how the feature is rolling out, the current state of Copilot Studio, or specific environment settings, rather than a missing admin configuration step.

If Teams still isn’t appearing as expected, I’d gently suggest starting a new post and sharing a bit more context about your setup. That way, the conversation stays focused on your specific scenario, and it also makes it easier for other community members who’ve seen something similar to jump in with their insights or recommendations.

Thanks again for the follow‑up, and appreciate you being part of the discussion, @M. Farid Retistianto.

Share via

Co-Pilot - Adding Teams as a source knowledge is not available

2 answers

Your answer