Skip to content

Commit d3665f7

Browse files
committed
reviewed, tested for accuracy
1 parent d43285b commit d3665f7

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/event-hubs/event-hubs-get-connection-string.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
11
---
2-
title: Get connection string - Azure Event Hubs | Microsoft Docs
2+
title: Get connection string - Azure Event Hubs
33
description: This article provides instructions for getting a connection string that clients can use to connect to Azure Event Hubs.
44
ms.topic: article
55
ms.custom: devx-track-azurepowershell, devx-track-azurecli
6-
ms.date: 06/21/2022
6+
ms.date: 07/28/2023
77
---
88

99
# Get an Event Hubs connection string
1010
To communicate with an event hub in a namespace, you need a connection string for the namespace or the event hub. If you use a connection string to the namespace from your application, the application will have the provided access (manage, read, or write) to all event hubs in the namespace. If you use a connection string to the event hub, you will have the provided access to that specific event hub.
1111

1212
The connection string for a namespace has the following components embedded within it,
1313

14-
* Fully qualified domain name of the Event Hubs namespace you created (it includes the Event Hubs namespace name followed by servicebus.windows.net)
14+
* Fully qualified domain name of the Event Hubs namespace you created (it includes the Event Hubs namespace name followed by `servicebus.windows.net`)
1515
* Name of the shared access key
1616
* Value of the shared access key
1717

@@ -50,7 +50,7 @@ This section gives you steps for getting a connection string to a specific event
5050

5151
1. On the **Event Hubs Namespace** page, select the event hub in the bottom pane.
5252
1. On the **Event Hubs instance** page, select **Shared access policies** on the left menu.
53-
1. There's no default policy created for an event hub. Create a policy with **Manage**, **Send, or **Listen** access.
53+
1. There's no default policy created for an event hub. Create a policy with **Manage**, **Send**, or **Listen** access.
5454
1. Select the policy from the list.
5555
1. Select the **copy** button next to the **Connection string-primary key** field.
5656

0 commit comments

Comments
 (0)