This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 76%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EE%3C/text%3E%3C/svg%3E)
Hi
I have a number of Azure Functions which i want to make public and and primarily am using APIM for allow me to configure them under 1 custom domain, to make them more user friendly.
However I am struggle to make the user friendly because of how the are configured by default.
So i add an api to the apim but finding the function app and adding it, in doing so it adds an API URL suffix by default and this is required as soon as you have multiple functions, as soon as you do this, all the api's endpoints are configured as :
<api-domain/<Function App name as API URL suffix>/<Function Route>
this makes them ugly and no very intuative.
All my apps have routes which make the route unique to the endpoints, so in theory all i have to do is find a way to not use the API URL suffix and my apis will be golden.
However if I use a url rewrite policy to remove the API URL suffix i get a 404 not found.
How do i make user friendly endpoints? is there a way to use the function apps routes as the API URL suffix, these do have dynamic values which need to be taken into consideration. (happy to use a different service to apim if needed)
Hi @EnenDaveyBoy Greetings! Thank you for posting the question on this forum.
Just wondering if you have looked into enabling proxy on your Azure functions end which might simplify the URL path. Even though this feature in disabled in 4.x versions of Azure functions, you can enable it by setting a flag AzureWebJobsFeatureFlags in the application setting and assign it a value EnableProxies.
Please refer the article Re-enable proxies in Functions v4.x for more details on this. Here is an article Customize an HTTP endpoint in Azure Functions which provides you the steps to create and test a proxy URL.
Once you create a proxy, test by importing the Azure function to a APIM instance and see if the function App now responds with the proxy URL.
Hope this helps. Let us know if you need any additional assistance.
having a quick look i don't think this will work, as i am hoping for cookie support using apim as well which i don't think will work with a proxy. I also don't think it will work because this effects the functions apps url, and the issue is the way the apim configures urls, i can see how the proxy changes that or fixes the problem.
to get this to work as i want, you simply don't import the API as a function app, and you create one app of blank http, then you manually add all the endpoints for each method for the azure functions, more work but so much cleaner, although the url rewrites can be a little weird