Azure vDiscovery error "Subnets with CIDR equal to the Virtual Network CIDR are not supported" [ Edited ]

[#1]

I'm responsible for Infoblox, but not our Azure subscription, so I'm looking for insight on why we're seeing this particular error for some networks and not others and, more importantly, how do we fix it? It seems that we only get VMs from networks that are smaller than the VPCs, but what if we've allocated someone a range who wants to use all of it?

"Subnets with CIDR equal to the Virtual Network CIDR are not supported"
Has network container, no data
10.252.34.112/28
10.252.171.0/28
10.252.171.16/28
10.252.167.16/28
10.252.180.32/27
10.252.192.0/27

No logged errors
Has network container, no data
10.252.115.0/26
10.252.115.64/26
10.252.115.192/26
10.252.167.32/28
10.252.167.48/28
10.252.167.64/28

P.S. We're running 8.5.4

[#2]

This is the expected behavior if the subnet CIDRs are equal to the VNet CIDRs. vDiscovery maps a VNet CIDR to a network container in the Grid. It is not able to map that same CIDR to a network. Unfortunately, there is no workaround for this in vDiscovery.