MS Foundry prompt agent is not responding in Teams and Copilot 365

For this symptom, the most likely causes are in the published-agent runtime path rather than the Foundry playground path.

Check these areas in order:

1. Reset the conversation/session

• If the published agent stops responding or returns errors such as no tool output found, the conversation can enter a locked state.
• In Microsoft 365 Copilot, start a new chat with the agent.
• In Microsoft Teams, send /foundry_new_preview to reset the conversation.
• The previous conversation can't be restored after reset.

2. Verify the published agent identity and permissions

• If the agent works in the Foundry playground but fails after publishing, the agent identity can be missing permissions for the resources it uses.
• Assign the required roles to the agent identity for any Azure resources it accesses.
• If authentication or agent identity errors occur during execution, verify the agent identity application is enabled.

3. Verify user access and publish scope

• Authorization failures can occur if the user doesn't have access to the Foundry project, or if the agent was published to Shared scope, which uses Azure role-based access control.
• Verify the user has access to the Foundry project and an appropriate role.
• If appropriate for the deployment model, publish to Tenant scope so users get access through admin approval.
• If the agent is organization-wide, confirm a Microsoft 365 admin approved the request in the Microsoft 365 admin center.

4. Check networking if the agent is published through the VNet/API path

• If the channel adapter can't reach the agent, confirm DNS, DNAT, and TLS are configured correctly.
• Confirm the A record points to the firewall.
• Confirm the DNAT rule forwards port 443 to the reverse proxy.
• Confirm the reverse proxy presents a certificate for the configured hostname.
• If the agent receives messages but never replies, allow outbound access to:
  • smba.trafficmanager.net
  • login.microsoftonline.com
  • login.botframework.com
• If requests reach the agent but are rejected, confirm the validate-jwt policy uses issuer https://api.botframework.com and an audience that matches the bot's Microsoft App ID.

5. Check authentication and approval flow issues

• If requests fail because an MCP approval request wasn't approved, approve the pending MCP request in the conversation. If the approval card is gone, start a new conversation and retry.
• If sign-in or authentication times out, retry sign-in and complete authentication before submitting the request again.

6. Check licensing and service-plan prerequisites

• Tool calls can fail if required licenses or service plans aren't assigned and enabled.
• For Work IQ scenarios, 403 Forbidden can indicate the user is missing a Microsoft 365 Copilot license.
• After license assignment, provisioning can take 15–30 minutes.

7. Check request/runtime limits

• If another response is already in progress, wait for the current request to complete, then retry. If the session appears stuck, start a new conversation.
• If the context length is too large, start a new conversation or reduce the amount of content.
• If rate limits are exceeded, wait and retry later, reduce request frequency, or increase deployment capacity if this happens often.

8. If the agent is visible but not where expected

• Shared agents appear under Your agents.
• Tenant agents appear under Built by your org.
• Store visibility can also be delayed by cache refresh and admin approval timing.

9. If the issue is specific to the test panel rather than Teams/Copilot

• In Copilot Studio, a corporate firewall or proxy can block or buffer the /subscribe Server-Sent Events connection, causing the panel to appear unresponsive after the first message.

Based on the described behavior—works in Foundry preview, appears healthy after publishing, but does not respond in Teams/Copilot—the highest-value checks are:

• reset the conversation
• verify the published agent identity has resource permissions
• verify the identity is enabled
• verify user/project access and publish scope
• verify outbound/network and JWT validation settings if using the VNet/API publishing path

References:

• Publish agents to Microsoft 365 Copilot and Microsoft Teams by using the REST API + VNet Guidance
• Connect agents to Microsoft 365 with Work IQ (preview) (javascript)
• Agent doesn't respond in the Test your agent panel