Skip to content

Commit e945091

Browse files
committed
Update quotas and webhook section
1 parent 5c3cad5 commit e945091

File tree

3 files changed

+8
-6
lines changed

3 files changed

+8
-6
lines changed

articles/event-grid/deliver-events-using-managed-identity.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,8 @@ To deliver events to Storage queues using managed identity, follow these steps:
5656
To deliver events to a Webhook using managed identity, follow these steps:
5757

5858
1. Enable system-assigned or user-assigned managed identity: [system topics](enable-identity-system-topics.md), [custom topics and domains](enable-identity-custom-topics-domains.md), and [namespaces](event-grid-namespace-managed-identity.md).
59-
1. [Configure the event subscription](create-view-manage-event-subscriptions.md) that uses a Webhook as an endpoint to use the system-assigned or user-assigned managed identity.
59+
1. Create a single tenant or multitenant application to set the audience for the token.
60+
1. [Configure the event subscription](create-view-manage-event-subscriptions.md) that uses a Webhook as an endpoint to use the system-assigned or user-assigned managed identity. Once you select the type of managed identity, you need to introduce the new application ID and the tenant ID. In the cross-tenant scenario, the application ID must be from an application created in the destination tenant.
6061

6162
## Firewall and virtual network rules
6263
If there's no firewall or virtual network rules configured for the destination Storage account, Event Hubs namespace, or Service Bus namespace, you can use both user-assigned and system-assigned identities to deliver events.

articles/event-grid/includes/limits.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
author: robece
55
ms.service: azure-event-grid
66
ms.topic: include
7-
ms.date: 11/15/2023
7+
ms.date: 04/30/2025
88
ms.author: robece
99
ms.custom: include file, ignite-2023
1010
---
@@ -41,9 +41,9 @@ The following limits apply to MQTT in Azure Event Grid namespace resource.
4141
| Session Expiry Interval | 8 hours, [configurable on the Event Grid namespace](../mqtt-support.md#maximum-session-expiry-interval-configuration)|
4242
| Inbound MQTT publishing requests per Event Grid namespace | 1,000 messages per second per TU |
4343
| Inbound MQTT bandwidth per Event Grid namespace | 1 MB per second per TU |
44-
| Inbound MQTT publishing requests per session | 100 messages per second |
44+
| Inbound MQTT publishing requests per session | 1000 messages per second |
4545
| Inbound MQTT bandwidth per session | 1 MB per second |
46-
| Inbound in-flight MQTT messages* | 100 messages |
46+
| Inbound in-flight MQTT messages* | 1000 messages |
4747
| Inbound in-flight MQTT bandwidth* | 64 KB |
4848
| Outbound MQTT publishing requests per Event Grid namespace | 1,000 messages per second per TU |
4949
| Outbound MQTT bandwidth per Event Grid namespace | 1 MB per second per TU |
@@ -52,11 +52,12 @@ The following limits apply to MQTT in Azure Event Grid namespace resource.
5252
| Outbound in-flight MQTT messages* | 100 messages |
5353
| Outbound in-flight MQTT bandwidth* | 64 KB |
5454
| Max message size | 512 KB |
55-
| Segments per topic/ topic filter | 8 |
55+
| Segments per topic/ topic filter | 15 |
5656
| Topic size | 256 B |
5757
| MQTTv5 response topic | 256 B |
5858
| MQTTv5 topic aliases | 10 per session |
5959
| MQTTv5 total size of all user properties | 32 KB |
60+
| MQTT connect rate per client Session | 1 connection attempt per second per client session |
6061
| MQTTv5 content type size | 256 B |
6162
| MQTTv5 correlation data size | 256 B |
6263
| Connect requests | 200 requests per second per TU |

articles/event-grid/quotas-limits.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Quotas and limits - Azure Event Grid | Microsoft Docs
33
description: This article provides limits and quotas for Azure Event Grid. For example, number of subscriptions for topic, number of custom topics per subscription, etc.
44
ms.topic: reference
55
ms.custom: build-2023
6-
ms.date: 05/09/2023
6+
ms.date: 04/30/2025
77
---
88

99
# Azure Event Grid quotas and limits

0 commit comments

Comments
 (0)