We are revising the APIs used for detecting enablement status to give the portal a single source of truth. This should address this issue.Anonymous commented
I ran into this problem recently, we are very lucky the function didn’t pose a critical problem while running in a “disabled” state. The functionality here is counter intuitive and only discoverable through direct experience or happening across the documentation (https://docs.microsoft.com/en-us/azure/azure-functions/disable-function#functions-1x---c-class-libraries ).
A warning in the Azure portal when trying to disable a Version ~1 C# function would have been enough to avoid the problemAnonymous supported this idea ·