Description:
After the deployment completes, navigate to the agent playground link shown in the post-deploy output and try out some test inputs. The Agent Playground remains stuck in a loading/spinning state and no response is returned. Details are as follows.
The issue occurs with the following agents:
Except for AgentWithTextSearchRag and AgentsInWorkflows, pytest runs for the other agents (agents-in-workflow, agent-with-text-search-rag, agent-with-foundry-tools, echo-agent, web-search-agent) also fail due to request timeouts.

Steps to Reproduce:
- Initialize the project:
azd init --template Azure-Samples/ai-foundry-starter-basic.
- Initialize AI agent:
azd ai agent init -m https://github.com/microsoft-foundry/foundry-samples/blob/main/samples/python/hosted-agents/agent-framework/echo-agent/agent.yaml and select location southcentralus.
- Run
azd up.
- Navigate to the agent playground link.
- Enter a test message, such as: "Hello world!"
Environment:
Expected Behavior:
The Agent Playground chat works correctly, and pytest also passes successfully.
@JeffreyCA and @rajeshkamal5050 for notification.
Description:
After the deployment completes, navigate to the agent playground link shown in the post-deploy output and try out some test inputs. The Agent Playground remains stuck in a loading/spinning state and no response is returned. Details are as follows.
The issue occurs with the following agents:
Except for AgentWithTextSearchRag and AgentsInWorkflows, pytest runs for the other agents (agents-in-workflow, agent-with-text-search-rag, agent-with-foundry-tools, echo-agent, web-search-agent) also fail due to request timeouts.

Steps to Reproduce:
azd init --template Azure-Samples/ai-foundry-starter-basic.azd ai agent init -m https://github.com/microsoft-foundry/foundry-samples/blob/main/samples/python/hosted-agents/agent-framework/echo-agent/agent.yamland select locationsouthcentralus.azd up.Environment:
southcentralus.Expected Behavior:
The Agent Playground chat works correctly, and pytest also passes successfully.
@JeffreyCA and @rajeshkamal5050 for notification.