What is the Azure Event Grid pricing for KeepAlive related messages?

Jonas 21 Reputation points
2025-08-28T18:34:16.1233333+00:00

A common pattern when using MQTT is to send continuous PingReq messages within a defined Keep-Alive interval. How are PingReq-type messages billed?

Azure Event Grid
Azure Event Grid
An Azure event routing service designed for high availability, consistent performance, and dynamic scale.
0 comments No comments
{count} votes

Accepted answer
  1. Marcin Policht 54,995 Reputation points MVP Volunteer Moderator
    2025-08-28T18:42:19.2133333+00:00

    AFAIK, Azure Event Grid does not bill for MQTT-level keep-alive operations. According to the official Azure Event Grid pricing FAQ for the Standard tier (https://azure.microsoft.com/en-us/pricing/details/event-grid), MQTT operations such as CONNECT, SUBSCRIBE, UNSUBSCRIBE, PUBLISH, dropped publishes, and client session lifecycle events are specifically listed as billable operations—but keep-alive messages (like PINGREQ and PINGRESP) are not mentioned in that list. Instead, billing focuses on events that carry data—such as ingested MQTT publishes, filters, enriched routing, delivery attempts, etc.—and these are charged per 64 KB data chunk).

    In Azure Event Grid (Standard tier), the billing applies to:

    • MQTT PUBLISH operations (both inbound & outbound)
    • CONNECT, SUBSCRIBE, UNSUBSCRIBE
    • Dropped publish requests (e.g., due to expiry or session overflow)
    • Enrichment and routing (counted as event operations) All of these are billed based on the payload size (per 64 KB chunk)

    PINGREQ (keep-alive) messages are not included in that charge list.


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.