From 9980d7517bdd87f0c06c376c1bb275fb1deb5736 Mon Sep 17 00:00:00 2001 From: Yaron Schneider Date: Fri, 5 Jun 2020 15:13:28 -0700 Subject: [PATCH] Update setup-azure-eventhubs.md (#629) --- howto/setup-pub-sub-message-broker/setup-azure-eventhubs.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/howto/setup-pub-sub-message-broker/setup-azure-eventhubs.md b/howto/setup-pub-sub-message-broker/setup-azure-eventhubs.md index a1b8215ef..46ca7c41b 100644 --- a/howto/setup-pub-sub-message-broker/setup-azure-eventhubs.md +++ b/howto/setup-pub-sub-message-broker/setup-azure-eventhubs.md @@ -32,6 +32,11 @@ See [here](https://docs.microsoft.com/en-us/azure/event-hubs/authorize-access-sh The above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described [here](../../concepts/secrets/README.md) +## Create consumer groups for each subscriber + +For every Dapr app that wants to subscribe to events, create an Event Hubs consumer group with the name of the `dapr id`. +For example, a Dapr app running on Kubernetes with `dapr.io/id: "myapp"` will need an Event Hubs consumer group named `myapp`. + ## Apply the configuration ### In Kubernetes