Merge pull request #312024 from spelluru/asafreshness0218

Azure Stream Analytics - Freshness Review

Author: Carolyn135

articles/stream-analytics/includes/event-generator-app.md

@@ -1,16 +1,11 @@
 ---
-title: include file
-description: include file
+title: Event generator application
+description: This include file has steps for creating an event hub, event generator application, and Stream Analytics job to analyze the data generated by the event generator application.
 author: spelluru
 ms.service: azure-stream-analytics
 ms.topic: include
-ms.date: 02/14/2024
+ms.date: 02/19/2026
 ms.author: spelluru
-ms.custom:
-  - "include file"
-  - sfi-image-nochange
-  - sfi-ropc-nochange
-
 ---
 
 ## Sign in to Azure
@@ -38,10 +33,10 @@ Use the following steps to create an event hub and send call data to that event
         :::image type="content" source="media/event-generator-app/create-event-hub-namespace.png" alt-text="Screenshot showing the Create Namespace page.":::
     1. On the **Review + create** page of the namespace creation wizard, select **Create** at the bottom of the page after reviewing all settings. 
 5. After the namespace is deployed successfully, select **Go to resource** to navigate to the **Event Hubs Namespace** page.
-6. On the **Event Hubs Namespace** page, select **+Event Hub** on the command bar.
+6. On the **Event Hubs namespace** page, select **+Event Hub** on the command bar.
 
     :::image type="content" source="media/event-generator-app/add-event-hub-button.png" alt-text="Screenshot showing the Add event hub button on the Event Hubs Namespace page.":::    
-1. On the **Create Event Hub** page, enter a **Name** for the event hub. Set the **Partition Count** to 2.  Use the default options in the remaining settings and select **Review + create**. 
+1. On the **Create Event Hub** page, enter a **Name** for the event hub. Set the **Partition Count** to 2. Use the default options in the remaining settings and select **Review + create**. 
 
     :::image type="content" source="media/event-generator-app/create-event-hub-portal.png" alt-text="Screenshot showing the Create event hub page.":::    
 1. On the **Review + create** page, select **Create** at the bottom of the page. Then wait for the deployment to succeed.
@@ -50,7 +45,7 @@ Use the following steps to create an event hub and send call data to that event
 
 Before an application can send data to Azure Event Hubs, the event hub must have a policy that allows access. The access policy produces a connection string that includes authorization information.
 
-1. On the **Event Hubs Namespace** page, select **Shared access policies** on the left menu.
+1. On the **Event Hubs namespace** page, select **Shared access policies** on the left menu.
 1. Select **RootManageSharedAccessKey** from the list of policies. 
 
     :::image type="content" source="media/event-generator-app/select-key.png" alt-text="Screenshot that shows the Shared access policies page.":::
@@ -71,7 +66,7 @@ Before you start the TelcoGenerator app, you should configure it to send data to
 2. Open the `TelcoGenerator\TelcoGenerator\telcodatagen.exe.config` file in a text editor of your choice There's more than one `.config` file, so be sure that you open the correct one.
 3. Update the `<appSettings>` element in the config file with the following details:
 
-   * Set the value of the **EventHubName** key to the value of the **EntityPath** at the end of the connection string.
+   * Set the value of the **EventHubName** key to the name of the event hub you created in the previous section.
    * Set the value of the **Microsoft.ServiceBus.ConnectionString** key to the connection string to the namespace. If you use a connection string to an event hub, not a namespace, remove `EntityPath` value (`;EntityPath=myeventhub`) at the end. **Don't forget** to remove the semicolon that precedes the EntityPath  value. 
 4. Save the file.
 5. Next open a command window and change to the folder where you unzipped the TelcoGenerator application. Then enter the following command:
@@ -101,7 +96,9 @@ Before you start the TelcoGenerator app, you should configure it to send data to
 Now that you have a stream of call events, you can create a Stream Analytics job that reads data from the event hub.
 
 1. To create a Stream Analytics job, navigate to the [Azure portal](https://portal.azure.com/).
-2. Select **Create a resource** and search for **Stream Analytics job**. Select the **Stream Analytics job** tile and select **Create**.
+1. Select **All services** in the left menu, search for **Stream Analytics jobs**, hover the mouse over the **Stream Analytics jobs** tile, and then select **+** button or select **Create** in the pop-up window.
+
+    :::image type="content" source="media/event-generator-app/find-stream-analytics-resource.png" alt-text="Screenshot showing how to find Stream Analytics in the Azure portal.":::
 1. On the **New Stream Analytics job** page, follow these steps:
     1. For **Subscription**, select the subscription that contains the Event Hubs namespace.
     1. For **Resource group**, select the resource group you created earlier.
@@ -130,7 +127,7 @@ The next step is to define an input source for the job to read data using the ev
     1. For **Event hub name**, select the event hub you created in the previous section. All the event hubs available in the selected namespace are listed in the dropdown.
     1. For **Event hub consumer group**, keep the **Create new** option selected so that a new consumer group is created on the event hub. We recommend that you use a distinct consumer group for each Stream Analytics job. If no consumer group is specified, the Stream Analytics job uses the `$Default` consumer group. When a job contains a self-join or has multiple inputs, some inputs later might be read by more than one reader. This situation affects the number of readers in a single consumer group.
     1. For **Authentication mode**, select **Connection string**. It's easier to test the tutorial with this option.  
-    1. For **Event hub policy name**, select **Use existing**, and then select the policy you created earlier. 
+    1. For **Event hub policy name**, select **Use existing**, and then select the default policy: **RootManageSharedAccessKey**. 
     1. Select **Save** at the bottom of the page. 
 
         :::image type="content" source="media/event-generator-app/configure-stream-analytics-input.png" alt-text="Screenshot showing the Event Hubs configuration page for an input.":::