Answered

Copilot Studio agent stuck after OneDrive consent and “Bad request” in Teams

(1) Share

Report

Posted on by VP-09031245-0

Hello everyone,

I am currently experiencing two issues with an agent developed and published in Copilot Studio, and I would appreciate any guidance or shared experiences from the community:

1️⃣ OneDrive connection issue

When running the agent, it prompts the user to grant permissions to connect to OneDrive for Business. However, after clicking “Allow”, the agent remains stuck at this step and does not continue generating responses. No additional error message is displayed, and the conversation does not progress.

2️⃣ “Bad request” error when sharing the agent in Microsoft Teams

Additionally, when the agent is shared with another user, the user receives a “Bad request” message when attempting to add the agent in Microsoft Teams, which prevents them from starting a chat with it. It is worth noting that the user has already been added to the agent’s access configuration in Copilot Studio.

Any insights regarding:

Proper handling of OneDrive connections in shared Copilot Studio agents.

Permissions, licensing, or publishing requirements to avoid the “Bad request” error in Teams

Thank you in advance for your support.

Captura de pantalla 2026-04-16 144650.png

Captura de pantalla 2026-04-16 144701.png

Categories:

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (8)

Answers (0)

Sort by

Vish WR 3,476 on at

Like (2)

Report
Copy link

Link copied!

@VP-09031245-0

Does the user having issues have the required licence ?

Was this reply helpful? Yes No
Prasad-MSFT Microsoft Employee on at

Like (3)

Report
Copy link

Link copied!
OneDrive Connection Issue (Stuck After “Allow”)
Possible causes:

The agent’s OneDrive connector is not fully configured or consent is not propagating.

The user’s permissions or tenant policies block delegated access.

There’s a backend issue with Copilot Studio’s OAuth flow.

What to check and try:

Connector Setup: In Copilot Studio, ensure the OneDrive for Business connector is properly added and configured for the agent.

Consent Propagation: Sometimes, tenant-wide admin consent is required. Ask your Microsoft 365 admin to grant admin consent for the OneDrive connector in Azure AD.

Clear Cache/Incognito: Try the flow in a private/incognito browser window to rule out stale cookies or cache.

Test with Different Users: See if the issue is user-specific or affects everyone.

Wait and Retry: Sometimes, consent propagation can take a few minutes.

“Bad request” Error When Sharing Agent in Teams
Possible causes:

The user does not have the required Copilot Studio or Microsoft 365 license.

The agent is not fully published or not available to Teams.

Permissions or access configuration is incomplete.

Teams client or Copilot Studio backend issue.

What to check and try:

Licensing: Ensure the user has a valid Copilot Studio (or Copilot for Microsoft 365) license.

Agent Publishing: Confirm the agent is published and enabled for Teams channel in Copilot Studio.

Access Configuration: Double-check that the user is added to the agent’s access list and that sharing settings allow Teams access.

Teams App Policies: In Teams Admin Center, verify that custom apps and Copilot agents are allowed for the user.

Try Web/Desktop: Test adding the agent in both Teams web and desktop clients.

Wait and Retry: Sometimes, publishing changes take time to propagate.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,031 on at

Like (3)

Report
Copy link

Link copied!

Hi @VP-09031245-0,

Two separate issues with different causes.

Issue 1 OneDrive consent loop (agent stuck after Permitir):
This happens because the OneDrive knowledge source is set to User authentication, which requires each user to individually consent via the FederatedKnowledgeSearchOperation prompt. The problem is that after the user allows it in Teams, the conversation context is lost and the agent doesn't continue.

Fix: In Copilot Studio go to Knowledge > your OneDrive source > edit the connection and switch authentication from User to Agent author authentication. This uses your credentials to access OneDrive on behalf of the agent, removing the per-user consent prompt entirely. This is the recommended approach when the data is not user-specific.

If the data needs to be user-specific and you must keep User auth, the workaround is to trigger the sign-in flow explicitly at the start of the conversation using the Sign In system topic, so consent happens before the query rather than mid-conversation.

Issue 2 "Solicitud incorrecta" (Bad request) when other users add the agent in Teams:
This is a Teams app availability issue. The agent needs to be approved and made available in Teams admin center before other users can install it. Being added to the Copilot Studio security group gives access to the agent's conversations but does not automatically install the Teams app for the user.

Fix:

1. A Teams admin must go to Teams admin center > Teams apps > Manage apps > find your agent > approve it
2. Set availability to your security group specifically (not all users) using app permission policies or app centric management
3. After approval, users in the group can install it without the Bad request error

Ref: https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-add-bot-to-microsoft-teams

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
VP-09031245-0 26 on at

Like (3)

Report
Copy link

Link copied!

@Vish WRHello, this is not only happening with one user; it’s something that occurs with several. What I’m not sure about is whether users who use the agent need to have some kind of license, and if so, which one. In other words, if 1000 users are going to use the agent, do they all need to have a license? This didn’t happen before, so I’m not sure if it’s due to some update in the Power Platform.

Was this reply helpful? Yes No
Vish WR 3,476 on at

Like (2)

Report
Copy link

Link copied!

@Prasad-MSFT

Does the user who uses the agent need a licence?

@VP-09031245-0

When you share , have you grated the permission ???

https://learn.microsoft.com/en-us/microsoft-copilot-studio/admin-share-bots?tabs=web

Was this reply helpful? Yes No
Prasad-MSFT Microsoft Employee on at

Like (3)

Report
Copy link

Link copied!

Hi Vish WR Yes—if you’re using a Copilot for Microsoft 365 agent, then every user who interacts with the agent in Teams must have a valid Copilot for Microsoft 365 license.

Without that license, users can experience issues like “Bad request” when trying to open the agent or the chat failing to start, even if they’ve been granted access in Copilot Studio.

Hi @VP-09031245-0 are you still facing this issue or has this been resolved? If it resolved, could you please share the findings what was causing the error/issue

Was this reply helpful? Yes No
VP-09031245-0 26 on at

Like (0)

Report
Copy link

Link copied!

@Prasad-MSFT Hello, I’m still having the same issue with a specific agent. However, I created a test one, published it, and shared the link with the same users, and they are able to access that test agent without any problem. I don’t understand why the “bad request” message is happening with that specific agent and not with the new test agent I published.

Was this reply helpful? Yes No
Prasad-MSFT Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
Hi VP-09031245-0
Since the newly created test agent is working correctly with the same users, this seems to be specific to the original agent configuration rather than a licensing or tenant-wide issue.

Could you please check the following for the affected agent:

Whether the Teams channel was removed/re-added after recent changes

If there are any custom authentication, OneDrive knowledge source, or connector configurations different from the test agent

Try republishing the agent and generating a new Teams sharing link

Verify whether cloning the affected agent reproduces the same behavior

Was this reply helpful? Yes No