Announcing Public Preview of Azure API Management Basic v2 and Standard v2 Tiers

In the current apim architecutre itself there is one problem( i dont know its a bug or UI issue) related to a property called `publicNetworkAccess` 

One can make the publicnetworkaccess to disable only if they create a private endpoint ( remember the private endpoint is a new feature on apim) Vnet injection was there for long time. My APIM is deployed inside a vnet (internal mode) which means its not publicly accessable - Hence i should ideally see the property value for publicnetworkaccess as false or disable. But we cannot do that if you apim is in vnet. 

The confliciting statement here are 

1. Disabling all publicNetworkAccess for service, is not supported if the service does not atleast one approved Private Endpoint Connections
2. To enable private endpoints, the API Management instance can't already be configured with an external or internal

It's a kind of deadlock scenario for me to disable public access. Since the private endpoint is a new feature that got introduced recently. But my APIM got deployed with Vnet Injection (internal) mode before that. So now I can't able to make my APIM truely private access. Because I cannot create private endpoints due to that I cannot switch off the public access. But ms claims that my apim is private however the property is saying otherwise

Already raised a https://github.com/Azure/azure-rest-api-specs/issues/24947