Freshness, in progress.

Author: TimShererWithAquent

articles/event-hubs/event-hubs-node-get-started-send.md

@@ -1,30 +1,31 @@
 ---
-title: Send or receive events using JavaScript
-description: This article provides a walkthrough for creating a JavaScript application that sends/receives events to/from Azure Event Hubs.
+title: 'Quickstart: Send or receive events using JavaScript'
+description: This article provides a walkthrough for creating JavaScript applications that send or receive events to and from Azure Event Hubs.
 ms.topic: quickstart
-ms.date: 04/05/2024
+ms.date: 06/13/2025
 ms.devlang: javascript
 ms.custom: devx-track-js, mode-api, passwordless-js
 #customer intent: As a JavaScript developer, I want to learn how to send events to an event hub and receive events from the event hub using C#. 
 ---
 
 # Quickstart: Send events to or receive events from event hubs by using JavaScript
-In this Quickstart, you learn how to send events to and receive events from an event hub using the **@azure/event-hubs** npm package. 
 
+In this Quickstart, you learn how to send events to and receive events from an event hub using the **@azure/event-hubs** npm package. 
 
 ## Prerequisites
+
 If you're new to Azure Event Hubs, see [Event Hubs overview](event-hubs-about.md) before you do this quickstart. 
 
 To complete this quickstart, you need the following prerequisites:
 
 - **Microsoft Azure subscription**. To use Azure services, including Azure Event Hubs, you need a subscription. If you don't have an existing Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
 - Node.js LTS. Download the latest [long-term support (LTS) version](https://nodejs.org).  
 - Visual Studio Code (recommended) or any other integrated development environment (IDE).  
-- **Create an Event Hubs namespace and an event hub**. The first step is to use the [Azure portal](https://portal.azure.com) to create a namespace of type Event Hubs, and obtain the management credentials your application needs to communicate with the event hub. To create a namespace and an event hub, follow the procedure in [this article](event-hubs-create.md). 
+- **Create an Event Hubs namespace and an event hub**. The first step is to use the [Azure portal](https://portal.azure.com) to create a namespace of type Event Hubs, and obtain the management credentials your application needs to communicate with the event hub. For more information, see [Create an event hub using Azure portal](event-hubs-create.md). 
 
 ### Install npm packages to send events
-To install the [Node Package Manager (npm) package for Event Hubs](https://www.npmjs.com/package/@azure/event-hubs), open a command prompt that has *npm* in its path, change the directory
-to the folder where you want to keep your samples.
+
+To install the [Node Package Manager (npm) package for Event Hubs](https://www.npmjs.com/package/@azure/event-hubs), open a command prompt that has `npm` in its path, change the directory to the folder where you want to keep your samples.
 
 ### [Passwordless (Recommended)](#tab/passwordless)
 
@@ -59,8 +60,9 @@ In this section, you create a JavaScript application that sends events to an eve
    ## [Passwordless (Recommended)](#tab/passwordless)
 
     In the code, use real values to replace the following placeholders:
-    * `EVENT HUBS NAMESPACE NAME`
-    * `EVENT HUB NAME`
+
+    - `EVENT HUBS NAMESPACE NAME`
+    - `EVENT HUB NAME`
 
     ```javascript
     const { EventHubProducerClient } = require("@azure/event-hubs");
@@ -102,8 +104,9 @@ In this section, you create a JavaScript application that sends events to an eve
    ## [Connection String](#tab/connection-string)
 
     In the code, use real values to replace the following placeholders:
-    * `EVENT HUB NAME`
-    * `EVENT HUBS NAMESPACE CONNECTION STRING`
+
+    - `EVENT HUB NAME`
+    - `EVENT HUBS NAMESPACE CONNECTION STRING`
 
     ```javascript
     const { EventHubProducerClient } = require("@azure/event-hubs");
@@ -138,35 +141,36 @@ In this section, you create a JavaScript application that sends events to an eve
 
     ---
 
-1. Run `node send.js` to execute this file. This command sends a batch of three events to your event hub. If you're using the Passwordless (Azure Active Directory's Role-based Access Control) authentication, you might want to run `az login` and sign into Azure using the account that was added to the Azure Event Hubs Data Owner role. 
-1. In the Azure portal, verify that the event hub received the messages. Refresh the page to update the chart. It might take a few seconds for it to show that the messages are received.
+1. To run this file, enter `node send.js`. This command sends a batch of three events to your event hub. If you're using the passwordless (Microsoft Entra ID Role-based access control (RBAC)) authentication, you might want to run `az login` and sign into Azure using the account that was added to the Azure Event Hubs Data Owner role. 
+1. In the Azure portal, verify that the event hub received the messages. To update the chart, refresh the page. It might take a few seconds for it to show that the messages are received.
 
-    [![Verify that the event hub received the messages](./media/node-get-started-send/verify-messages-portal.png)](./media/node-get-started-send/verify-messages-portal.png#lightbox)
+   :::image type="content" source="./media/node-get-started-send/verify-messages-portal.png" alt-text="Screenshot shows the Overview page where you can verify that the event hub received the message." lightbox="./media/node-get-started-send/verify-messages-portal.png":::
 
-    > [!NOTE]
-    > For the complete source code, including additional informational comments, go to the [GitHub sendEvents.js page](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/eventhub/event-hubs/samples/v5/javascript/sendEvents.js).
 
+   > [!NOTE]
+   > For more information and the complete source code, see [GitHub sendEvents.js page](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/eventhub/event-hubs/samples/v5/javascript/sendEvents.js).
     
 ## Receive events
+
 In this section, you receive events from an event hub by using an Azure Blob storage checkpoint store in a JavaScript application. It performs metadata checkpoints on received messages at regular intervals in an Azure Storage blob. This approach makes it easy to continue receiving messages later from where you left off.
 
 [!INCLUDE [storage-checkpoint-store-recommendations](./includes/storage-checkpoint-store-recommendations.md)]
 
-
 ### Create an Azure storage account and a blob container
+
 To create an Azure storage account and a blob container in it, do the following actions:
 
 1. [Create an Azure storage account](../storage/common/storage-account-create.md?tabs=azure-portal)  
-2. [Create a blob container in the storage account](../storage/blobs/storage-quickstart-blobs-portal.md#create-a-container)  
-3. Authenticate to the blob container
+1. [Create a blob container in the storage account](../storage/blobs/storage-quickstart-blobs-portal.md#create-a-container)  
+1. Authenticate to the blob container
     
 ## [Passwordless (Recommended)](#tab/passwordless)
 
 [!INCLUDE [event-hub-storage-assign-roles](../../includes/passwordless/event-hub/event-hub-storage-assign-roles.md)]
     
 ## [Connection String](#tab/connection-string)
 
-[Get the connection string to the storage account](../storage/common/storage-configure-connection-string.md).
+Get the connection string to the storage account. See [Configure Azure Storage connection strings](../storage/common/storage-configure-connection-string.md).
 
 Note the connection string and the container name. You use them in the code to receive events. 
 
@@ -205,6 +209,7 @@ npm install @azure/eventhubs-checkpointstore-blob
     ### [Passwordless (Recommended)](#tab/passwordless)
 
     In the code, use real values to replace the following placeholders:
+
     - `EVENT HUBS NAMESPACE NAME`
     - `EVENT HUB NAME`
     - `STORAGE ACCOUNT NAME`
@@ -281,8 +286,8 @@ npm install @azure/eventhubs-checkpointstore-blob
 
     ### [Connection String](#tab/connection-string)
 
-
     In the code, use real values to replace the following placeholders:
+
     - `EVENT HUBS NAMESPACE CONNECTION STRING`
     - `EVENT HUB NAME`
     - `STORAGE CONNECTION STRING`
@@ -346,8 +351,7 @@ npm install @azure/eventhubs-checkpointstore-blob
 
     ---
 
-
-1. Run `node receive.js` in a command prompt to execute this file. The window should display messages about received events.
+1. To run this file, enter `node receive.js`. The window should display messages about received events.
 
     ```bash
     C:\Self Study\Event Hubs\JavaScript>node receive.js
@@ -357,14 +361,16 @@ npm install @azure/eventhubs-checkpointstore-blob
     ```
 
     > [!NOTE]
-    > For the complete source code, including additional informational comments, go to the [GitHub receiveEventsUsingCheckpointStore.js page](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/eventhub/eventhubs-checkpointstore-blob/samples/v1/javascript/receiveEventsUsingCheckpointStore.js).
+    > For the complete source code, including additional informational comments, see [receiveEventsUsingCheckpointStore.js](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/eventhub/eventhubs-checkpointstore-blob/samples/v1/javascript/receiveEventsUsingCheckpointStore.js).
 
     The receiver program receives events from all the partitions of the default consumer group in the event hub.
 
 ## Clean up resources
+
 Delete the resource group that has the Event Hubs namespace or delete only the namespace if you want to keep the resource group. 
 
 ## Related content
+
 Check out these samples on GitHub:
 
 - [JavaScript samples](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/eventhub/event-hubs/samples/v5/javascript)

articles/event-hubs/includes/storage-checkpoint-store-recommendations.md

@@ -4,7 +4,7 @@ description: Provides recommendations when using Azure Blob Storage as a checkpo
 author: spelluru
 ms.service: azure-event-hubs
 ms.topic: include
-ms.date: 02/15/2024
+ms.date: 06/13/2025
 ms.author: spelluru
 ms.custom: "include file"
 ---

articles/event-hubs/media/node-get-started-send/verify-messages-portal.png

@@ -5,16 +5,17 @@ services: storage
 author: alexwolfmsft
 ms.service: azure-storage
 ms.topic: include
-ms.date: 09/09/2022
+ms.date: 06/13/2025
 ms.author: alexwolf
 ms.custom: include file
 ---
 
-When developing locally, make sure that the user account that connects to Azure Event Hubs has the correct permissions. You'll need the [Azure Event Hubs Data Owner](../../../articles/role-based-access-control/built-in-roles.md#azure-event-hubs-data-owner) role in order to send and receive messages. To assign yourself this role, you'll need the User Access Administrator role, or another role that includes the `Microsoft.Authorization/roleAssignments/write` action. You can assign Azure RBAC roles to a user using the Azure portal, Azure CLI, or Azure PowerShell. Learn more about the available scopes for role assignments on the [scope overview](../../../articles/role-based-access-control/scope-overview.md) page.
+When developing locally, make sure that the user account that connects to Azure Event Hubs has the correct permissions. You need the [Azure Event Hubs Data Owner](../../../articles/role-based-access-control/built-in-roles.md#azure-event-hubs-data-owner) role in order to send and receive messages. To assign yourself this role, you need the User Access Administrator role, or another role that includes the `Microsoft.Authorization/roleAssignments/write` action. You can assign Azure RBAC roles to a user using the Azure portal, Azure CLI, or Azure PowerShell. For more information about the available scopes for role assignments, see [Understand scope for Azure RBAC](../../../articles/role-based-access-control/scope-overview.md) page.
 
 The following example assigns the `Azure Event Hubs Data Owner` role to your user account, which provides full access to Azure Event Hubs resources. In a real scenario, follow the [Principle of Least Privilege](../../../articles/active-directory/develop/secure-least-privileged-access.md) to give users only the minimum permissions needed for a more secure production environment.
 
 ### Azure built-in roles for Azure Event Hubs
+
 For Azure Event Hubs, the management of namespaces and all related resources through the Azure portal and the Azure resource management API is already protected using the Azure RBAC model. Azure provides the below Azure built-in roles for authorizing access to an Event Hubs namespace:
 
 - [Azure Event Hubs Data Owner](../../../articles/role-based-access-control/built-in-roles.md#azure-event-hubs-data-owner): Enables data access to Event Hubs namespace and its entities (queues, topics, subscriptions, and filters)
@@ -24,27 +25,27 @@ For Azure Event Hubs, the management of namespaces and all related resources thr
 If you want to create a custom role, see [Rights required for Event Hubs operations](../../../articles/service-bus-messaging/service-bus-sas.md#rights-required-for-service-bus-operations).
 
 > [!IMPORTANT]
-> In most cases, it will take a minute or two for the role assignment to propagate in Azure. In rare cases, it may take up to eight minutes. If you receive authentication errors when you first run your code, wait a few moments and try again.
+> In most cases, it takes a minute or two for the role assignment to propagate in Azure. In rare cases, it might take up to eight minutes. If you receive authentication errors when you first run your code, wait a few moments and try again.
 
 ### [Azure portal](#tab/roles-azure-portal)
 
 1. In the Azure portal, locate your Event Hubs namespace using the main search bar or left navigation.
 
-2. On the overview page, select **Access control (IAM)** from the left-hand menu.	
+1. On the overview page, select **Access control (IAM)** from the left-hand menu.	
 
-3. On the **Access control (IAM)** page, select the **Role assignments** tab.
+1. On the **Access control (IAM)** page, select the **Role assignments** tab.
 
-4. Select **+ Add** from the top menu and then **Add role assignment** from the resulting drop-down menu.
+1. Select **+ Add** from the top menu and then **Add role assignment** from the resulting drop-down menu.
 
-    :::image type="content" source="media/event-hub-assign-roles/add-role.png" alt-text="A screenshot showing how to assign a role.":::    
+    :::image type="content" source="media/event-hub-assign-roles/add-role.png" alt-text="Screenshot showing how to assign a role.":::    
 
-5. Use the search box to filter the results to the desired role. For this example, search for `Azure Event Hubs Data Owner` and select the matching result. Then choose **Next**.
+1. Use the search box to filter the results to the desired role. For this example, search for `Azure Event Hubs Data Owner` and select the matching result. Then choose **Next**.
 
-6. Under **Assign access to**, select **User, group, or service principal**, and then choose **+ Select members**.
+1. Under **Assign access to**, select **User, group, or service principal**, and then choose **+ Select members**.
 
-7. In the dialog, search for your Microsoft Entra username (usually your *user@domain* email address) and then choose **Select** at the bottom of the dialog. 
+1. In the dialog, search for your Microsoft Entra username (usually your *user@domain* email address) and then choose **Select** at the bottom of the dialog. 
 
-8. Select **Review + assign** to go to the final page, and then **Review + assign** again to complete the process.
+1. Select **Review + assign** to go to the final page, and then **Review + assign** again to complete the process.
 
 ### [Azure CLI](#tab/roles-azure-cli)
 

articles/storage/common/media/assign-role-system-identity.png

@@ -5,12 +5,12 @@ services: storage
 author: diberry
 ms.service: azure-storage
 ms.topic: include
-ms.date: 09/09/2022
+ms.date: 06/13/2025
 ms.author: diberry
 ms.custom: include file
 ---
 
-This quickstart shows you two ways of connecting to Azure Event Hubs: passwordless and connection string. The first option shows you how to use your security principal in Microsoft Entra ID and role-based access control (RBAC) to connect to an Event Hubs namespace. You don't need to worry about having hard-coded connection strings in your code or in a configuration file or in a secure storage like Azure Key Vault. The second option shows you how to use a connection string to connect to an Event Hubs namespace. If you're new to Azure, you may find the connection string option easier to follow. We recommend using the passwordless option in real-world applications and production environments. For more information, see [Authentication and authorization](../../../articles/service-bus-messaging/service-bus-authentication-and-authorization.md). You can also read more about passwordless authentication on the [overview page](/azure/developer/intro/passwordless-overview).
+This quickstart shows you two ways of connecting to Azure Event Hubs: passwordless and connection string. The first option shows you how to use your security principal in Microsoft Entra ID and role-based access control (RBAC) to connect to an Event Hubs namespace. You don't need to worry about having hard-coded connection strings in your code, in a configuration file, or in secure storage like Azure Key Vault. The second option shows you how to use a connection string to connect to an Event Hubs namespace. If you're new to Azure, you might find the connection string option easier to follow. We recommend using the passwordless option in real-world applications and production environments. For more information, see [Service Bus authentication and authorization](../../../articles/service-bus-messaging/service-bus-authentication-and-authorization.md). For more information, see [Passwordless connections for Azure services](/azure/developer/intro/passwordless-overview).
 
 ## [Passwordless (Recommended)](#tab/passwordless)
 
@@ -20,21 +20,20 @@ This quickstart shows you two ways of connecting to Azure Event Hubs: passwordle
 
 [!INCLUDE [event-hub-assign-roles](event-hub-assign-roles.md)]
 
-
-
 ## [Connection String](#tab/connection-string)
 
 ## Get the connection string 
+
 Creating a new namespace automatically generates an initial Shared Access Signature (SAS) policy with primary and secondary keys and connection strings that each grant full control over all aspects of the namespace. See [Event Hubs authentication and authorization](../../../articles/service-bus-messaging/service-bus-authentication-and-authorization.md) for information about how to create rules with more constrained rights for regular senders and receivers. 
 
 A client can use the connection string to connect to the Event Hubs namespace. To copy the primary connection string for your namespace, follow these steps: 
 
 1. On the **Event Hub Namespace** page, select **Shared access policies** on the left menu.
-3. On the **Shared access policies** page, select **RootManageSharedAccessKey**.
-4. In the **Policy: RootManageSharedAccessKey** window, select the copy button next to **Primary Connection String**, to copy the connection string to your clipboard for later use. Paste this value into Notepad or some other temporary location.
+1. On the **Shared access policies** page, select **RootManageSharedAccessKey**.
+1. In the **Policy: RootManageSharedAccessKey** window, select the copy button next to **Primary Connection String**, to copy the connection string to your clipboard for later use. Paste this value into Notepad or some other temporary location.
 
-    :::image type="content" source="./media/event-hub-passwordless-template-tabbed/connection-string.png"alt-text="Screenshot shows an SAS policy called RootManageSharedAccessKey, which includes keys and connection strings.":::
+   :::image type="content" source="./media/event-hub-passwordless-template-tabbed/connection-string.png" alt-text="Screenshot shows an SAS policy called RootManageSharedAccessKey, which includes keys and connection strings.":::
 
-    You can use this page to copy primary key, secondary key, primary connection string, and secondary connection string. 
+   You can use this page to copy primary key, secondary key, primary connection string, and secondary connection string. 
 
 ---