Copilot Agent Publish working along with preview but not generating any response in teams and also new agent publish getting timed out

Question

Copilot Agent Publish working along with preview but not generating any response in teams and also new agent publish getting timed out

Subhra Sankar Roy 0

Copilot Agent Publish working along with preview but not generating any response in teams and also new agent publish getting timed out.

I have added multiple enhancements in the initial chatbot, in copilot preview everything is working as required but once i publish and open in teams, no response is coming.

Also newly created agents are not getting published.

Subhra Sankar Roy 0 Reputation points

2026-07-01T23:00:13.8833333+00:00
Additional troubleshooting performed

Existing agent "RAN Chatbot" is successfully published and available in Microsoft Teams.

Existing published agents continue to function.

Newly created agents remain in Publishing → Queued for approximately 15 minutes and then fail.

A minimal test agent with no knowledge, no tools and no skills also fails to publish.

Testing in the Default environment returns "Publish blocked by policy (DLP)".

Testing in Preview works correctly.

Issue is reproducible across multiple newly created agents.
Ashlesha Pawar (Tata Consultancy Services Limited) 395 Reputation points Microsoft External Staff

2026-07-02T05:46:58.6066667+00:00
@Subhra Sankar Roy

Recommended next steps:

Ask your Power Platform admin to review DLP policies applied to this environment (especially Copilot Studio, Teams/M365 channels, connectors/tools used by the agent).

Validate environment type/region and confirm Copilot Studio + Dataverse + Teams integration is allowed for that environment.

In Teams channel settings, republish, then reinstall/update the app in Teams and start a fresh chat (stale installs can show no response).

Test one clean production environment with no restrictive DLP as a control check.

If publish still queues then fails for minimal agents, open a Microsoft support ticket with:

Tenant ID, Environment ID, Agent IDs

UTC timestamps of failed publish attempts

Failure correlation/request IDs from Monitor/diagnostics

Screenshot/log showing “Publish blocked by policy (DLP)”
Ashlesha Pawar (Tata Consultancy Services Limited) 395 Reputation points Microsoft External Staff

2026-07-06T10:11:43.23+00:00

@Subhra Sankar Roy Could you please let me know if your issue has been resolved?
Subhra Sankar Roy 0 Reputation points

2026-07-06T10:50:40.89+00:00
@Ashlesha Pawar (Tata Consultancy Services Limited) I created a new chatbot with minimum instructions and added child agents to perform complex tasks, it is working fine. The old chatbot was a single bot with huge instructions and repeated publish actions might have corrupted the bot.

1 answer

Your answer

Subhra Sankar Roy 0 Reputation points

2026-07-01T23:00:13.8833333+00:00

Additional troubleshooting performed

Existing agent "RAN Chatbot" is successfully published and available in Microsoft Teams.

Existing published agents continue to function.

Newly created agents remain in Publishing → Queued for approximately 15 minutes and then fail.

A minimal test agent with no knowledge, no tools and no skills also fails to publish.

Testing in the Default environment returns "Publish blocked by policy (DLP)".

Testing in Preview works correctly.

Issue is reproducible across multiple newly created agents.
Ashlesha Pawar (Tata Consultancy Services Limited) 395 Reputation points Microsoft External Staff

2026-07-02T05:46:58.6066667+00:00

@Subhra Sankar Roy

Recommended next steps:

Ask your Power Platform admin to review DLP policies applied to this environment (especially Copilot Studio, Teams/M365 channels, connectors/tools used by the agent).

Validate environment type/region and confirm Copilot Studio + Dataverse + Teams integration is allowed for that environment.

In Teams channel settings, republish, then reinstall/update the app in Teams and start a fresh chat (stale installs can show no response).

Test one clean production environment with no restrictive DLP as a control check.

If publish still queues then fails for minimal agents, open a Microsoft support ticket with:

Tenant ID, Environment ID, Agent IDs

UTC timestamps of failed publish attempts

Failure correlation/request IDs from Monitor/diagnostics

Screenshot/log showing “Publish blocked by policy (DLP)”
Ashlesha Pawar (Tata Consultancy Services Limited) 395 Reputation points Microsoft External Staff

2026-07-06T10:11:43.23+00:00

@Subhra Sankar Roy Could you please let me know if your issue has been resolved?
Subhra Sankar Roy 0 Reputation points

2026-07-06T10:50:40.89+00:00

@Ashlesha Pawar (Tata Consultancy Services Limited) I created a new chatbot with minimum instructions and added child agents to perform complex tasks, it is working fine. The old chatbot was a single bot with huge instructions and repeated publish actions might have corrupted the bot.

Answer 1

Use the following checks and troubleshooting steps for both issues: no response in Teams and new agents timing out on publish.

Confirm the agent is correctly published and updated
- In Copilot Studio, verify the agent shows as successfully published.
- Remember that any changes made after publishing don’t take effect until the agent is published again.
- If publishing fails, use the Retry option in the publish dialog. If it keeps failing, review the agent configuration and try again.
Verify configuration and dependencies
- On the Publish page, review the publish status and any error details.
- Ensure all configurations are correct: agent settings, authentication options, and channel configurations.
- Check for missing dependencies such as topics, flows, connectors, and data sources.
Check Teams-specific behavior and limitations
- Teams can have known limitations when working with Copilot agents:
  - Customer satisfaction survey is text-only.
  - Teams renders up to six suggested actions per question node.
  - Attachments aren’t supported; if users send attachments, the agent responds that only text is supported.
- If the agent appears in Teams but returns a generic error or no response, it can be due to Teams caching an older configuration.
Work around Teams “SystemError” / stale configuration When Teams continues to use a previously published version of the agent after republish, users can see generic errors or no responses. To refresh the configuration:
1. In the Microsoft Teams admin center, locate the agent app, disable it, wait a few seconds, then re-enable it.
2. In Copilot Studio, turn off the Teams channel for the agent, save, then turn it back on.
3. Republish the agent so the latest version is available to Teams. If the issue persists, collect the Conversation ID, Agent ID, and the time of the error and contact Microsoft Support.
Troubleshoot publish timeouts / failures for new agents
- Ensure the agent has valid metadata and a unique identity (agent.identity not null) and that the developer name is 32 characters or fewer.
- If publishing to Microsoft 365 Copilot or Teams via Azure AI Foundry:
  - Confirm the identity has permission to create/update Azure Bot Service resources.
  - If a 403 AuthorizationFailed appears for Microsoft.BotService/botServices/write, assign the Azure Bot Service Contributor role on the resource group that contains the bot service, refresh credentials, and reopen the publish flow.
  - If publishing fails with an identity error, follow the migration guidance to ensure the agent has a unique identity.
If using a virtual network or restricted network
- If publishing from the portal returns 403, public network access might be disabled; use the API-based flow or download the manifest .zip and create the agent from it in the Microsoft 365 admin center.
- Ensure outbound traffic from the agent can reach required endpoints (smba.trafficmanager.net, login.microsoftonline.com, login.botframework.com) and that DNS/DNAT/TLS are correctly configured.
Verify the agent in Microsoft 365 Copilot/Teams
- In Microsoft 365 Copilot or Teams, open the agent store and confirm the agent appears under Your agents (Shared scope) or Built by your org (Tenant scope) after admin approval.
- Start a conversation and send a message; a successful reply confirms both inbound and outbound paths are working.

If after these steps the agent still doesn’t respond in Teams while working in preview, focus on:

For existing agents: refreshing the Teams app and channel as in step 4.
For new agents: resolving publish errors and identity/permission issues as in step 5.

References: