Geo-availability integration a la CosmosDB for Consumption Plan
For Functions in a Consumption Plan, it's a bit arduous to get them to be geo-distributed (have to set up deployment to all the various regions you want to support, add APIM/Traffic Manager to handle). It would be super awesome if Functions had a setup like CosmosDB where you deployed them once, then "lit up" the geos you want the code replicated to. Then, not too much different than the request in #214 , an "invisible" Traffic Manager service could be provided on the endpoint for the Function to hit the nearest geo to the end user.
This is a great feature ask though we have no concrete plans on this right now.
We will check back to see if there is more community support.