It's great to see a more accessible model for connecting API Management to virtual networks when that's the only feature driving Premium SKU adoption. Speeding up network configuration changes is fantastic as well. I'm anxious to adopt the v2 SKU in a future deployment.
I will say that I'm hopeful for better options for virtual network connectivity in the future. I know that most reference architectures accomplish combined public and private inbound connectivity through the use of Application Gateway and APIM in internal mode, but it still feels clumsy. I know there's already a lot under the hood of an APIM deployment unit already today, but it would be great if we could simplify managing this scenario where APIM is the public ingress point for communications to a wider Azure private resource deployment that also consumes that same gateway.
Still, this a very welcome change for smaller deployments that don't require centralized policy management with global replication.