Microsoft recently announced the general availability of the following new price tiers: Azure API management, Basic v2, and Standard v2. It provides scalability and flexibility to support a variety of development projects, from small applications to enterprise-level applications.
Azure API Management is Microsoft’s API gateway product in the cloud, offering customers different tiers based on workload and functionality. The GA release of the new Basic and Standard tiers follows last year’s public preview.
The v2 price point represents an evolution in Microsoft’s approach to API management.The company has an existing classic price range While introducing features that align with modern development practices. These tiers complement the existing Developer, Basic, Standard, and Premium tiers, giving users a variety of options to match the size and complexity of their projects.
The Basic v2 and Standard v2 tiers have several important features.
- Rapid deployment and scalability: These tiers allow you to quickly set up and configure API Management instances, a critical element of agile development cycles. Developers can efficiently scale API management resources to accommodate different workloads.
- Simplified network options: In particular, Standard v2 provides improved support for outbound connectivity to network-isolated backends. This networking simplification facilitates secure and efficient integration with backend services. This is essential for applications that require high data security.
- Enhanced security with VNet integration: VNet integration This is a highlight of the v2 layer and allows for more secure API backend connections. This feature is essential for applications where secure private connectivity is paramount. Previously, the Premium tier offered comprehensive VNet support, and Standard v2 expands on similar capabilities, but with some additional features, such as the requirement that the API Management gateway and developer portal remain publicly accessible. There are restrictions.
Significant improvements in Standard v2. It was not available in v1 due to missing VNet integration.
Also, when asking questions, Thun VanhoeteAs an Azure MVP, he responded about the new tier:
Thanks to a new tier, Azure API Management customers can now benefit from premium networking at a lower price.
Azure API management layer overview (Source: Tech Community blog post)
An important aspect of the Azure API Management layer is its focus on hardening networking and security.
- Private endpoint for inbound connections: This feature supports secure client connections in API management. This is an important consideration for developers who want to minimize their exposure to the public Internet.
- VNet injection: Available in developer and premium tiers, this service can be deployed in virtual networks. This helps you set public or private receive mode depending on your project’s security needs.
- Standard v2 VNet integration: Unlike VNet injection, VNet integration allows the API Management service to access the service through the private IP of the connected VNet. This feature is very important for projects that require secure access to backend services within a VNet.
The new v2 tier, specifically Standard v2, is designed for production environments. Supports backends isolated from the network and provides scalability. This development is important for teams looking for flexible and scalable solutions to manage APIs securely and efficiently.
Massimo CrippaCodit’s Azure MVP told InfoQ:
By leveraging shared infrastructure, the V2 tier brings more flexibility to the table and provides access to several cloud network layouts at a competitive pricing model.
However, while these tiers extend the services of Microsoft Azure, Limitations. For example, certain features such as API Management service configuration using Git, backup and restore functionality, and built-in analytics are not supported in the v2 tier. Developers should consider these factors when choosing the appropriate tier for their project.
InfoQ asked Fernando MejiaGiven that you cannot currently migrate existing API Management instances to new v2 tier instances, what plans do you have in place to support such migrations in the future? I’ll explain what’s going on.
As a final milestone after releasing the premium v2 preview and GA and improving parity between the v1 and v2 tiers, we plan to invest in migrating from the v1 tier to the v2 tier.
Additionally, InfoQ asked about the introduction of v2 pricing tiers and its new features. Some features available in the v1 tier are not supported in the v2 tier. How will the product team address the absence of features such as API Management service configuration using Git, API Management instance backup and restore, and enabling Azure DDoS Protection on the v2 tier? Mejia replied: Ta.
For missing features, here are some strategies:
- Some features will be deprecated across all tiers, such as git repositories, direct management APIs, and legacy built-in analytics. Two of them have already been released.
- We are working on providing parity for the remaining features. We are prioritizing the following features: Minor missing features (capacity metrics, tracing), Azs, multi-region, self-hosted gateway, and workspaces.
Finally, the new hierarchy is available at: Various Azure regionsprice details, price page.
