Support for consumption function apps that are not publicly addressable

Today to get consumption based pricing for functions, you must create function apps that are publicly addressable over HTTP and there is no way to avoid this. If you workload doesn't involve HTTP triggers and you're managing the function app through ARM, the HTTP endpoint exposes unnecessary surface area.

Consider implementing support to remove the public HTTP endpoint. This could be achieved without any modifications to the functions host itself, if the consumption infrastructure supported "unregistering" a given function app from the frontends.