Foundry Hosted Agents can't be created for west us3 region and South Central

Hello Rajender Akula
Thanks for the details. It looks like you’ve run into a regional support gap in the Foundry Hosted Agents service. According to our current docs, Hosted Agents are only available in a handful of Azure regions (for example East US, West US 2, Central US, North Europe, etc.) and West US 3 / South Central US aren’t on the list yet. That’s why your REST calls to westus3 are simply timing out (504) and South Central is rejected with “400 – Bad Request.”

Here are a couple of ways to work around it today:

Deploy your hosted agents into a supported region (e.g. East US or West US 2) even though your Foundry workspace lives in West US 3. – In your MCP-Tools or REST call, explicitly set the location to one of the supported regions. – The agents will still be able to connect back to your West US 3 Foundry workspace over the public endpoint.

If you really need the compute to reside in West US 3 or South Central US, spin up self-hosted agents there instead. – You can use an Azure VM Scale Set or container-based pool in that region. – Point your Foundry agent pool at those VMs or containers and you’ll get the same build/test/run capabilities.

Open a support request if you want to track an ETA for enabling Hosted Agents in West US 3 or South Central US. We can add you to the feature request so you’ll be notified when it goes live.

Reference commands for deploying to a different region via REST:

# Example: create hosted agent pool in West US 2
curl -X PUT \
  https://foundry.azure.com/subscriptions/{subId}/resourceGroups/{rg}/providers/Microsoft.Foundry/agentpools/{poolName}?api-version=2023-01-01 \
  -H "Content-Type: application/json" \
  -d '{
        "location": "westus2",
        "properties": {
          "agentSize": "Standard_D4_v3",
          "count": 5
        }
      }'

Hope that helps you unblock. Let me know if you have any questions on spinning up self-hosted agents or need help crafting your REST/CLI call

Check the below documents:
https://docs.microsoft.com/azure/foundry/hosted-agents-rest-api

https://docs.microsoft.com/azure/foundry/hosted-agents-skus-and-regions

Thanks for the response @Praveen Bandaru .

We tested your suggestion to force hosted-agent placement to westus2 while keeping the Foundry project in westus3.

What we tried:

1. Direct REST create-agent call to the project-scoped agents endpoint (preview header enabled).
2. Included location: "westus2" in the payload at:
   • top level (location)
     • hosted definition level (definition.location)
     1. Used the same known-good hosted agent config shape (kind=hosted, container image, cpu/memory, protocol, env vars).

Observed result:

1. Create call returned timeout from service:
   • HTTP status: 408
     • Error code: Timeout
       • Message: "The operation was timeout."
2. Follow-up list/get calls show no agent resource was created.
3. Behavior is reproducible.We tested your suggestion to force hosted-agent placement to westus2 while keeping the Foundry project in westus3.