[Chore]: Add support for Azure AI Foundry Capability Hosts (optional deployment, CosmosDB thread store, Bicep integration) #73
Description
Area
Infrastructure (Bicep/infra)
Chore Type
Other
Description
Add support for Azure AI Foundry Capability Hosts, following https://learn.microsoft.com/en-us/azure/ai-foundry/agents/concepts/capability-hosts?view=foundry. This should include:
- Optional deployment of capability hosts
- CosmosDB used as Thread/Conversation store (new resource to be deployed)
- Configuration of capability host connections
- Implement via Bicep modules, since AVM does not currently support capabilityHosts for Microsoft.CognitiveServices/accounts
AI Search and Azure Storage are already optionally deployed by the project, but capabilityHosts require CosmosDB for storage. Use Bicep for infrastructure changes.
Justification
Enabling support for capability hosts allows solutions to take advantage of new features in Azure AI Foundry. It modernizes the accelerator, aligns with official Azure guidance, and maintains parity with documented architecture patterns. This will unblock additional agent and capability scenarios.
Acceptance Criteria
- Bicep modules add capability host deployment as an optional feature
- CosmosDB thread/conversation store deployed optionally alongside capability hosts
- Configuration for capability host connections available and documented
- Documentation updated with guidance on deploying and connecting capability hosts
- Uses Bicep for all new infrastructure (not AVM, which lacks capabilityHost support)
- Existing optional deployments for AI Search and Storage remain unaffected
- Solution tested with new capability hosts enabled
- CI/CD pipelines updated as needed
Priority
Medium - Should be addressed in next few releases
Additional Context
See official Azure documentation for capability hosts: https://learn.microsoft.com/en-us/azure/ai-foundry/agents/concepts/capability-hosts?view=foundry