microsoft-foundry / microsoft-foundry/foundry-samples
capabilityHost error with bicep script
Nobody has claimed this yet.
- Dominant language
- Bicep
- Stars
- 445
- Forks
- 494
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 38
Description
It looks like creating the resource account 'Microsoft.CognitiveServices/accounts@2025-06-01' created a default capability host, when the bicep script then attempts to create another capabilityHost and gets the following error.
"There is an existing Capability Host with name: ais-XXXX-eastus-05@aml_aiagentservice, provisioning state: Succeeded for workspace: 2f6d1613-555-xxxx-8672-205248a2fx5d/rg-xxx-ai-service-01/ais-XXXX-eastus-05@AML/XXcaphostaccteastus05, cannot create a new Capability Host with name: XXcaphostaccteastus05 for the same ClientId."
Has this worked in testing, so far this has not worked for us at all.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Bicep script that creates the Microsoft.CognitiveServices resource account and the additional capability host, then reproduce the deployment using the error details and resource names in this report. Done means identifying why the default capability host conflicts with the scripted one and documenting or correcting the deployment so it completes without the duplicate-host error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100