Event Grid Media/IoT Event to Workflow

Overview

This event-driven flow bridges Azure platform events into business workflows using Azure Event Grid. It subscribes (via a webhook Event Grid subscription) to Azure service events - Media Services job finished/errored, IoT Hub device telemetry/connection, and Azure Maps geofence - classifies each event, writes a full audit record to Dataverse, and notifies a Microsoft Teams channel, escalating critical events to a high-visibility alert.

Why it matters: platform events normally stay inside Azure. Routing them into Power Automate connects infrastructure signals to the people and processes that must react - publishing finished media, investigating device anomalies, or dispatching field tasks - while keeping a durable, queryable history of everything that happened.

Ships Off (demo).

Use Case

An Azure-native solution emits platform events (media processing, IoT device signals, mapping geofences) that need to drive business actions and be auditable. This flow gives event-driven, low-latency reaction instead of polling: every event is categorized (Media / IoT / Maps / Other), logged to Dataverse with a correlation id, and surfaced in Teams - with critical event types raising an on-call alert.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Azure Event Grid	shared_azureeventgrid	CreateSubscription (trigger)
Microsoft Dataverse	shared_commondataserviceforapps	CreateRecord
Microsoft Teams	shared_teams	PostMessageToConversation

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Target a specific resource

Set the Event Grid resource type and point the topic at a Media Services account, IoT Hub, or Maps account resource id; adjust includedEventTypes to that resource's events.

Tune criticality

Edit the critical event types list to control which event types escalate to the alert branch (no flow edit needed).

IoT routing

Extend the critical branch to map a device id to an owner and dispatch a task.

Media publish

In the Media branch, push finished assets to a CDN or site.

Geofence dispatch

In the Maps branch, look up the nearest technician and create a field task.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@if(startsWith(coalesce(triggerOutputs()?['body/eventType'],''),'Microsoft.Media'),'Media', if(startsWith(coalesce(triggerOutputs()?['body/eventType'],''),'Microsoft.Devices'),'IoT', if(startsWith(coalesce(triggerOutputs()?['body/eventType'],''),'Microsoft.Maps'),'Maps','Other')))

contains(toLower(variables('varCriticalEventTypes')), toLower(coalesce(triggerOutputs()?['body/eventType'],'__none__')))

@{string(triggerOutputs()?['body'])}

Customize & download