Azure Functions
Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in other Azure services, SaaS products, and on-premises systems. With Azure Functions, your applications scale based on demand and you pay only for the resources you consume. Azure Functions provides an intuitive, browser-based user interface allowing you to create scheduled or triggered pieces of code implemented in a variety of programming languages.
-
Access the management console for Azure Functions in an App Service Environment deployed via ILB
As it stands, Azure Functions and Web Jobs deployed in an intranet-based App Service Environment cannot be managed via the Azure portal unless the user is connected to the internal network or VPN. It appears that the advanced management console code is deployed into the App Service Environment for these services,, as the SCM host name is provisioned on the custom domain. This makes remote management difficult especially for enterprise customers.
7 votes -
Application Insights integration with proxies
Currently AI integration is only working for functions, not for function proxies. Therefore 50x and 40x errors from backend services cannot be captured with the likes of Application Insights. Diagnostics of function proxies falls short, Azure Monitor can only be used to capture 50x errors.
1 voteProxies are currently supported, and emit request information to App Insights.
If this is not working, and you do not see proxies requests in the requests view in your App Insights subscription, please open a github bug, as this would be a regression.
Thanks for your feedback!
Alex
Functions team -
Pass HTTP Method as a variable to be used in the backend URL
In case we have several functions or external resources to handle get, post, put, delete, etc for a single entity. It would be good to be able to capture the HTTP method as a variable and use it in the backend URL, for example:
https://xxxxx/{HTTPMETHOD}ToDo
with this, we can have a single proxy configuration to handle:
https://xxxxx/GetToDo
https://xxxxx/PostToDo
https://xxxxx/DeleteToDo1 voteWe now support this using the {request.method} binding syntax.
Please see the documentation for more details:
https://docs.microsoft.com/en-us/azure/azure-functions/functions-proxies#use-variables
- Don't see your idea?