Skip to content

Commit 2cb2ed8

Browse files
committed
Resolving links
1 parent c0c3042 commit 2cb2ed8

File tree

2 files changed

+1
-15
lines changed

2 files changed

+1
-15
lines changed

articles/purview/configure-event-hubs-for-kafka.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ One of these identities will need **at least contributor permissions on your Eve
7777

7878
:::image type="content" source="media/configure-event-hubs-for-kafka/select-kafka-configuration.png" alt-text="Screenshot showing the Kafka configuration option in the Microsoft Purview menu in the Azure portal.":::
7979

80-
1. If there's a configuration already listed as type **Notification**, Event Hubs is already configured, and you can begin the steps to [receive Microsoft Purview messages](#receive-microsoft-purview-messages).
80+
1. If there's a configuration already listed as type **Notification**, Event Hubs is already configured, and you can begin the steps to [receive Microsoft Purview messages](manage-kafka-dotnet.md#receive-microsoft-purview-messages).
8181
>[!NOTE]
8282
> Only one *Notification* Event Hubs can be configured at a time.
8383

articles/purview/manage-kafka-dotnet.md

Lines changed: 0 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -297,10 +297,6 @@ We'll use Azure Storage as the checkpoint store. Use the following steps to crea
297297
private const string blobContainerName = "<BLOB CONTAINER NAME>";
298298
```
299299
300-
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.
301-
302-
:::image type="content" source="media/manage-eventhub-kafka-dotnet/properties.png" alt-text="A screenshot that shows an Event Hubs Namespace.":::
303-
304300
Use **ATLAS_ENTITIES** as the event hub name when sending messages to Microsoft Purview.
305301
306302
1. Replace the `Main` method with the following `async Main` method. See the comments in the code for details.
@@ -396,16 +392,6 @@ We'll use Azure Storage as the checkpoint store. Use the following steps to crea
396392
}
397393
```
398394

399-
## Remove configured Event Hubs
400-
401-
To remove configured Event Hubs namespaces, you can follow these steps:
402-
403-
1. Search for and open your Microsoft Purview account in the [Azure portal](https://portal.azure.com).
404-
1. Select **Kafka configuration** under settings on your Microsoft Purview account page in the Azure portal.
405-
1. Select the Event Hubs you want to disable. (Hook hubs send messages to Microsoft Purview. Notification hubs receive notifications.)
406-
1. Select **Remove** to save the choice and begin the disablement process. This can take several minutes to complete.
407-
:::image type="content" source="media/manage-eventhub-kafka-dotnet/select-remove.png" alt-text="Screenshot showing the Kafka configuration page of the Microsoft Purview account page in the Azure portal with the remove button highlighted.":::
408-
409395
## Next steps
410396

411397
Check out more examples in GitHub.

0 commit comments

Comments
 (0)