Published Agents to Microsoft 365 and Teams not working

Question

Published Agents to Microsoft 365 and Teams not working

RSKenzz 96

I've currently deployed a couple of agents to Microsoft 365 and Teams via Bot Service in the New Foundry portal, but every time I ask it a question via the agent in Copilot, I get the following response - Sorry, I wasn't able to respond to that. Is there something else I can help with?

This response isn't getting logged within the agent's Traces section either in the New Foundry portal.

However, when asking a question directly to the Bot via the Chat section in Teams or using the Test Web Chat option against the Bot in the Azure portal, I don't get any response, but I can see the trace and a response in the Traces section in the New Foundry portal.

Any ideas?

Sridhar M 5,335 Reputation points Microsoft External Staff Moderator

2026-02-25T12:34:41.4266667+00:00
Hi RSKenzz

The behavior you are seeing is not a single issue, but a split failure across different hops in the Microsoft 365 Copilot → Bot Service → Foundry Agent pipeline. When Copilot responds with “Sorry, I wasn’t able to respond to that” and no trace appears in Foundry, it means the request never reached the Foundry Agent Application at all. Conversely, when Teams or Azure “Test in Web Chat” shows no UI response but Foundry Traces contain a model response, it means the request reached Foundry successfully, but the return path back to the channel failed.

Copilot responses are not logged in Foundry Traces

Microsoft 365 Copilot invokes your agent via the Azure Bot Service front door, not directly against the Foundry Agent endpoint. If Copilot cannot successfully route the request to the bot (due to app registration, tenant approval, or channel configuration issues), Copilot returns a generic fallback message and does not forward the request downstream. Because the request never reaches Foundry, no trace is generated, which exactly matches your observation.

Teams / Test Web Chat show no response even though Foundry has traces

In the Teams chat and Azure “Test in Web Chat” scenarios, your bot is successfully calling the Foundry Agent Application, which is why you see valid traces and responses inside Foundry. However, the Bot Framework channel is failing to deliver the response back to the client UI. This typically indicates a Bot Service return‑path issue (authentication, channel validation, or response rejection), not a Foundry or model problem.

The most common root cause: identity changes after publishing

When an agent is published from the New Foundry portal, it runs under a new Agent Application identity, which is different from the project-level identity used during testing. Any permissions, RBAC assignments, or tool access granted to the project identity do not automatically carry over. If the published agent lacks required permissions, failures may occur before or after model execution, resulting in silent channel failures or generic Copilot fallbacks

Copilot-specific requirement: app registration and admin approval

Publishing to Microsoft 365 Copilot creates an Entra app registration (App ID + Tenant ID) that must be approved and allowed in the tenant. If the app is unapproved, blocked by policy, or mismatched with the Bot Service registration, Copilot can discover the agent but cannot invoke it successfully, resulting in the exact fallback message you are seeing. This failure happens before bot invocation, which is why neither Bot logs nor Foundry traces appear.

Bot Service and Teams channel configuration impact

Even when Foundry is working correctly, Teams and Web Chat depend entirely on Azure Bot Service channel configuration. If the Teams channel is misconfigured, unhealthy, or failing validation on outbound messages, responses are silently dropped. Microsoft’s Bot Service documentation explicitly notes that bots can appear healthy while still failing message delivery if channel configuration or authentication is incorrect.

How to determine exactly where the failure occurs

You can isolate the break by checking Bot Service telemetry:

If Copilot messages produce no Bot Service activity, the failure is Copilot → Bot (app/tenant/policy).

If Teams messages produce incoming activity but no outgoing activity, the failure is Bot → Channel return path.

If Bot Service shows successful outbound messages but UI shows nothing, the channel is rejecting or discarding the response.

First, confirm that the Microsoft Teams channel is enabled and healthy on the Azure Bot Service resource. Second, verify that the App ID and Tenant ID generated during Foundry publishing exactly match what Copilot and the bot are using. Third, ensure that Azure AI User RBAC is assigned on the Agent Application resource, not just the Foundry project.

NOTE:This is not a model or Foundry runtime issue. The Foundry agent is demonstrably generating responses. The problem lies in channel integration and identity propagation between Microsoft 365 Copilot, Azure Bot Service, and the published Agent Application. Once app approval, RBAC, and Bot Service channel configuration are aligned, both Copilot and Teams will start logging traces consistently and returning responses to the user.

References:

Testing Your Bot In Web Chat

Connect a Bot to Channels

Publish Agents to Microsoft 365 Copilot and Microsoft Teams

Agent Identity Concepts

I Hope this helps. Do let me know if you have any further queries.

Thankyou!
SRILAKSHMI C 14,815 Reputation points Microsoft External Staff Moderator

2026-02-26T06:39:28.2666667+00:00

Hi Hi RSKenzz,

Did you get any chance to review the above response. Do let me know if you have any further queries.

Thank you!
Naman Bajaj 10 Reputation points

2026-02-26T09:35:52.6733333+00:00

Hi @Sridhar M ,

Even I am facing the same issue, after publishing the agent to Co-Pilot from AI Foundry , the Agent is not responding, getting error - ''Sorry, I wasn’t able to respond" , all the permissions are being assigned to Entra ID, being created by the bot.

Even tried exported the Zip file, manually importing it in Teams, which also failed to respond.

We raised a request with the Support team, even the MS support team face the same isssue from their end. We tried different regions as well, but the issue persists. An issue is being internally raised to the Product team.

Can you also try the same from your end and test? Attached the snippet for bot channel health status.
RSKenzz 96 Reputation points

2026-02-26T09:37:06.2866667+00:00

Hi @SRILAKSHMI C , thanks for your reply. I have approved the application in the 365 admin center, and the App ID on the Bot configuration matches the one in the Foundry portal.
Naman Bajaj 10 Reputation points

2026-02-26T11:29:23.8533333+00:00

Got an update from the backend team seems like isssue is being fixed from PG team. We had tested the agents, and now we are getting a response from Copilot.
RSKenzz 96 Reputation points

2026-02-26T11:33:58.42+00:00

Nope, I'm still getting the error. I've also just tried re publishing the agent, approved the deployment in the 365 Admin center too.
Sridhar M 5,335 Reputation points Microsoft External Staff Moderator

2026-02-26T12:57:45.24+00:00

Hi RSKenzz

Got an update from the backend team seems like issue is being fixed from PG team.please Can you try to check once
RSKenzz 96 Reputation points

2026-02-26T13:05:41.1866667+00:00

Nope, same error. Tried re publishing it again and approved the request too.
Sridhar M 5,335 Reputation points Microsoft External Staff Moderator

2026-02-27T12:30:51.8533333+00:00

Hi RSKenzz

We have escalated this issue to our Product Group (PG) team and are currently reviewing the details. The team is actively working on the investigation, and we will update you as soon as we have more information.
Naman Bajaj 10 Reputation points

2026-03-02T07:46:40.0766667+00:00

Yes, from Friday again, I am facing the same issue in the newly created Foundry. But no signin link pop up and its failing
SRILAKSHMI C 14,815 Reputation points Microsoft External Staff Moderator

2026-03-04T06:14:59.3+00:00

Hi RSKenzz,

The issue has been mitigated from the PG side. Please check on your end and let me know once you've confirmed.

Thank you!
RSKenzz 96 Reputation points

2026-03-04T10:23:34.65+00:00

Nope, still occurring. Tried redeploying too.
Manas Mohanty 14,660 Reputation points Microsoft External Staff Moderator

2026-03-05T10:21:22.2766667+00:00
Hi RSKenzz

Sorry for the trouble.

We have duplicate queries on same context. Multiple customers were impacted,

Duplicate thread

Post a hot fix was rolled out, it is working for customers now.

Tested in Canada East region, it asked to sign in then worked- Could you test in other supported regions.

Please clear cache and cookies then sign in again.

Could you share the resource id of Foundry Agent and Bot service via private message to tag in the respective engineering ticket.

Shall create separate engineering ticket if the issue persists.

Thank you.