[Virtual Networks]: Missing support for `ipamPoolPrefixAllocations` property

Resource Type

Microsoft.Network/virtualNetworks

Api Version

2024-03-01

Issue Type

Missing property(s)

Other Notes

The ipamPoolPrefixAllocations property now exists to support allocation of address spaces from IPAM (see https://learn.microsoft.com/en-us/azure/virtual-network-manager/how-to-manage-ip-addresses-network-manager?tabs=armtemplate)

The API documentation hasn't been updated yet (https://learn.microsoft.com/en-us/azure/templates/microsoft.network/virtualnetworks?pivots=deployment-language-bicep)

This property is valid under properties -> addressSpace for virtualNetworks, and directly under properties for subnets.

Bicep Repro

resource networkManager 'Microsoft.Network/networkManagers@2024-03-01' existing = {
  name: 'NetworkManager'
}

resource ipamPool 'Microsoft.Network/networkManagers/ipamPools@2024-01-01-preview' existing = {
  parent: networkManager
  name: 'CoreNetwork'
}

resource dynamic 'Microsoft.Network/virtualNetworks@2024-03-01' = {
  name: 'dynamic-vnet'
  location: resourceGroup().location
  properties: {
    addressSpace: {
      ipamPoolPrefixAllocations: [
        {
          pool: { id: ipamPool.id }
          numberOfIpAddresses: 256
        }
      ]
    }
  }

  resource defaultSubnet 'subnets' = {
    name: 'default'
    properties: {
      ipamPoolPrefixAllocations: [
        {
          pool: { id: ipamPool.id }
          numberOfIpAddresses: 64
        }
      ]
    }
  }
}

Confirm

• I have read the troubleshooting guide and looked for duplicates.

Start with the Microsoft.Network/virtualNetworks@2024-03-01 type definition and trace how addressSpace and subnet properties are represented. Use the supplied Bicep repro to check both ipamPoolPrefixAllocations locations; done means the repro is accepted with the documented property shape.