Azure Function Proxy (AZP) was meant for helping you to re-write your multitude of API URLs in a uniform fashion by the design of it, however it can be used for a rather unorthodox use case just as well.
Imagine you have two web resources you would like to get under one URL, with two path extensions – mapped to these web resources. As we live in a modern, mobile first world these web resources happen to be in AMP format.
So these two resources are a) one page from my pet blog log2talk.com as well as b) one from digiday.com. Now what I did with the help of AZP: create a new Proxy endpoint with route template and mapped the content origins to sub-paths of my Function endpoint. (Sounds a lot more complex than it really is, see screen caps below.)
And presto, your AZP will expose those resources to any path element you wish.
There are some caveats, however.