Freshness, in progress.

TimShererWithAquent · TimShererWithAquent · commit d41252171996 · 2025-06-13T15:35:34.000-07:00
diff --git a/articles/event-hubs/schema-registry-dotnet-send-receive-quickstart.md b/articles/event-hubs/schema-registry-dotnet-send-receive-quickstart.md
@@ -1,37 +1,43 @@
 ---
-title: 'Validate schema when sending or receiving events'
+title: 'Validate Schema When Sending or Receiving Events'
 description: In this quickstart, you create a .NET Core application that sends/receives events to/from Azure Event Hubs with schema validation using Schema Registry.
 ms.topic: quickstart
-ms.date: 04/26/2023
+ms.date: 06/16/2025
 ms.devlang: csharp
 ms.custom: devx-track-dotnet
 author: spelluru
 ms.author: spelluru
+#customer intent: As a developer, I want to learn how to send events to and receive events from an event hub with schema validation.
 ---
 
-# Validate using an Avro schema when streaming events using Event Hubs .NET SDKs (AMQP) 
+# Validate using an Avro schema when streaming events using Event Hubs .NET SDKs (AMQP)
+
 In this quickstart, you learn how to send events to and receive events from an event hub with schema validation using the **Azure.Messaging.EventHubs** .NET library. 
 
 > [!NOTE]
 > **Azure Schema Registry** is a feature of Event Hubs, which provides a central repository for schemas for event-driven and messaging-centric applications. It provides the flexibility for your producer and consumer applications to **exchange data without having to manage and share the schema**. It also provides a simple governance framework for reusable schemas and defines relationship between schemas through a grouping construct (schema groups). For more information, see [Azure Schema Registry in Event Hubs](schema-registry-overview.md).
 
-
 ## Prerequisites
+
 If you're new to Azure Event Hubs, see [Event Hubs overview](event-hubs-about.md) before you do this quickstart. 
 
 To complete this quickstart, you need the following prerequisites:
+
 - If you don't have an **Azure subscription**, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 - **Microsoft Visual Studio 2022**. 
-    The Azure Event Hubs client library makes use of new features that were introduced in C# 8.0.  You can still use the library with  previous C# language versions, but the new syntax isn't available. To make use of the full syntax, we recommended that you compile with the [.NET Core SDK](https://dotnet.microsoft.com/download) 3.0 or higher and [language version](/dotnet/csharp/language-reference/configure-language-version#override-a-default) set to `latest`. If you're using Visual Studio, versions before Visual Studio 2019 aren't compatible with the tools needed to build C# 8.0 projects. Visual Studio 2019, including the free Community edition, can be downloaded [here](https://visualstudio.microsoft.com/vs/).    
+    The Azure Event Hubs client library makes use of new features that were introduced in C# 8.0.  You can still use the library with  previous C# language versions, but the new syntax isn't available. To make use of the full syntax, we recommended that you compile with the [.NET Core SDK](https://dotnet.microsoft.com/download) 3.0 or higher and [language version](/dotnet/csharp/language-reference/configure-language-version) set to `latest`. If you're using Visual Studio, versions before Visual Studio 2019 aren't compatible with the tools needed to build C# 8.0 projects. To download Visual Studio 2019, including the free Community edition, see [Visual Studio](https://visualstudio.microsoft.com/vs/).    
 
 ## Create an event hub
+
 Follow instructions from the quickstart: [Create an Event Hubs namespace and an event hub](event-hubs-create.md) to create an Event Hubs namespace and an event hub. Then, follow instructions from [Get the connection string](event-hubs-get-connection-string.md) to get a connection string to your Event Hubs namespace. 
 
-Note down the following settings that you'll use in the current quickstart:
+Note down the following settings that to use in the current quickstart:
+
 - Connection string for the Event Hubs namespace
 - Name of the event hub
 
 ## Create a schema 
+
 Follow instructions from [Create schemas using Schema Registry](create-schema-registry.md) to create a schema group and a schema. 
 
 1. Create a schema group named **contoso-sg** using the Schema Registry portal. Use Avro as the serialization type and **None** for the compatibility mode. 
@@ -60,14 +66,15 @@ Follow instructions from [Create schemas using Schema Registry](create-schema-re
     ```
 
 ## Add user to Schema Registry Reader role
+
 Add your user account to the **Schema Registry Reader** role at the namespace level. You can also use the **Schema Registry Contributor** role, but that's not necessary for this quickstart.  
 
 1. On the **Event Hubs Namespace** page, select **Access control (IAM)** on the left menu.
-2. On the **Access control (IAM)** page, select **+ Add** -> **Add role assignment** on the menu. 
-3. On the **Assignment type** page, select **Next**.
-4. On the **Roles** page, select **Schema Registry Reader (Preview)**, and then select **Next** at the bottom of the page.
-5. Use the **+ Select members** link to add your user account to the role, and then select **Next**. 
-6. On the **Review + assign** page, select **Review + assign**.
+1. On the **Access control (IAM)** page, select **+ Add** -> **Add role assignment** on the menu. 
+1. On the **Assignment type** page, select **Next**.
+1. On the **Roles** page, select **Schema Registry Reader (Preview)**, and then select **Next** at the bottom of the page.
+1. Use the **+ Select members** link to add your user account to the role, and then select **Next**. 
+1. On the **Review + assign** page, select **Review + assign**.
 
 ## Produce events to event hubs with schema validation
 
@@ -76,15 +83,16 @@ Add your user account to the **Schema Registry Reader** role at the namespace le
 
 1. Start Visual Studio 2019. 
 1. Select **Create a new project**. 
-1. On the **Create a new project** dialog box, do the following steps: If you don't see this dialog box, select **File** on the menu, select **New**, and then select **Project**. 
-    1. Select **C#** for the programming language.
-    1. Select **Console** for the type of the application. 
-    1. Select **Console Application** from the results list. 
-    1. Then, select **Next**. 
+1. On the **Create a new project** dialog box, do the following steps: If you don't see this dialog box, select **File** on the menu, select **New**, and then select **Project**.
 
-        :::image type="content" source="./media/getstarted-dotnet-standard-send-v2/new-send-project.png" alt-text="Image showing the New Project dialog box.":::
-1. Enter **OrderProducer** for the project name, **SRQuickStart** for the solution name, and then select **OK** to create the project. 
+   1. Select **C#** for the programming language.
+   1. Select **Console** for the type of the application. 
+   1. Select **Console Application** from the results list. 
+   1. Then, select **Next**. 
 
+       :::image type="content" source="./media/getstarted-dotnet-standard-send-v2/new-send-project.png" alt-text="Image showing the New Project dialog box.":::
+
+1. Enter **OrderProducer** for the project name, **SRQuickStart** for the solution name, and then select **OK** to create the project. 
 
 ### Add the Event Hubs NuGet package
 
@@ -97,26 +105,28 @@ Add your user account to the **Schema Registry Reader** role at the namespace le
     Install-Package Microsoft.Azure.Data.SchemaRegistry.ApacheAvro
     Install-Package Azure.ResourceManager.Compute
     ```
-1. Authenticate producer applications to connect to Azure via Visual Studio as shown [here](/dotnet/api/overview/azure/identity-readme#authenticating-via-visual-studio).  
-1. Sign-in to Azure using the user account that's a member of the `Schema Registry Reader` role at the namespace level. For information about schema registry roles, see [Azure Schema Registry in Event Hubs](schema-registry-concepts.md#azure-role-based-access-control). 
 
-### Code generation using the Avro schema  
+1. Authenticate producer applications to connect to Azure via Visual Studio. For more information, see [Azure Identity client library for .NET](/dotnet/api/overview/azure/identity-readme#authenticate-via-visual-studio).  
+1. Sign-in to Azure using the user account that's a member of the `Schema Registry Reader` role at the namespace level. For information about schema registry roles, see [Azure role-based access control](schema-registry-concepts.md#azure-role-based-access-control). 
+
+### Code generation using the Avro schema
+
 1. Use the same content you used to create the schema to create a file named ``Order.avsc``. Save the file in the project or solution folder. 
-1. Then you can use this schema file to generate code for .NET. You can use any external code generation tool such as [avrogen](https://www.nuget.org/packages/Apache.Avro.Tools/) for code generation. For example you can run `` avrogen -s .\Order.avsc .`` to generate code. 
-1. Once you generate code, you'll see the file named `Order.cs` in the `\Microsoft\Azure\Data\SchemaRegistry\example` folder. For the above Avro schema, it generates the C# types in ``Microsoft.Azure.Data.SchemaRegistry.example`` namespace. 
+1. Then you can use this schema file to generate code for .NET. You can use any external code generation tool such as [avrogen](https://www.nuget.org/packages/Apache.Avro.Tools/) for code generation. For example, you can run `` avrogen -s .\Order.avsc .`` to generate code. 
+1. Once you generate code, you see the file named `Order.cs` in the `\Microsoft\Azure\Data\SchemaRegistry\example` folder. For the above Avro schema, it generates the C# types in ``Microsoft.Azure.Data.SchemaRegistry.example`` namespace. 
 1. Add the `Order.cs` file to the `OrderProducer` project. 
 
-
 ### Write code to serialize and send events to the event hub 
 
-1. Add the following code to the `Program.cs` file. See the code comments for details. High-level steps in the code are: 
-    1. Create a producer client that you can use to send events to an event hub.
-    1. Create a schema registry client that you can use to serialize and validate data in an `Order` object. 
-    1. Create a new `Order` object using the generated `Order` type. 
-    1. Use the schema registry client to serialize the `Order` object to `EventData`.
-    1. Create a batch of events.
-    1. Add the event data to the event batch. 
-    1. Use the producer client to send the batch of events to the event hub. 
+1. Add the following code to the `Program.cs` file. See the code comments for details. High-level steps in the code are:
+
+   1. Create a producer client that you can use to send events to an event hub.
+   1. Create a schema registry client that you can use to serialize and validate data in an `Order` object. 
+   1. Create a new `Order` object using the generated `Order` type. 
+   1. Use the schema registry client to serialize the `Order` object to `EventData`.
+   1. Create a batch of events.
+   1. Add the event data to the event batch. 
+   1. Use the producer client to send the batch of events to the event hub. 
 
     ```csharp
     using Azure.Data.SchemaRegistry;
@@ -166,7 +176,9 @@ Add your user account to the **Schema Registry Reader** role at the namespace le
     await producerClient.SendAsync(eventBatch);
     Console.WriteLine("A batch of 1 order has been published.");        
     ```    
+
 1. Replace the following placeholder values with the real values.
+
     - `EVENTHUBSNAMESPACECONNECTIONSTRING` - connection string for the Event Hubs namespace
     - `EVENTHUBNAME` - name of the event hub
     - `EVENTHUBSNAMESPACENAME` - name of the Event Hubs namespace
@@ -184,22 +196,25 @@ Add your user account to the **Schema Registry Reader** role at the namespace le
     
     // name of the consumer group   
     const string schemaGroup = "SCHEMAGROUPNAME";
-    ```    
+    ```
+
 1. Build the project, and ensure that there are no errors.
 1. Run the program and wait for the confirmation message. 
 
     ```csharp
     A batch of 1 order has been published.
     ```
-1. In the Azure portal, you can verify that the event hub has received the events. Switch to **Messages** view in the **Metrics** section. Refresh the page to update the chart. It may take a few seconds for it to show that the messages have been received. 
 
-    :::image type="content" source="./media/getstarted-dotnet-standard-send-v2/verify-messages-portal.png" alt-text="Image of the Azure portal page to verify that the event hub received the events." lightbox="./media/getstarted-dotnet-standard-send-v2/verify-messages-portal.png":::
+1. In the Azure portal, you can verify that the event hub received the events. Switch to **Messages** view in the **Metrics** section. Refresh the page to update the chart. It might take a few seconds for it to show that the messages have been received. 
 
+    :::image type="content" source="./media/getstarted-dotnet-standard-send-v2/verify-messages-portal.png" alt-text="Image of the Azure portal page to verify that the event hub received the events." lightbox="./media/getstarted-dotnet-standard-send-v2/verify-messages-portal.png":::
 
 ## Consume events from event hubs with schema validation
+
 This section shows how to write a .NET Core console application that receives events from an event hub and use schema registry to deserialize event data. 
 
 ### Additional prerequisites
+
 - Create the storage account to be used the event processor.
 
 ### Create consumer application
@@ -222,22 +237,22 @@ This section shows how to write a .NET Core console application that receives ev
     Install-Package Microsoft.Azure.Data.SchemaRegistry.ApacheAvro
     Install-Package Azure.ResourceManager.Compute
     ```
-1. Authenticate producer applications to connect to Azure via Visual Studio as shown [here](/dotnet/api/overview/azure/identity-readme#authenticating-via-visual-studio). 
-1. Sign-in to Azure using the user account that's a member of the `Schema Registry Reader` role at the namespace level. For information about schema registry roles, see [Azure Schema Registry in Event Hubs](schema-registry-concepts.md#azure-role-based-access-control). 
+
+1. Authenticate producer applications to connect to Azure via Visual Studio as shown [Azure Identity client library for .NET](/dotnet/api/overview/azure/identity-readme#authenticate-via-visual-studio). 
+1. Sign-in to Azure using the user account that's a member of the `Schema Registry Reader` role at the namespace level. For information about schema registry roles, see [Azure role-based access control](schema-registry-concepts.md#azure-role-based-access-control). 
 1. Add the `Order.cs` file you generated as part of creating the producer app to the **OrderConsumer** project. 
 1. Right-click **OrderConsumer** project, and select **Set as Startup project**. 
 
-
 ### Write code to receive events and deserialize them using Schema Registry
 
-
 1. Add the following code to the `Program.cs` file. See the code comments for details. High-level steps in the code are: 
-    1. Create a consumer client that you can use to send events to an event hub.
-    1. Create a blob container client for the blob container in the  Azure blob storage.
-    1. Create an event processor client and register event and error handlers. 
-    1. In the event handler, create a schema registry client that you can use to deserialize event data into an `Order` object.     
-    1. Deserialize the event data into an `Order` object using the serializer. 
-    1. Print the information about the received order.
+
+   1. Create a consumer client that you can use to send events to an event hub.
+   1. Create a blob container client for the blob container in the  Azure blob storage.
+   1. Create an event processor client and register event and error handlers. 
+   1. In the event handler, create a schema registry client that you can use to deserialize event data into an `Order` object.     
+   1. Deserialize the event data into an `Order` object using the serializer. 
+   1. Print the information about the received order.
 
     ```csharp
     using Azure.Data.SchemaRegistry;
@@ -313,7 +328,9 @@ This section shows how to write a .NET Core console application that receives ev
         return Task.CompletedTask;
     }      
     ```    
+
 1. Replace the following placeholder values with the real values.
+
     - `EVENTHUBSNAMESPACE-CONNECTIONSTRING` - connection string for the Event Hubs namespace
     - `EVENTHUBNAME` - name of the event hub
     - `EVENTHUBSNAMESPACENAME` - name of the Event Hubs namespace
@@ -339,9 +356,10 @@ This section shows how to write a .NET Core console application that receives ev
     
     // Azure blob container name
     const string blobContainerName = "BLOBCONTAINERNAME";
-    ```    
+    ```
+
 1. Build the project, and ensure that there are no errors.
-6. Run the receiver application. 
+1. Run the receiver application. 
 1. You should see a message that the events have been received. 
 
     ```bash
@@ -350,12 +368,14 @@ This section shows how to write a .NET Core console application that receives ev
     These events are the three events you sent to the event hub earlier by running the sender program. 
 
 ## Samples
-See the [Readme](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/schemaregistry/Microsoft.Azure.Data.SchemaRegistry.ApacheAvro) article in our GitHub repository.
+
+See [Azure Schema Registry Apache Avro client library for .NET](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/schemaregistry/Microsoft.Azure.Data.SchemaRegistry.ApacheAvro).
 
 ## Clean up resources
+
 Delete the Event Hubs namespace or delete the resource group that contains the namespace. 
 
-## Next steps
+## Next step
 
 > [!div class="nextstepaction"]
-> Checkout [Azure Schema Registry client library for .NET](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/schemaregistry/Azure.Data.SchemaRegistry)
+> [Azure Schema Registry client library for .NET](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/schemaregistry/Azure.Data.SchemaRegistry)
