How to deploy aspire app using azd in a particular VNET

[faisalriazz]

Hi All
I want to deploy an aspire app to my own VNET using azd so that i can control it and add application gateway , web application firewall and other other services.
Currently when deployed using azd i do not have control over the VNET.
is it possible ? or there is any other solution to deploy aspire app so that i can have control over it

[davidfowl]

is it possible ? or there is any other solution to deploy aspire app so that i can have control over it

There's nothing built in to help you here as yet. If you need more control over the deployment you'll need to use azd infra synth and you'll have to mutate the generated bicep.

[faisalriazz]

@davidfowl Thanks for your reply.
Is there any recommended procedure to follow for example a microsoft document.
Or If someone has achieved it and shared in aspire community as a reference.
It would be of great help.

[davidfowl]

Do you have experience with virtual networks and bicep?

[faisalriazz]

yes ,basic knowledge , can use template from

[https://azure.github.io/bicep/] to modify as per my need

[dmi-harlow]

@faisalriazz, I had a similar requirement and found that deploying an Aspire application to an existing vnet is actually pretty straightforward. Here is an excerpt from the default resources.bicep generated by azd infra synth with the new code added between the comments:

resource containerAppEnvironment 'Microsoft.App/managedEnvironments@2024-02-02-preview' = {
  name: 'cae-${resourceToken}'
  location: location
  properties: {
    workloadProfiles: [{
      workloadProfileType: 'Consumption'
      name: 'consumption'
    }]
    appLogsConfiguration: {
      destination: 'log-analytics'
      logAnalyticsConfiguration: {
        customerId: logAnalyticsWorkspace.properties.customerId
        sharedKey: logAnalyticsWorkspace.listKeys().primarySharedKey
      }
    }

    //---- BEGIN VNET INTEGRATION ----//
    vnetConfiguration: {
      internal: true
      infrastructureSubnetId: resourceId('yourVnetResourceGroupName', 'Microsoft.Network/virtualNetworks/subnets', 'yourVnetName', 'yourSubnetName')
    }
    publicNetworkAccess: 'Disabled'
    //---- END VNET INTEGRATION ----//

  }
  tags: tags

  resource aspireDashboard 'dotNetComponents' = {
    name: 'aspire-dashboard'
    properties: {
      componentType: 'AspireDashboard'
    }
  }
}

Note that the subnet used must be empty and delegated to Microsoft.App/environments.

After deploying this I was able to add a Private Endpoint to the CAE and access container apps with external ingress over the Private Endpoint.

[faisalriazz]

@dmi-harlow Thanks for taking time to reply.

• deploying aspire project using azd creates resource group.
• My question is where should i create VNET ?
• is it possible to create a resource group with VNET before initializing azd and then assigning this resource group to my aspire app.
• I am bit confused here , please guide me here

[dmi-harlow]

Happy to help.

1. Your Virtual Network does not have to be in the same Resource Group as your Aspire app.
2. You can azd deploy to an existing Resource Group where you have already created a Virtual Network.

[faisalriazz]

Thanks, Will try it out and keep you posted for help.
Thanks