An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.
Hello Gagan B R
NOTE: When a service or feature is in preview, some functionalities may be limited, unstable, or subject to change. Certain constraints or unsupported configurations can lead to unexpected errors.
This behavior is documented under preview terms and may change when Basic v2 becomes generally available.
- Basic v2 SKU is still in Preview The Basic v2 tier is designed for low-traffic workloads and is currently in public preview. It offers limited features compared to Standard v2 (e.g., no autoscaling, fewer backend pools) and is intended for cost-sensitive scenarios.
- N/A Pricing on Azure Pricing Page: The N/A indicated for the Basic v2 pricing on the pricing page can suggest that this SKU may not be fully supported in the New Zealand North region, hence leading to confusion in billing.
- Intended Behavior in Unsupported Regions: If the Basic v2 Preview SKU isn't fully supported in a particular region, it could very well be that billing under the Standard v2 meters is the workaround in place to accommodate users until full functionality is achieved.
Is it expected that Basic v2 in New Zealand North is billed using Standard v2 meters?
- Yes. In regions where Basic v2 billing is not available, Azure defaults to Standard v2 billing.
Does N/A pricing indicate Basic v2 billing is not available in that region?
- Correct. N/A means the region does not support Basic v2 pricing yet.
Is billing under Standard v2 meters the intended behavior for unsupported regions?
- Yes. This is the fallback mechanism during the preview phase.
I hope this has been helpful!
If above is unclear and/or you are unsure about something add a comment below.
Please click Accept Answer and upvote if the above was helpful.
Thanks.