Agent loses access to knowledge when published in Teams

(0) Share

Report

Posted on by imscavok

I'm working on getting a bot published as a demo and testing platform. I created a generative AI agent and set a SharePoint site with corporate policies as a knowledge source. Within the design copilot studio environment, I can ask "How much vacation do employees get?" and it will provide a perfect answer and cite the employee handbook.

When I ask the same question to the agent in Teams, it is not able to answer it. "I don’t have access to specific internal policies of companies like COMPANY. For accurate information regarding vacation days, I recommend checking your employee handbook or contacting your HR department directly. They will be able to provide you with the most accurate and detailed information."

I'm using the same account in Copilot Studio and Teams. I'm using Authenticate with Microsoft. Is there any way to troubleshoot this?

Categories:

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Artur Stepniak 1,539 Super User 2025 Season 2 on at

Like (0)

Report

Hello,

it could be the case that there are some prompts which are added to the system prompt or somewhere, which alter the behaviour of the bot, when it's deployed to Teams. You'd need to try to alter the system prompt a bit and test, test, test... It's hard to tell what is the cause of this.

You could also try with Sharepoint agents - I've seen that they're generally working better than the "standard" Copilot Studio ones with SP data: https://support.microsoft.com/en-us/office/get-started-with-agents-in-sharepoint-69e2faf9-2c1e-4baa-8305-23e625021bcf.

In the meantime - I've just opened a group related to Copilot stuff. Maybe you'd like to join? I plan for it to be the place, where we can help each other. Here's the link: https://community.powerplatform.com/usergroups/details/?groupid=dbc367c2-b7b7-ef11-b8e8-7c1e5259f813.

In case of any other questions, let me know. If the answer helped you, mark it, so that others can benefit from it.

Best regards,

Artur Stepniak

Was this reply helpful? Yes No
imscavok 8 on at

Like (0)

Report

It's not a prompt issue. The Teams agent responds strictly by stating it doesn't have access to any specific company policies, including [mine]. The same agent in Copilot studio asking the same question simply provides the correct answer and a citation. It's perfect. But I have no way of giving anyone access to actually use it.

My tenant doesn't have access to Sharepoint agents yet. I guess that's what I'll have to wait for. I'm kind of shocked that I bought a $1200 license that doesn't work and I can't get any support from the vendor without an additional support contract.

Was this reply helpful? Yes No
Suggested answer

LG-17122012-0 2 on at

Like (2)

Report

I've experienced the same. At least in my case, the problem was the "Authenticate with Microsoft" configuration.
I created an auth app on Azure, configured it on my CoPilot, and now it works great!

Here is the video I used as a guide: https://www.youtube.com/watch?v=JTN7aa8X_AQ

If you're building a CoPilot for a company I recommend you configure your Azure app with "Accounts in this organizational directory only" instead of the video's option, "Accounts in any organizational directory". Also, check if your sharepoints are available to the needed users.

Hope this helps!

Was this reply helpful? Yes No
Suggested answer

juangonzalezAuc 84 on at

Like (1)

Report

You need to correctly configure an app registration to: Access Sharepoint sites and files, SSO with Teams

https://learn.microsoft.com/en-us/microsoft-copilot-studio/configuration-authentication-azure-ad
https://learn.microsoft.com/en-us/microsoft-copilot-studio/configure-sso-teams

The documentation above shows how to do both, you can skip the secret part in the sharepoint configuration, as you won't be using it if you are just deploying to Teams.
All the users also need to have access to the sharepoint site. And sometimes, just sometimes for some reason in my experience it takes a while to consider new site members.

Was this reply helpful? Yes No