Skip to content

Commit 4b13b77

Browse files
Minor edits.
1 parent 2d36bac commit 4b13b77

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/event-hubs/schema-registry-dotnet-send-receive-quickstart.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,7 @@ ms.author: spelluru
1414

1515
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.
1616

17-
> [!NOTE]
18-
> **Azure Schema Registry** is a feature of Event Hubs. The registry 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).
17+
*Azure Schema Registry* is a feature of Event Hubs. The registry 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).
1918

2019
## Prerequisites
2120

@@ -45,7 +44,7 @@ Note down the following settings to use in the current quickstart:
4544

4645
To create a schema group and a schema, follow instructions from [Create schemas using Schema Registry](create-schema-registry.md).
4746

48-
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.
47+
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.
4948
1. In that schema group, create a new Avro schema with schema name: `Microsoft.Azure.Data.SchemaRegistry.example.Order`. Use the following schema content.
5049

5150
```json
@@ -75,7 +74,7 @@ To create a schema group and a schema, follow instructions from [Create schemas
7574
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.
7675

7776
1. On the **Event Hubs Namespace** page, on the left menu, select **Access control (IAM)**.
78-
1. On the **Access control (IAM)** page, select **+ Add** -> **Add role assignment**.
77+
1. On the **Access control (IAM)** page, select **+ Add** > **Add role assignment**.
7978
1. On the **Roles** page, select **Schema Registry Reader**, and then select **Next**.
8079
1. Use the **+ Select members** link to add your user account to the role, and then select **Next**.
8180
1. On the **Review + assign** page, select **Review + assign**.
@@ -109,8 +108,8 @@ Add your user account to the **Schema Registry Reader** role at the namespace le
109108
Install-Package Azure.ResourceManager.Compute
110109
```
111110

112-
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).
113-
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).
111+
1. Authenticate producer applications to connect to Azure by using Visual Studio. For more information, see [Azure Identity client library for .NET](/dotnet/api/overview/azure/identity-readme#authenticate-via-visual-studio).
112+
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).
114113

115114
### Code generation using the Avro schema
116115

@@ -178,7 +177,7 @@ Add your user account to the **Schema Registry Reader** role at the namespace le
178177
// Send the batch of events to the event hub.
179178
await producerClient.SendAsync(eventBatch);
180179
Console.WriteLine("A batch of 1 order has been published.");
181-
```
180+
```
182181

183182
1. Replace the following placeholder values with the real values.
184183

@@ -368,6 +367,7 @@ This section shows how to write a .NET Core console application that receives ev
368367
```bash
369368
Received order with ID: 1234, amount: 45.29, description: First sample order.
370369
```
370+
371371
These events are the three events you sent to the event hub earlier by running the sender program.
372372

373373
## Samples

0 commit comments

Comments
 (0)