Skip to content

Commit c3a51c5

Browse files
Merge pull request #213674 from whhender/patch-39
Resolving Microsoft Purview naming
2 parents 4f114c6 + 0369263 commit c3a51c5

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

articles/purview/manage-kafka-dotnet.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.custom: mode-other
1515
This quickstart teaches you how to send and receive *Atlas Kafka* topics events. We'll make use of *Azure Event Hubs* and the **Azure.Messaging.EventHubs** .NET library.
1616

1717
> [!IMPORTANT]
18-
> A managed event hub is created automatically when your *Microsoft Purview* account is created. See, [Purview account creation](create-catalog-portal.md). You can publish messages to Event Hubs Kafka topic, ATLAS_HOOK. Purview will receive it, process it and notify Kafka topic ATLAS_ENTITIES of entity changes. This quickstart uses the new **Azure.Messaging.EventHubs** library.
18+
> A managed event hub is created automatically when your *Microsoft Purview* account is created. See, [Microsoft Purview account creation](create-catalog-portal.md). You can publish messages to Event Hubs Kafka topic, ATLAS_HOOK. Microsoft Purview will receive it, process it and notify Kafka topic ATLAS_ENTITIES of entity changes. This quickstart uses the new **Azure.Messaging.EventHubs** library.
1919
2020

2121
## Prerequisites
@@ -31,8 +31,8 @@ To follow this quickstart, you need certain prerequisites in place:
3131
>[!NOTE]
3232
>Enabling this Event Hubs namespace does incur a cost for the namespace. For specific details, see [the pricing page](https://azure.microsoft.com/pricing/details/purview/).
3333
34-
## Publish messages to Purview
35-
Let's create a .NET Core console application that sends events to Purview via Event Hubs Kafka topic, **ATLAS_HOOK**.
34+
## Publish messages to Microsoft Purview
35+
Let's create a .NET Core console application that sends events to Microsoft Purview via Event Hubs Kafka topic, **ATLAS_HOOK**.
3636

3737
## Create a Visual Studio project
3838

@@ -86,13 +86,13 @@ Next create a C# .NET console application in Visual Studio:
8686
private const string eventHubName = "<EVENT HUB NAME>";
8787
```
8888
89-
You can get the Event Hubs namespace associated with the Purview account by looking at the Atlas kafka endpoint primary/secondary connection strings. These can be found in **Properties** tab of your Purview account.
89+
You can get the Event Hubs namespace associated with the Microsoft Purview account by looking at the Atlas kafka endpoint primary/secondary connection strings. These can be found in **Properties** tab of your account.
9090
9191
:::image type="content" source="media/manage-eventhub-kafka-dotnet/properties.png" alt-text="A screenshot that shows an Event Hubs Namespace.":::
9292
93-
The event hub name for sending messages to Purview is **ATLAS_HOOK**.
93+
The event hub name for sending messages to Microsoft Purview is **ATLAS_HOOK**.
9494
95-
3. Replace the `Main` method with the following `async Main` method and add an `async ProduceMessage` to push messages into Purview. See the comments in the code for details.
95+
3. Replace the `Main` method with the following `async Main` method and add an `async ProduceMessage` to push messages into Microsoft Purview. See the comments in the code for details.
9696
9797
```csharp
9898
static async Task Main()
@@ -240,8 +240,8 @@ Next create a C# .NET console application in Visual Studio:
240240
241241
```
242242

243-
## Receive Purview messages
244-
Next learn how to write a .NET Core console application that receives messages from event hubs using an event processor. The event processor manages persistent checkpoints and parallel receptions from event hubs. This simplifies the process of receiving events. You need to use the ATLAS_ENTITIES event hub to receive messages from Purview.
243+
## Receive Microsoft Purview messages
244+
Next learn how to write a .NET Core console application that receives messages from event hubs using an event processor. The event processor manages persistent checkpoints and parallel receptions from event hubs. This simplifies the process of receiving events. You need to use the ATLAS_ENTITIES event hub to receive messages from Microsoft Purview.
245245

246246
> [!WARNING]
247247
> Event Hubs SDK uses the most recent version of Storage API available. That version may not necessarily be available on your Stack Hub platform. If you run this code on Azure Stack Hub, you will experience runtime errors unless you target the specific version you are using. If you're using Azure Blob Storage as a checkpoint store, review the [supported Azure Storage API version for your Azure Stack Hub build](/azure-stack/user/azure-stack-acs-differences?#api-version) and in your code, target that version.
@@ -301,11 +301,11 @@ We'll use Azure Storage as the checkpoint store. Use the following steps to crea
301301
private const string blobContainerName = "<BLOB CONTAINER NAME>";
302302
```
303303
304-
You can get event hub namespace associated with your Purview account by looking at your Atlas kafka endpoint primary/secondary connection strings. This can be found in the **Properties** tab of your Purview account.
304+
You can get event hub namespace associated with your Microsoft Purview account by looking at your Atlas kafka endpoint primary/secondary connection strings. This can be found in the **Properties** tab of your Microsoft Purview account.
305305
306306
:::image type="content" source="media/manage-eventhub-kafka-dotnet/properties.png" alt-text="A screenshot that shows an Event Hubs Namespace.":::
307307
308-
Use **ATLAS_ENTITIES** as the event hub name when sending messages to Purview.
308+
Use **ATLAS_ENTITIES** as the event hub name when sending messages to Microsoft Purview.
309309
310310
3. Replace the `Main` method with the following `async Main` method. See the comments in the code for details.
311311
@@ -361,7 +361,7 @@ We'll use Azure Storage as the checkpoint store. Use the following steps to crea
361361
> For the complete source code with more informational comments, see [this file on the GitHub](https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/eventhub/Azure.Messaging.EventHubs.Processor/samples/Sample01_HelloWorld.md).
362362
6. Run the receiver application.
363363
364-
### An example of a Message received from Purview
364+
### An example of a Message received from Microsoft Purview
365365
366366
```json
367367
{

0 commit comments

Comments
 (0)