Edit

Ops automation using Event Grid

Automation
Event Grid

Solution ideas

This article is a solution idea. If you'd like us to expand the content with more information, such as potential use cases, alternative services, implementation considerations, or pricing guidance, let us know by providing GitHub feedback.

Azure Event Grid can serve as an essential building block in the automation of cloud operations.

Architecture

Architecture diagram that shows the flow of data during the process of automatically tagging a new VM.

Download an SVG file of this architecture.

Dataflow

  1. A user deploys a new resource in Azure. In this case, the resource is a virtual machine (VM).
  2. The deployment creates the VM.
  3. The Azure subscription of the VM emits an event that Event Grid subscribes to.
  4. Event Grid fires an event that the subscriber Automation account receives.
  5. The Automation account reacts to the event by completing a task. For example, Automation applies a tag to the new VM.
  6. Optionally, Azure Logic Apps also consumes the Event Grid event. A logic app reacts to the event, for example by making an entry in an operation tool.

Components

Scenario details

This solution helps you simplify the process of managing resources.

Specifically, Event Grid can consume topics from multiple services in Azure. In this solution, Event Grid uses Azure subscriptions as a source. As a result, when a VM is created, Event Grid is notified. Event Grid can then notify an Automation account.

These events provide a way to automate resource management tasks.

Potential use cases

This solution has many applications. Examples include automating the following tasks:

  • Checking whether service configurations are compliant
  • Inserting metadata into operations tools
  • Tagging VMs
  • Filing work items

Next steps