Discussed in #85
Originally posted by JFolberth February 19, 2026
Feature Description
Support having Cosmos, ACA, and ACR in separate resource groups as opposed to all in one. This will allow for easier customer adoption in scenarios they have their own existing CosmosDB and associate architecture.
Problem or Use Case
Currently the MCP toolkit assumes that Cosmos, ACR, and ACA are in the same resource groups. Most large customers will have these in three separate resource groups due to security, scalability, and high availability.
Proposed Solution
Describe how you envision this feature working. Include:
Think there are couple pieces.
First there should be a parameter for Cosmos Resource Group Name and ACR Resource Group Name. From there the bicep would need to accommodate these parameters and leverage the existing function. Additionally the RBAC role assignment piece will need to verify if the deployed user has the appropriate access over the resource groups.
Example Usage
If a customer has their won CosmsoDB in a separate resource groups they'd like to expose via MCP. Really these are two features. One to support a separate RG for Cosmos and one for a separate RG for ACR.
# Example command or code
Alternatives Considered
Have you considered any alternative solutions or workarounds? Describe them here.
Benefits
Who would benefit from this feature?
Additional Context
Add any other context, screenshots, mockups, or examples about the feature request here.
Priority
How important is this feature to you?
Checklist:
Discussed in #85
Originally posted by JFolberth February 19, 2026
Feature Description
Support having Cosmos, ACA, and ACR in separate resource groups as opposed to all in one. This will allow for easier customer adoption in scenarios they have their own existing CosmosDB and associate architecture.
Problem or Use Case
Currently the MCP toolkit assumes that Cosmos, ACR, and ACA are in the same resource groups. Most large customers will have these in three separate resource groups due to security, scalability, and high availability.
Proposed Solution
Describe how you envision this feature working. Include:
Think there are couple pieces.
First there should be a parameter for Cosmos Resource Group Name and ACR Resource Group Name. From there the bicep would need to accommodate these parameters and leverage the existing function. Additionally the RBAC role assignment piece will need to verify if the deployed user has the appropriate access over the resource groups.
Example Usage
If a customer has their won CosmsoDB in a separate resource groups they'd like to expose via MCP. Really these are two features. One to support a separate RG for Cosmos and one for a separate RG for ACR.
# Example command or codeAlternatives Considered
Have you considered any alternative solutions or workarounds? Describe them here.
Benefits
Who would benefit from this feature?
Additional Context
Add any other context, screenshots, mockups, or examples about the feature request here.
Priority
How important is this feature to you?
Checklist: