You need a single public endpoint that routes requests to multiple backends without provisioning additional infrastructure. Requests to /v1/orders/* must be forwarded to a legacy API in another App Service, and /v1/images/* should be served from a Blob Storage static website. You must hide backend URLs, support simple path rewrites, and keep costs minimal. What should you do?

Azure Functions Proxies provide a simple, cost-effective solution for routing requests to multiple backends from a single public endpoint without provisioning additional infrastructure. By defining proxies.json entries with route templates and backendUri values (which can be stored in app settings for security and flexibility), you can easily hide backend URLs and perform simple path rewrites. This aligns perfectly with the requirements for minimal cost and hiding backend URLs. Azure API Management is more robust but also more expensive and complex than needed for this scenario. Azure Front Door is a global load balancing service, also more complex and costly than required for simple path-based routing within Azure. Implementing custom HTTP-triggered functions would involve significant development effort and maintenance overhead, defeating the purpose of a simple, low-cost solution.