Deployment fails at capability host step

[skillbuilderzone]

We are using the bicep template to deploy in 'uksouth'. It always fails at capabilityHost-configuration-xyz-deployment

  "message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."

I have been able to delete the caphost and then redeploy which succeeded. However, then created agents could not reach private resources.

[fosteramanda]

@skillbuilderzone What template were you using? Could you provide more details on the exact steps you took to deploy it and if you edited the template?

[skillbuilderzone]

@skillbuilderzone What template were you using? Could you provide more details on the exact steps you took to deploy it and if you edited the template?

That will be bicep template. Edited only the uniqueSuffix

Tried again this morning and got the same error at caphost deployment step
capabilityHost-configuration-xxxx-deployment:
"message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.","details":[{"code":"CapabilityHostOperationFailed","message":"Capability host operation failed","details":[],"additionalInfo":[]}]}]}]}]}}

[gukoff]

@skillbuilderzone do you have all necessary providers registered?

I had such a failure provisioning the caphost when I had a missing az provider register --namespace 'Microsoft.App'.

https://learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/virtual-networks#prerequisites

[skillbuilderzone]

@skillbuilderzone do you have all necessary providers registered?

I had such a failure provisioning the caphost when I had a missing az provider register --namespace 'Microsoft.App'.

https://learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/virtual-networks#prerequisites

@gukoff Thanks a lot . I had it registered but still wasn't working. Re-registered it and got past this now

[sebastianczech]

In my case I also had it registered - unregistering and registering Microsoft.App hasn't solved the problem :(

I was trying also with customerSubnet as we discussed in #246 , but I failed with that approach too.

[philippsautter]

I have also registered all of them.
Re-register did not solve the problem for me either. :(

[skillbuilderzone]

In my case I also had it registered - unregistering and registering Microsoft.App hasn't solved the problem :(

I was trying also with customerSubnet as we discussed in #246 , but I failed with that approach too.

@sebastianczech @philippsautter Can you share where exactly you got stuck?

-Try looking for deleted accounts and purge. I think the deleted account stays there for 2 days or something before being permanently deleted
az cognitiveservices account list-deleted

• Check the status of your capabilityHosts
  You can use az rest --method get --url "https://management.azure.com/subscriptions/xxxx/resourceGroups/xxxx/providers/Microsoft.CognitiveServices/accounts/aiservicesxxxx/projects/project?api-version=2025-06-01"

And do the same for Account. It was in Failed state for me. I then deleted both resources and re-created using az rest --method put...

• Try creating the capabilityHost for the Account manually and re-deploying by passing existing resources in the bicep.

[sebastianczech]

In my case I also had it registered - unregistering and registering Microsoft.App hasn't solved the problem :(
I was trying also with customerSubnet as we discussed in #246 , but I failed with that approach too.

@sebastianczech @philippsautter Can you share where exactly you got stuck?

I'm stack with creating AI Foundry with 1 project in VNet injected mode. In fact I'm stack in 2 problems, for which one of them lack of possibility to create capabilityHosts.

In my case configuration of capabilityHosts on account level is different than on project. For account I have "provisioningState": "Succeeded" and null for storageConnections, threadStorageConnections and vectorStoreConnections. For project I have "provisioningState": "Failed" and not null values:

    "storageConnections": [
      "aiservices***storage"
    ],
    "threadStorageConnections": [
      "aiservices***cosmosdb"
    ],
    "vectorStoreConnections": [
      "aiservices***search"
    ]

-Try looking for deleted accounts and purge. I think the deleted account stays there for 2 days or something before being permanently deleted az cognitiveservices account list-deleted

Yes, I was doing that. Moreover I was removing accounts by command az cognitiveservices account purge. Besides that I'm using different names every time.

• Check the status of your capabilityHosts
  You can use az rest --method get --url "https://management.azure.com/subscriptions/xxxx/resourceGroups/xxxx/providers/Microsoft.CognitiveServices/accounts/aiservicesxxxx/projects/project?api-version=2025-06-01"

And do the same for Account. It was in Failed state for me. I then deleted both resources and re-created using az rest --method put...

• Try creating the capabilityHost for the Account manually and re-deploying by passing existing resources in the bicep.

I was also checking that approach - I remove config by delete method, adding new by put , but still it finishes with failed provisioning.

[philippsautter]

The deployment failed at the Capability Host with the error "CapabilityHostOperationFailed".

If i look at the raw error, it shows me the following:

{ "code": "DeploymentFailed", "target": "/subscriptions/XXXXX/resourceGroups/rg-ai-foundry-swe/providers/Microsoft.Resources/deployments/capabilityHost-configuration-XXXX-deployment", "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.", "details": [ { "code": "ResourceDeploymentFailure", "target": "/subscriptions/XXXXX/resourceGroups/rg-ai-foundry-swe/providers/Microsoft.CognitiveServices/accounts/aiservicesXXXX/projects/projectXXXX/capabilityHosts/caphostproj", "message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.", "details": [ { "code": "CapabilityHostOperationFailed", "message": "Capability host operation failed", "details": [], "additionalInfo": [] } ] } ] }

All Resource Provider a registered correctly as shown here: https://learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/virtual-networks#prerequisites.

[philippsautter]

Hello everyone, are there any new findings on this yet?

[denlai-mshk]

@fosteramanda Is there any add-account-capability-host.bicep work like /modules-network-secured/add-project-capability-host.bicep? I was tried to make one but failed. Any can share how to make the caphost on Account level only? Thank you in advance!