You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: 'Quickstart: Send and receive large messages with Azure Event Hubs (preview)'
3
-
description: In this quickstart, you learn how to send and receive large messages with Azure Event Hubs.
2
+
title: 'Quickstart: Send and Receive Large Messages with Azure Event Hubs (Preview)'
3
+
description: In this quickstart, you learn how to send and receive large messages with Azure Event Hubs after you configure an Event Hubs dedicated cluster.
4
4
ms.topic: quickstart
5
5
ms.author: Saglodha
6
-
ms.date: 5/6/2024
6
+
ms.date: 06/16/2025
7
+
#customer intent: As a developer, I want to understand how to send and receive large messages with Azure Event Hubs to support apps that need this ability.
7
8
---
8
9
9
10
# Quickstart: Send and receive large messages with Azure Event Hubs (preview)
10
11
11
-
In this quickstart, you learn how to send and receive large messages (up to 20 MB) by using Azure Event Hubs. If you're new to Event Hubs, see [Event Hubs overview](event-hubs-about.md) before you go through this quickstart.
12
+
In this quickstart, you learn how to send and receive large messages (up to 20 MB) by using Azure Event Hubs. If you're new to Event Hubs, see [Event Hubs overview](event-hubs-about.md) before you begin.
12
13
13
-
###Prerequisites
14
+
## Prerequisites
14
15
15
-
To complete this quickstart, you need the following prerequisites:
16
-
17
-
- An Azure subscription. To use Azure services, including Event Hubs, you need a subscription. If you don't have an existing Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) or use your MSDN subscriber benefits when you [create an account](https://azure.microsoft.com/).
18
-
- A [self-serve scalable dedicated cluster](event-hubs-dedicated-cluster-create-portal.md), an event hubs namespace, and an event hub. The first step to meet this prerequisite is to use the Azure portal to create a dedicated cluster and namespace inside a cluster. To create an event hub, see [Quickstart: Create an event hub by using the Azure portal](event-hubs-create.md). You can skip this step if you already have a self-serve scalable dedicated cluster.
16
+
- An Azure subscription. To use Azure services, including Event Hubs, you need a subscription. If you don't have an Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) or activate your [Monthly Azure credits for Visual Studio subscribers](https://azure.microsoft.com/pricing/member-offers/credit-for-visual-studio-subscribers/?WT.mc_id=A85619ABF).
17
+
- A [self-serve scalable dedicated cluster](event-hubs-dedicated-cluster-create-portal.md), an Event Hubs namespace, and an event hub. Use the Azure portal to create a dedicated cluster and namespace inside a cluster. To create an event hub, see [Quickstart: Create an event hub by using the Azure portal](event-hubs-create.md). You can skip this step if you already have a self-serve scalable dedicated cluster.
19
18
20
19
> [!NOTE]
21
-
> Large message support, currently in public preview, is exclusively available with certain Event Hubs self-serve dedicated clusters. Streaming large messages with these clusters incurs no extra charges.
20
+
> Large message support is currently in public preview. It's exclusively available with certain Event Hubs self-serve dedicated clusters. Streaming large messages with these clusters incurs no extra charges.
22
21
23
22
## Configure an Event Hubs dedicated cluster
24
23
25
24
To stream large messages, you must configure your self-serve scalable dedicated cluster.
26
25
27
26
In the Azure portal, go to the **Settings** section for the dedicated cluster. Under **Settings**, select the **Quota** tab.
28
27
29
-
:::image type="content" source="./media/event-hubs-quickstart-stream-large-messages/large-message-configuration-for-dedicated-cluster.png" alt-text="Screenshot that shows the Quota pane for a dedicated cluster.":::
28
+
:::image type="content" source="./media/event-hubs-quickstart-stream-large-messages/large-message-configuration-for-dedicated-cluster.png" alt-text="Screenshot that shows the Quota pane for a dedicated cluster." lightbox="./media/event-hubs-quickstart-stream-large-messages/large-message-configuration-for-dedicated-cluster.png":::
30
29
31
30
- Validate that the value for the read-only key `supportslargemessages` is set to `True`.
32
31
- You can update the key `eventhubmaxmessagesizeinbytes` to a suitable value in bytes. An acceptable range for this value is between 1,048,576 and 20,971,520 bytes.
33
32
34
33
After the configuration is saved, you're ready to stream large messages with Event Hubs.
35
34
36
35
> [!IMPORTANT]
37
-
> Large message streaming is only supported with self-serve scalable dedicated clusters built out of the latest infrastructure. This capability is reflected by the `Supportslargemessages` key.
36
+
> Large message streaming is only supported with self-serve scalable dedicated clusters built out of the latest infrastructure. The `Supportslargemessages` key reflects this capability.
38
37
>
39
-
> If a cluster value is false, it won't support large message streaming. To enable this feature, you must re-create the cluster.
38
+
> If a cluster value is false, it doesn't support large message streaming. To enable this feature, you must re-create the cluster.
40
39
41
40
## Stream large messages with Event Hubs
42
41
@@ -47,6 +46,6 @@ For more information, see [Send events to and receive events from Event Hubs by
47
46
> [!TIP]
48
47
> Make sure to review any Event Hubs Advanced Message Queuing Protocol (AMQP) client or Kafka client configuration that might limit the maximum message size that you stream into Event Hubs. You must update client timeout to a higher value to stream large messages.
49
48
>
50
-
>By default, the AMQP client prefetch count is 300. Lower this value to avoid client-side memory issues when you deal with large messages.
49
+
>By default, the AMQP client prefetch count is 300. Lower this value to avoid client-side memory issues when you deal with large messages.
51
50
52
-
For the complete .NET library reference, see the [SDK documentation](/dotnet/api/overview/azure/event-hubs).
51
+
For the complete SDK reference, see [Azure Event Hubs libraries for .NET](/dotnet/api/overview/azure/event-hubs).
0 commit comments