Blog Post

Azure Integration Services Blog
2 MIN READ

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

feranto's avatar
feranto
Brass Contributor
Oct 10, 2023

We are excited to announce the launch of the public preview of our newest Azure API Management tiers – Basic v2 and Standard v2. Thousands of the world’s largest enterprises trust Azure API Management to implement, secure, and scale their API initiatives. Our customers are at the center of our innovation at Microsoft, and their feedback guides our investments. The new tiers answer popular customer requests, offer quality-of-service improvements, and allow customers of any size to get started with API Management, adding capabilities and scale as their API programs grow.

 

Key capabilities and quality of service improvements

 

  • Faster deployment and scaling. Deploy a new, production-ready API Management service instance in minutes. Scale it out or in quickly to meet the ever-evolving needs of your API management workloads.
  • Private networking. Standard v2 tier now supports VNet Integration, allowing outbound traffic can be restricted to a single connected VNet
  • Higher scale. Basic v2 and Standard v2 tiers support up to 10 scale units, a 5X and 2.5X improvement over Basic and Standard tiers respectively.

 

Preview limitations

 

The Basic v2 and Standard v2 tiers public preview is available only in selected public regions for newly created service instances. Upgrades from the current tiers aren’t supported. During the preview some features found in the current tiers will not be present the new tiers.

For pricing information and regional availability please visit API Management pricing page.

 

Learn more

 

Frequently asked questions

 

Q: Can I migrate my existing API Management service instance to the Basic v2 or Standard v2 tier?

A: No, you can't migrate an existing Consumption, Developer, Basic, Standard, or Premium tier API Management service instance to Basic v2 or Standard v2 tier. Currently the new tiers are available for newly created service instances only. Migration path will be announced separately.

 

Q: What's the relationship between the stv2 compute platform and the Basic v2 and Standard v2 tiers?

A: They're not related. stv2 is a compute platform version of the Developer, Basic, Standard, and Premium tier service instances. stv2 is a successor to stv1 platform scheduled for retirement in 2024.

 

Q: Will I still be able to provision Basic or Standard tier services?

A: Yes, there are no changes to the Basic or Standard tiers.

 

Q: What is the difference between VNet integration in Standard v2 tier and VNet support in the Premium tier?

A: Standard v2 service instance can be integrated with a VNet to provide secure access to the backends residing there. A Standard v2 service instance integrated with a VNet will have a public IP address which will have to be secured separately, via Private Link, if necessary. Premium tier supports a fully private integration with a VNet (often referred to as injection into VNet) without exposing a public IP address.

 

Q: Can I deploy any of the new SKUs entirely in my VNet?

A: No, such a deployment is only supported in the Premium tier.

Updated Nov 09, 2023
Version 2.0
azure
integration

13 Comments

Show More
  • Jayendran's avatar
    Jayendran
    MCT
    Oct 11, 2023

    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 

  • LSuarez5280's avatar
    LSuarez5280
    Copper Contributor
    Oct 10, 2023

    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.