99 out of 100 times if your Azure Function is having issues running in Azure it will be because of configuration settings, be they missing or containing empty values – OK, I admit, may be a bit of an exaggeration, but it is often the contributor to the problem.
Prior to my discovery today, you would normally receive an error message inside the portal, that included an extremely UNHELPFUL 😢 error message. It often took several minutes or hours 🕒 to figure out exactly that the issue was with the configuration settings.
I say all that, because today I deployed an Azure Function and left one of my configuration settings empty – which is not uncommon for me, failed to initialize it in my Azure DevOps release pipeline – and as expected, my function failed to start and I received an error message.
But …
This time the error message was way more informative, told me the exactly where my problem was.
I was able to address the issue quickly and was back up and running in no time!
Thank you 👏 Azure Functions team!