Allow multi-region deployment at Standard Tier
Standard Tier currently does not allow for multi-region deployment. Premium transaction levels are so much higher and more costly, when there may only be need for a very small deployment in some geos, but need to be co-located with services already deployed to those geos. Allow for more flexibility in the deployment model, so a user can tune what they need in each different Geo (Premium in US, Standard in EU, Basic/Dev in AU).
+1 for consumption. Would love to deploy an Azure Function in multiple regions behind a multi-region APIM Consumption. Multi-region Functions can be accomplished using Traffic Manager today; however, that solution doesn't work well with APIM.
Should apply this to the consumption plan as well.
Michael Bonetti commented
Features such as Virtual Network support and multi-region deployments are valuable in low throughput business cases that can't justify paying the premium cost. A pay-as-you-go solution for throughput would be a nice option to allow low throughput business cases to take advantage of the features available in premium.
[Deleted User] commented
This should be available in all tiers. We must have this feature or we are going with Mulesoft!
Siddharth Mathur commented
Multi-region deployment should start on the Basic tier with 2 geos, and increase incrementally to unlimited geos on the highest plan.