Why does your timer trigger Azure Function run at unforeseen times? Has it ever happened that your timer triggered Azure Function was running on unforeseen times? We had it for two functions, and could not immediately find out where or why this was triggered more than once an hour.
Just a quick article about how you can let your Azure Function runtime know there was a problem during the execution. This is important when you are for example working with queue triggered functions. The default method to let your Azure Function know it has finished is the context.done() method. When you use the method like this: context.
We all get a lot of emails every day. Did you know that some of these emails are being tracked by others? There are various kinds of email trackers available, most of them work by inserting hidden images and/or changing the links in the mail by a tracking prefix. This allows them to see when and how many times you opened your email and which of the links you clicked from the mail.
A couple of weeks ago I wrote a simple Office add-in which just added a custom add-in command. An add-in command only requires that you specify an URL to a page / HTML file to make it work. As it would be overkill to create a website for just that one file, I thought about using an HTTPTrigger Azure Function to return me the necessary HTML for my command.
These days I use Azure Functions quite a lot for automating things. Since the general availability of Azure Functions which was announcement back in November 2016, they are becoming even more popular and are being used for various kinds of things. Even the local development process of Azure Functions got a lot better.
Azure functions are available for a while now. Their purpose is to have an event-driven compute without maintaining any server or applications. On my Azure environment, I have various of these small functions running. They all do different things like keeping my Azure search index up to date, sending notifications about my NPM packages, etc.