IPAM Pool referenceID

**Bicep version**
Bicep CLI version 0.38.33 (6bb5d5f859)

**Describe the bug**
I'm trying to deploy a vnet in a different subscription from a Azure Network Manager and its related IPAM Pools and constantly get this error:
_Ipam API call failed with status NotFound with error message Pool with ARM ID not found., please check the parameters and retry._
However I provide the IPAMs ID I get the same issue. I'm able to deploy this vnet in the azure portal.

**To Reproduce**
Have a Azure Network Manager and IPAM pools setup in Subscription A, make a note of the region and add subscription B to its scope.
Deploy vnet to subscription B and the same region:
````
resource anmRg 'Microsoft.Resources/resourceGroups@2025-04-01' existing = {
scope: subscription('7b4e5b72-e47b-4fd3-8d90-2d9567799c99')
name: 'azureNetworkManager-RG'
}

resource ANM 'Microsoft.Network/networkManagers@2024-10-01' existing = {
scope: anmRg
name: 'azureNetworkManager'
}

resource ipamPool 'Microsoft.Network/networkManagers/ipamPools@2024-07-01' existing = {
parent: ANM
name: 'IP-ApplicationPool'
}

resource ANMnetwork 'Microsoft.Network/virtualNetworks@2024-10-01' = {
name: vnetName
location: location
properties: {
addressSpace: {
ipamPoolPrefixAllocations: [
{
numberOfIpAddresses: '64'
pool: {id: ipamPool.id}
}
]
}
subnets: [
for subnet in subnets: {
name: subnetname
properties: {
ipamPoolPrefixAllocations: [
{
pool: {id: ipamPool.id}
numberOfIpAddresses: '32'
}
]
}
}
]
}
}
````

**Additional context**
Different API versions have also been tested.

Start by reproducing the cross-subscription deployment from the issue using the listed Bicep and resource API versions, then compare the behavior with deployment through the Azure portal. Trace the bicep-types-az definitions involved in virtual network IPAM pool prefix allocations; done means identifying the cause of the NotFound response and recording a validated fix or confirmed upstream issue.

Written by the indexing model from the issue text.