Blog Post

Messaging on Azure Blog
4 MIN READ

Azure Event Grid: Powering IoT and Event-Driven Applications at Scale

Connected-Seth's avatar
Jun 03, 2026

Modern IoT and event-driven applications demand more than reliable messaging. They require the ability to handle larger payloads, efficiently route data at scale, and automatically adapt to changing workloads. Today, we're excited to introduce a new set of capabilities in Azure Event Grid Namespace (MQTT Broker & Event Broker) that help organizations build more scalable, resilient, and cost-efficient connected solutions. With support for MQTT v5 Subscription Identifiers, larger messages(1MB), and Auto scale-up and scale-down, customers can simplify architecture, reduce operational overhead, and accelerate deployments across manufacturing, automotive, retail, energy, and other connected industries.

Event Grid Standard: MQTT v5 Subscription Identifier (GA)

What it solves

In many MQTT applications, one client subscribes to several topics at the same time. When a message arrives, the application needs a quick way to tell which subscription triggered it and what should happen next.

  • Which subscription triggered this message?
  • Which business rule should process it?

What’s new

MQTT v5 Subscription Identifier is now generally available in Event Grid MQTT broker. Each subscription can have an ID, and that ID is included when the message is delivered.

Each subscription can have an ID, and when a message is delivered, that ID comes with it.

Why it matters

  • Faster message routing
  • Cleaner application logic
  • No need to parse topic strings

Simple example

Example subscriptions:

Subscription ID 101 = factory/line1/temperature

Subscription ID 202 = factory/line1/vibration

When a message arrives

If the message comes in with Subscription ID 101, the app immediately knows it is temperature data and can send it to the correct processing path without inspecting the topic string.

Instant message context with MQTT v5 Subscription Identifiers

Common use cases

  • Manufacturing lines with hundreds of sensors
  • Automotive telemetry platforms
  • Multi‑tenant IoT solutions
  • Rule engines and stream processors

Event Grid Standard: 1MB Message Support (GA) - Coming Soon

Applies to both MQTT and non-MQTT workloads.

What it solves

As devices and applications become more capable, the events they send are becoming richer too.

In many real-world scenarios, a single message may need to include things like:

  • Sensor batches
  • Telemetry snapshots
  • Diagnostics data
  • Configuration payloads

Before this, customers often had to split large messages into smaller pieces or store the payload somewhere else and send only a reference.

What’s new

Event Grid Standard Namespace now supports larger event payloads upto 1MB for both MQTT and non-MQTT scenarios. That means customers can send more complete information in one message and reduce complex workarounds in design.

Why it matters

  • Fewer architectural components
  • Simpler producers and consumers
  • Lower latency for real‑time decisions

Example

Before: A factory device sent the main payload to storage and then published a small event that pointed to that file.

Now: The same device can publish the full event payload directly through Event Grid, making the flow easier to build and easier to operate.

Example: A smart machine can send a larger diagnostic package in one event, including the machine ID, a batch of readings, and a timestamp, instead of splitting the information across multiple services.

 

Unlock larger event-driven workloads with Azure Event Grid

Common use cases

  • Smart manufacturing telemetry
  • Vehicle diagnostics and firmware data
  • Batch sensor readings from edge devices
  • Rich business events for analytics

Event Grid Standard: Autoscale Up and Down (Preview) - Coming Soon

Applies to both MQTT and non-MQTT workloads.

What it solves

Event-driven systems rarely operate at a constant rate. Traffic patterns fluctuate throughout the day, with predictable peaks, seasonal surges, and unexpected bursts that can quickly overwhelm static infrastructure.

Think about:

  • Morning factory startup
  • Fleet check‑ins at the top of the hour
  • Flash sales or system bursts

Manually sizing infrastructure leads to:

  • Over‑provisioning (higher cost)
  • Under‑provisioning (missed events)

What’s new

Azure Event Grid Standard Namespace now supports Autoscale Up and Down, automatically adjusting capacity based on real-time workload demand. Whether you're running MQTT-based IoT workloads or event-driven applications using HTTP, AMQP, or CloudEvents, Event Grid dynamically scales resources to match traffic patterns without manual intervention.

As demand grows, Event Grid automatically adds capacity to absorb increased traffic and maintain performance. When activity subsides, resources scale back down to optimize efficiency and reduce costs.

Why it matters

 With Autoscale, customers can focus on building applications instead of managing infrastructure and reap benefits like:

  • Scale seamlessly during traffic spikes without pre-provisioning for peak demand.
  • Reduce costs during quieter periods by automatically scaling capacity down.
  • Maintain consistent performance and reliability across changing workloads.
  • Eliminate manual tuning and capacity planning, reducing operational overhead.
  • Optimize resource utilization while supporting millions of devices and high-volume event streams.

Use case: A Modern Event-Driven Manufacturing Platform

A smart manufacturing company uses Microsoft to connect factory machines, sensors, edge gateways, and enterprise applications through a single scalable eventing platform. Devices publish rich telemetry and diagnostic payloads using MQTT, while cloud applications send operational and business events using HTTP. The company has steady traffic during the day, a large spike during shift changes, and much lower usage overnight. With autoscale, Event Grid adjusts capacity automatically, so performance stays strong when traffic is high and costs stay more efficient when traffic is low.

 

Autoscale intelligently to match changing workload demands

Common use cases

  • Shift‑based manufacturing systems
  • Connected vehicle platforms
  • Event‑driven commerce backends
  • Analytics pipelines with bursty data

Building IoT platforms, manufacturing and automotive solutions, or high-scale event-driven applications?

Azure Event Grid MQTT Broker now delivers larger messages, subscription Identifiers, and autoscale up/down, helping you simplify operations, improve performance, and optimize costs all on a single eventing platform.

Event Grid Basic: Powering Event Driven Payments with Stripe (GA)

Developers can seamlessly route Stripe events into Azure Event Grid to build scalable, event driven architectures without managing webhooks or custom brokers. Event Grid acts as a fully managed event broker between Stripe and Azure services.

Azure Event Grid now delivers Stripe events directly to Azure subscribers, including:

  • Azure Functions
  • Logic Apps
  • Event Hubs
  • Service Bus
  • And more

With Event Grid’s native integration with Microsoft Fabric, Stripe events can also be ingested as continuous streams, enabling real time transformation, enrichment, and analytics within Fabric. Learn more.

Updated Jun 02, 2026
Version 1.0
No CommentsBe the first to comment