Azure deployment fails

[robi26]

Hi,
I try to deploy kernel-memory to azure using bicep. However, I get the following error:
The subnet '/providers/Microsoft.Network/virtualNetworks/t-vne-gptbuddykm-01/subnets/infrastructure-subnet'
is already used by environment
'/providers/Microsoft.App/managedEnvironments/t-cae-gptbuddykm-01'.
The subnet must not already be in use by any
other environment or Azure service. (Code: ManagedEnvironmentSubnetInUse)

There are no connected devices in the vnet to the infrastructure-subnet.
Any help is highly appreciated.
Thanks.
Cheers,
Stephan

[dluc]

@cherchyk FYI

[cherchyk]

As you build your network in Azure, ensure nonoverlapping address spaces. Make sure your virtual network address space (CIDR block) doesn't overlap with your organization's other network ranges.

This is why you have an availability to chance address space in deployment UI.

https://learn.microsoft.com/en-us/azure/virtual-network/concepts-and-best-practices#best-practices
@robi26

[robi26]

Ok, I thought that all virtual networks are inside the boundaries of a resource group and not the whole tenant.

[cherchyk]

In Azure, network boundaries should not overlap within the Subscription

[robi26]

Hm, that's strange. I still get the same error. I changed the IP range and checked my subscription and that's the only vnet that is deployed.
My config
infrastructure-subnet
192.168.0.0/23

app-gateway-subnet
192.168.2.0/24

private-endpoint-subnet
192.168.3.0/24

[cherchyk]

there are four parameters to define address space. Show all please

[robi26]

Sorry, forgot, here the config from my bicep
param VirtualNetworkAddressSpace string = '192.168.0.0/16'
param InfrastructureSubnetAddressRange string = '192.168.0.0/23'
param ApplicationGatewaySubnetAddressRange string = '192.168.2.0/24'
param PrivateEndpointSubnetAddressRange string = '192.168.3.0/24'

[robi26]

after moving to a new subscription it works now...