Troubleshooting Updated October 2026

Copilot Studio agent not working in Teams or SharePoint? What to check

Two problems fill the Copilot Studio forums. The agent works in the test pane but says nothing in Microsoft Teams. Or it is connected to SharePoint and still answers "I can't find that". Both usually have ordinary causes. This guide lists them in the order worth checking.

Start Free Trial All guides
Publish is not deployPublishing does not add the agent to Teams by itself
Sign-in mattersAuthentication settings decide whether Teams messages reach the agent
The 7 MB limitWithout a Microsoft 365 Copilot license, SharePoint files over 7 MB are skipped
Permissions trim answersUsers only get answers from files they can open themselves
The Short Answer

Why is my Copilot Studio agent not working?

If the agent is silent in Teams, the message is usually not reaching it: the Teams channel is not connected, the app was not republished after a change, a Teams admin policy blocks it, or authentication is set up in a way Teams cannot complete.

If the agent answers but cannot find SharePoint content, the usual causes are file size (over 7 MB without a Microsoft 365 Copilot license in the tenant), the user lacking access to the file, content that is still being indexed, or files that hold text in images or scans.

Microsoft changes these limits from time to time, so confirm the current numbers on the Copilot Studio quotas and limits page.

Symptoms

Symptom, likely cause, what to check

Start at the top row that matches what you see.

SymptomLikely causeWhat to check
Works in the test pane, silent in TeamsTeams channel not connected, or the app in Teams is an old versionChannels page in Copilot Studio, then republish and update the app in Teams
Colleagues cannot find the agent in TeamsNot shared, or blocked by a Teams app policyAgent sharing settings and Teams admin center app permission policies
Asks users to sign in, then nothing happensAuthentication or SSO mismatch for TeamsSecurity settings: authentication type, and SSO configuration for Teams
"I can't find that" for a file you know existsFile over 7 MB, or the user cannot open itFile size, and the file's sharing for that user
Finds old content after you updated a fileIndexing delayWait and retest; check when the source last refreshed
Answers from the wrong sourceSeveral knowledge sources with vague descriptionsGive each source a clear description, or split the agent
Problem 1

Agent not responding in Microsoft Teams

  1. 1

    Connect the Teams channel after publishing

    The Publish button prepares a new version. It does not put the agent into Teams. Open Channels, turn on Microsoft Teams and Microsoft 365 Copilot, and add the agent to Teams from there.

  2. 2

    Share the agent with the right people

    Users who were not given access will not see the agent, or will see it but get no reply. Check who the agent is shared with and whether it was submitted for admin approval.

  3. 3

    Check authentication

    If the agent asks users to sign in, Teams needs a matching setup. "Authenticate with Microsoft" is the simplest option for Teams. Manual authentication needs SSO configured for Teams or users get stuck in a sign-in loop.

  4. 4

    Check Teams admin policies

    In the Teams admin center, the app has to be allowed by the app permission policy that applies to the user. Custom apps can be blocked tenant-wide.

  5. 5

    Republish and update the Teams app

    After any change, publish again. In Teams, the app under "Built for your org" may need an update or a reinstall before the new version answers.

  6. 6

    Test in Teams on the web

    If it works in the browser but not in the desktop app, the desktop client is caching an old version. Sign out and back in, or clear the Teams cache.

  7. 7

    Look for sessions in analytics

    If Copilot Studio shows no Teams sessions at all, messages are not reaching the agent. That points to channel, policy or platform problems, not topics. Open a Microsoft support case at that point.

Problem 2

Copilot Studio SharePoint knowledge not working

  1. 1

    Check the file size

    Without a Microsoft 365 Copilot license in the same tenant, generative answers only use SharePoint files under 7 MB. Larger files are ignored without a clear error. Split large PDFs into smaller ones, or upload the files directly as knowledge instead of linking the SharePoint site.

  2. 2

    Check the user's own access

    SharePoint answers are trimmed to the asking user's permissions. If the user cannot open the file in SharePoint, the agent will not use it for them. Test with an account that you know has access.

  3. 3

    Check authentication

    SharePoint knowledge needs the agent to know who the user is. With no authentication, or the wrong type, SharePoint sources return nothing.

  4. 4

    Wait for indexing

    New and changed files take time to show up in answers. If a test fails right after an upload, try again later before changing settings.

  5. 5

    Check the content itself

    Scanned PDFs, text inside images and complex tables are hard to search. A file that is mostly a screenshot gives the agent nothing to quote. Export a text-based PDF or a Word file.

  6. 6

    Narrow the sources

    One agent with ten SharePoint sites and vague descriptions will pick the wrong one. Fewer sources with clear descriptions give better answers.

When To Stop Debugging

If all you need is an FAQ bot

Copilot Studio is a capable builder, and most of the problems above are fixable. But many teams open it to build one thing: an HR or IT FAQ bot in Teams that answers from a set of documents. If that is your goal, a ready bot skips the channel, authentication and indexing setup.

ChatGridAI installs as a finished Teams app (and a Google Chat app). You upload files or pick them from SharePoint, OneDrive, Google Drive, Dropbox or Confluence, and they are indexed into a vector store in your own OpenAI account, so you can see exactly what the bot knows. Each department gets its own group of documents and its own list of people who can ask. Answers cite the source file.

See Copilot Studio alternative for the full comparison, or estimate the running cost with the Copilot Studio pricing calculator.

FAQ

Common questions

The most common reasons are that the Teams channel was never connected after publishing, the Teams app is an old version, a Teams app permission policy blocks it, or authentication is configured in a way Teams cannot complete. Check them in that order.
No. Publishing creates a new version of the agent. You still turn on the Microsoft Teams channel and add the agent to Teams, and after later changes you publish again and update the app in Teams.
Check file size first: without a Microsoft 365 Copilot license in the tenant, only SharePoint files under 7 MB are used for generative answers. Then check that the asking user can open the file, that authentication is set up, and that indexing has finished.
Microsoft documents 7 MB per SharePoint file for generative answers without a Microsoft 365 Copilot license in the tenant, and up to 200 MB with one. Files uploaded directly as knowledge can be larger. Check Microsoft's quotas page for current numbers.
Yes. A ready bot such as ChatGridAI installs as a finished Teams app, reads documents you upload or pick from SharePoint, and cites its sources. Setup takes under 30 minutes and it also works in Google Chat.

Skip the Copilot Studio setup

A ready HR and IT FAQ bot for Teams and Google Chat, on your own OpenAI account. Under 30 minutes to the first answer.

Start Free Trial Read the setup guide

$5/seat/month - 14-day free trial with 10 seats - no credit card required