Editja

Ixxerja permezz ta’

What is Azure Event Grid?

  • Artiklu

Azure Event Grid is a highly scalable, fully managed Pub Sub message distribution service that offers flexible message consumption patterns using the MQTT and HTTP protocols. With Azure Event Grid, you can build data pipelines with device data, integrate applications, and build event-driven serverless architectures. Event Grid enables clients to publish and subscribe to messages over the MQTT v3.1.1 and v5.0 protocols to support Internet of Things (IoT) solutions. Through HTTP, Event Grid enables you to build event-driven solutions where a publisher service announces its system state changes (events) to subscriber applications. Event Grid can be configured to send events to subscribers (push delivery) or subscribers can connect to Event Grid to read events (pull delivery). Event Grid supports CloudEvents 1.0 specification to provide interoperability across systems.

High-level diagram of Event Grid that shows publishers and subscribers using MQTT and HTTP protocols.

Azure Event Grid is a generally available service deployed across availability zones in all regions that support them. For a list of regions supported by Event Grid, see Products available by region.

Overview

Azure Event Grid is used at different stages of data pipelines to achieve a diverse set of integration goals.

MQTT messaging. IoT devices and applications can communicate with each other over MQTT. Event Grid can also be used to route MQTT messages to Azure services or custom endpoints for further data analysis, visualization, or storage. This integration with Azure services enables you to build data pipelines that start with data ingestion from your IoT devices.

Data distribution using push and pull delivery modes. At any point in a data pipeline, HTTP applications can consume messages using push or pull APIs. The source of the data may include MQTT clients’ data, but also includes the following data sources that send their events over HTTP:

  • Azure services
  • Your custom applications
  • External partner (SaaS) systems

Event Grid's push delivery mechanism sends data to destinations that include your own application webhooks and Azure services.

Capabilities

Event Grid offers a rich mixture of features. These features include:

MQTT messaging

  • MQTT v3.1.1 and MQTT v5.0 support – Use any open source MQTT client library to communicate with the service.
  • Custom topics with wildcards support - Leverage your own topic structure.
  • Publish-subscribe messaging model - Communicate efficiently using one-to-many, many-to-one, and one-to-one messaging patterns.
  • Built-in cloud integration - Route your MQTT messages to Azure services or custom webhooks for further processing.
  • Flexible and fine-grained access control model - Group clients and topic to simplify access control management, and use the variable support in topic templates for a fine-grained access control.
  • MQTT broker authentication methods - X.509 certificate authentication is the industry authentication standard in IoT devices, Microsoft Entra IDauthentication is Azure's authentication standard for applications and OAuth 2.0 (JSON Web Token) authentication provides a lightweight, secure, and flexible option for MQTT clients that are not provisioned in Azure.
  • TLS 1.2 and TLS 1.3 support - Secure your client communication using robust encryption protocols.
  • Multi-session support - Connect your applications with multiple active sessions to ensure reliability and scalability.
  • MQTT over WebSockets - Enable connectivity for clients in firewall-restricted environments.
  • Custom domain names - Allows users to assign their own domain names to Event Grid namespace's MQTT endpoints, enhancing security and simplifying client configuration.
  • Client Life Cycle events - Allow applications to react to events about the client connection status or the client resource operations.

Event messaging (HTTP)

  • Flexible event consumption model – when using HTTP, consume events using pull or push delivery mode.
  • System events – Get up and running quickly with built-in Azure service events.
  • Your own application events - Use Event Grid to route, filter, and reliably deliver custom events from your app.
  • Partner events – Subscribe to your partner SaaS provider events and process them on Azure.
  • Advanced filtering – Filter on event type or other event attributes to make sure your event handlers or consumer apps receive only relevant events.
  • Reliability – Push delivery features a 24-hour retry mechanism with exponential backoff to make sure events are delivered. If you use pull delivery, your application has full control over event consumption.
  • High throughput - Build high-volume integrated solutions with Event Grid.
  • Custom domain names - Allows users to assign their own domain names to Event Grid namespace's HTTP endpoints, enhancing security and simplifying client configuration.

Note

Regarding TLS 1.0 / 1.1 deprecation: For system topics, you need to take action only for the event delivery to webhook destinations. If the destination supports TLS 1.2, the event delivery happens using 1.2. If the destination doesn't support TLS 1.2, the event delivery automatically falls back to 1.0 and 1.1. Post March 1st, 2025, event delivery using 1.0 and 1.1 won't be supported. Ensure that your webhook destinations support TLS 1.2. One easy way to check for TLS 1.2 support is to use Qualys SSL Labs. If the report shows that TLS 1.2 is supported, no action is required. For more information, see the following blog post: Retirement: Upcoming TLS changes for Azure Event Grid

Use cases

Event Grid supports the following use cases:

MQTT messaging

Event Grid enables your clients to communicate on custom MQTT topic names using a publish-subscribe messaging model. Event Grid supports clients that publish and subscribe to messages over MQTT v3.1.1, MQTT v3.1.1 over WebSockets, MQTT v5, and MQTT v5 over WebSockets. Event Grid allows you to send MQTT messages to the cloud for data analysis, storage, and visualizations, among other use cases.

Event Grid integrates with Azure IoT MQ to bridge its MQTT broker capability on the edge with Event Grid’s MQTT broker capability in the cloud. Azure IoT MQ is a new distributed MQTT broker for edge computing, running on Arc enabled Kubernetes clusters. It's now available in public preview as part of Azure IoT Operations.

The MQTT broker feature in Azure Event Grid is ideal for the implementation of automotive and mobility scenarios, among others. See the reference architecture to learn how to build secure and scalable solutions for connecting millions of vehicles to the cloud, using Azure’s messaging and data analytics services.

High-level diagram of Event Grid that shows bidirectional MQTT communication with publisher and subscriber clients.

Azure Event Grid’s MQTT broker feature enables you to accomplish the following scenarios.

Ingest IoT telemetry

High-level diagram of Event Grid that shows IoT clients using MQTT protocol to send messages to a cloud app.

Ingest telemetry using a many-to-one messaging pattern. For example, use Event Grid to send telemetry from multiple IoT devices to a cloud application. This pattern enables the application to offload the burden of managing the high number of connections with devices to Event Grid.

Command and control

High-level diagram of Event Grid that shows a cloud application sending a command message over MQTT to a device using request and response topics.

Control your MQTT clients using the request-response (one-to-one) message pattern. For example, use Event Grid to send a command from a cloud application to an IoT device.

Broadcast alerts

High-level diagram of Event Grid that shows a cloud application sending an alert message over MQTT to several devices.

Broadcast alerts to a fleet of clients using the one-to-many messaging pattern. For example, use Event Grid to send an alert from a cloud application to multiple IoT devices. This pattern enables the application to publish only one message that the service replicates for every interested client.

Integrate MQTT data

Diagram that shows several IoT devices sending health data over MQTT to Event Grid, then to Event Hubs, and from this service to Azure Stream Analytics.

Integrate data from your MQTT clients by routing MQTT messages to Azure services and custom endpoints through push delivery or pull delivery. For example, use Event Grid to route telemetry from your IoT devices to Event Hubs and then to Azure Stream Analytics to gain insights from your device telemetry.

Push delivery of events

Event Grid can be configured to send events to a diverse set of Azure services or webhooks using push event delivery. Event sources include your custom applications, Azure services, and partner (SaaS) services that publish events announcing system state changes (also known as "discrete" events). In turn, Event Grid delivers those events to configured subscribers’ destinations.

Event Grid’s push delivery allows you to realize the following use cases.

Note

Push delivery is available in Event Grid basic tier and Event Grid standard tier, to learn more about the differences see choose the right Event Grid tier for your solution.

Build event-driven serverless solutions

Diagram that shows Azure Functions publishing events to Event Grid using HTTP. Event Grid then sends those events to Azure Logic Apps.

Use Event Grid to build serverless solutions with Azure Functions Apps, Logic Apps, and API Management. Using serverless services with Event Grid affords you a level of productivity, effort economy, and integration superior to that of classical computing models where you have to procure, manage, secure, and maintain all infrastructure deployed.

Receive events from Azure services

Diagram that shows Blob Storage publishing events to Event Grid over HTTP. Event Grid sends those events to event handlers, which are either webhooks or Azure services.

Event Grid can receive events from 20+ Azure services so that you can automate your operations. For example, you can configure Event Grid to receive an event when a new blob has been created on an Azure Storage Account so that your downstream application can read and process its content. For a list of all supported Azure services and events, see System topics.

Receive events from your applications

Diagram that shows customer application publishing events to Event Grid using HTTP. Event Grid sends those events to webhooks or Azure services.

Your own service or application publishes events to Event Grid that subscriber applications process. Event Grid features Namespace Topics to address integration and routing requirements at scale with a simple resource model. You can also use Custom Topics to meet basic integration requirements and Domains for a simple management and routing model when you need to distribute events to hundreds or thousands of different groups.

Receive events from partner (SaaS providers)

Diagram that shows an external partner application publishing event to Event Grid using HTTP. Event Grid sends those events to webhooks or Azure services.

A multitenant SaaS provider or platform can publish their events to Event Grid through a feature called Partner Events. You can subscribe to those events and automate tasks, for example. Events from the following partners are currently available:

Event Handlers

An event subscription is a generic configuration resource that allows you to define the event handler or destination to which events are sent using push delivery. For example, you can send data to a Webhook, Azure Function, or Event Hubs. For a complete list of event handlers supported, see:

Pull delivery of discrete events

Azure Event Grid features pull CloudEvents delivery. With this delivery mode, clients connect to Event Grid to read events. The following use cases can be realized using pull delivery.

Receive events at your own pace

High-level diagram of a publisher and consumer application. The publisher sends events to Event Grid at a higher pace than the subscriber's event consumption rate.

One or more clients can connect to Azure Event Grid to read messages at their own pace. Event Grid affords clients full control on events consumption. Your application can receive events at certain times of the day, for example. Your solution can also increase the rate of consumption by adding more clients that read from Event Grid.

High-level diagram of a consumer app inside a VNET reading events from Event Grid over a private endpoint inside the VNET.

You can configure private links to connect to Azure Event Grid to publish and read CloudEvents through a private endpoint in your virtual network. Traffic between your virtual network and Event Grid travels the Microsoft backbone network.

Important

Private links are available with pull delivery, not with push delivery. You can use private links when your application connects to Event Grid to publish events or receive events, not when Event Grid connects to your webhook or Azure service to deliver events.

Regions where Event Grid namespace is available

Here's the list of regions where the new MQTT broker and namespace topics features are available:

Region Region Region Region
Australia East Australia South East Australia Central Australia Central 2
Brazil South Brazil Southeast Canada Central Canada East
Central India Central US East Asia East US
East US 2 West US France Central France South
Germany North Germany West Central Israel Central Italy North
Japan East Japan West Korea Central Korea South
Mexico Central North Central US North Europe Norway East
Poland Central South Africa West South Africa North South Central US
South India Southeast Asia Spain Central Sweden Central
Sweden South Switzerland North Switzerland West UAE North
UAE Central UK South UK West West Europe
West US 2 West US 3 West Central US

Next steps

MQTT messaging

Data distribution using pull or push delivery

See also