An Azure service that provides an event-driven serverless compute platform.
Hi @Turic Mario
Thank you for reaching out to Microsoft Q&A.
Posting this as an answer to help other community members.
As discussed on teams, Glad the issue is resolved.
The issue was resolved by you, and you also followed the steps mentioned by the backend team below:
Recommendations for Customer
Option 1 (Recommended): Fix settings on PremiumV3
Set both App Settings simultaneously, then restart:
FUNCTIONS_WORKER_RUNTIME = custom AzureFunctionsJobHost__configurationProfile = mcp-custom-handler No Feature Flag needed. HttpWorkerOptionsSetup does not check Feature Flags.
Option 2: Switch to MCP Extension approach
Use the Azure Functions MCP Extension with McpToolTrigger bindings:
Python sample: remote-mcp-functions-python Official docs: aka.ms/functions-mcp FUNCTIONS_WORKER_RUNTIME stays as python, no configurationProfile needed Lower risk of configuration mismatch
Option 3: Deploy on Flex Consumption as designed
Run azd up from the sample repo to provision FC1 automatically. The Bicep template includes VNet integration.
If the resolution was helpful, kindly take a moment to click on
and click on Yes for was this answer helpful. And, if you have any further query do let us know.