Working with Existing Resources and Multiple Subscriptions in Azure

[NapalmCodes]

I am working with the Aspire deployment model for the first time and have ran into some issues:

1. I seem to need to modify the generated bicep no matter what I do (organization policies on resource naming and tagging requirements). Some of this I can do via an infrastructure resolver but it's not perfect. Renaming the resource group seems difficult to do without bicep changes as well as other opinionated resources due to hard coded prefixes (log analytics workspaces, managed identities, etc.).
2. I cannot figure out how to utilize resources like a container registry in other subscriptions (than the subscription being deployed to). Is there any support for this?
3. Also is anything documented how to use an existing container app environment to deploy to vs creating a new one? I found .WithComputeEnvironment and PublishAsContainerApp but cannot seem to figure this out.

Thanks in advance. I can provide more details if needed.

[davidfowl]

I seem to need to modify the generated bicep no matter what I do (organization policies on resource naming and tagging requirements). Some of this I can do via an infrastructure resolver but it's not perfect. Renaming the resource group seems difficult to do without bicep changes as well as other opinionated resources due to hard coded prefixes (log analytics workspaces, managed identities, etc.).

An InfrastructureResolver is the way to go if you want to make cross cutting changes. There are gaps today because azd still creates the top level resource group, but everything else should be mutable via the InfrastructureResolver or https://learn.microsoft.com/en-us/dotnet/aspire/azure/customize-azure-resources.

I cannot figure out how to utilize resources like a container registry in other subscriptions (than the subscription being deployed to). Is there any support for this?

Existing resources in other subscriptions are not supported at the moment #7514 (cc @captainsafia)

Also is anything documented how to use an existing container app environment to deploy to vs creating a new one? I found .WithComputeEnvironment and PublishAsContainerApp but cannot seem to figure this out.

#9094

PS: You can always build custom resources (or use AI to do so) that avoid the built-ins but we're pretty close to making some of these scenairos work end to end.

cc @eerhardt

[NapalmCodes]

Thank you for the response. What do you mean by custom resources exactly? I assume you are meaning wrappers around the official aspire components to add these customizations? Obviously not ideal if we are close to an out-of-box solution.