PLEASE HELP - Funtion app proxies are greyed out

@Anonymous Thanks for reaching out. Not all languages and operating system combinations support in-portal editing. For more details you can refer to this document.
If you're unable to create a proxy in the portal, you can instead manually create a proxies.json file in the root of your function app project folder.

Not all languages and operating system combinations support in-portal editing. If you're unable to create a proxy in the portal, you can instead manually create a proxies.json file in the root of your function app project folder. To learn more about portal editing support, see Language support details.

In case you are running Function V4 then the proxy is not supported currently, and it will be added in the next few months. For more details you can refer to the discussion here.

Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.

I have it working. You can create a proxies.json (e.g. copy nul proxies.json in the portal's dev console) file at the root of your project and add the proxy object manually. Then, with the 'AzureWebJobsFeatureFlags' flag, the proxy will run, even though this potal button never un-greyed for me.

• https://learn.microsoft.com/en-us/azure/azure-functions/legacy-proxies#re-enable-proxies-in-functions-v4x
• https://stackoverflow.com/questions/75002689/azure-function-proxy-that-works-locally-and-on-azure

Proxies are ONLY greyed out because the App is running.
Go to your Function App, then click on STOP, this will stop the instance, it will reload the pane, then Proxies will be available :)