Can I start a runbook from storage queue?

Ano Acco 191 Reputation points

Azure Functions integrate beautifully with Azure Storage Queue:

Can Runbooks be used in a similar way as an alternative?
I haven't found much in terms of triggers. Could Watchers be a solution? What about Event Grid? From documentation it seems like it could do the job but with extra steps.

Azure Automation
Azure Automation
An Azure service that is used to automate, configure, and install updates across hybrid environments.
1,111 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Ano Acco 191 Reputation points

    Nvm, I found an answer:

    Yes, it is possible to trigger Azure Runbooks from a Storage Queue by using an Azure Function as a bridge between the Storage Queue and the Runbook.

    You create an Azure Function that will read the messages from the Storage Queue and trigger the Runbook.

    So, in summary, it is impossible to directly start Runbook from a Queue.

    1 person found this answer helpful.
    0 comments No comments

  2. Prrudram-MSFT 21,881 Reputation points

    Hello @Ano Acco

    Thank you for reaching out to the Microsoft Q&A platform.

    Yes, Azure Functions can integrate with Azure Storage Queue using the Azure Queue storage trigger and output binding.
    The Azure Queue storage trigger allows you to run an Azure Function as Azure Queue storage data changes.

    Watchers in Azure Automation are a type of runbook that can be used to monitor the output of other runbooks and act based on the results. Watchers can be used to send notifications, such as email notifications, when a runbook completes or fails.

    Event Grid is a fully managed event routing service that allows you to send and receive events from various sources and act on those events. You can use Event Grid to trigger runbooks in Azure Automation in response to events from various sources, such as Azure services, custom applications, and IoT devices.

    Event Grid requires extra steps to set up, but it provides a more flexible and scalable solution for triggering runbooks in response to events.

    You can find more information on these topics in the Azure Automation documentation:

    If this does answer your question, please accept the answer, and give a thumbs up as a token of appreciation.