Fn + SignalR - updates

Author: diberry

learn-pr/advocates/automatic-update-of-a-webapp-using-azure-functions-and-signalr/3-exercise-analyze-limitations-of-polling-in-a-web-app.yml

@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise - Analyze the limitations of a polling-based web app
   description: Review the implementation of polling website and run the app on your machine.
-  ms.date: 08/12/2024
+  ms.date: 01/22/2025
   author: craigshoemaker
   ms.author: cshoe
   ms.topic: unit

learn-pr/advocates/automatic-update-of-a-webapp-using-azure-functions-and-signalr/5-exercise-enable-automatic-updates-in-a-web-app-using-signalr.yml

@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise – Enable automatic updates in a web application using SignalR Service
   description: Implement integration with Azure Functions and SignalR Service for fast and targeted automatic updates.
-  ms.date: 08/12/2024
+  ms.date: 01/22/2025
   author: craigshoemaker
   ms.author: cshoe
   ms.topic: unit

learn-pr/advocates/automatic-update-of-a-webapp-using-azure-functions-and-signalr/includes/3-exercise-analyze-limitations-of-polling-in-a-web-app.md

@@ -4,16 +4,16 @@ Before you change the prototype, you need to run it to validate the assumptions.
 
 1. In a separate browser tab or window, fork the sample repository on GitHub with the following link: [mslearn-advocates.azure-functions-and-signalr](https://github.com/MicrosoftDocs/mslearn-advocates.azure-functions-and-signalr/fork). This allows you to push your changes to your own version of the source code. This is a required step in order to deploy the source code to Azure later in the module.
 
-1. In the terminal, clone the repository. In the following command, replace `MicrosoftDocs` with your account:
+1. In the terminal, clone your forked repository. In the following command, replace `MicrosoftDocs` with your account:
 
     ```bash
-    git clone https://github.com/MicrosoftDocs/mslearn-advocates.azure-functions-and-signalr stock-prototype
+    git clone https://github.com/<YOUR-GITHUB-ALIAS>/mslearn-advocates.azure-functions-and-signalr stock-prototype
     ```
 
 1. Install the dependencies in the **setup-resources** folder.
 
     ```bash
-    cd stock-prototype/setup-resources && npm install
+    cd setup-resources && npm install
     ```
 
     If you receive warnings about `EBADENGINE`,  you can ignore them.
@@ -81,7 +81,7 @@ Before you change the prototype, you need to run it to validate the assumptions.
 
 1. If you receive a notification about installing the latest Azure Functions Core Tools, select **Install**.
 
-## Get the client and server URLs
+## Know the client and server URLs
 
 When running locally, the client and server applications need to know where to find each other. The URLs are:
 
@@ -152,6 +152,6 @@ BACKEND_URL=http://localhost:7071
 
     :::image type="content" source="../media/visual-studio-code-terminal-output-stock-change.png" alt-text="Screenshot of Visual Studio Code terminal showing console output of the stock price change.":::
 
-1. In both the start-client and start server terminals, stop the applications with <kbd>Ctrl</kbd> + <kbd>C</kbd> or kill the terminal by selecting the trashcan icon.
+1. In both the terminals for client and server, stop the applications with <kbd>Ctrl</kbd> + <kbd>C</kbd> or kill the terminal by selecting the trashcan icon.
 
 In this unit, you ran the prototype. While the client does run successfully, it isn't efficient. While each individual client may not notice this with such a small number of stocks, that will change as the number of stocks grows and the number of clients pull from the server. The prototype can be improved. Let's learn how in the next unit.

learn-pr/advocates/automatic-update-of-a-webapp-using-azure-functions-and-signalr/includes/5-exercise-enable-automatic-updates-in-a-web-app-using-signalr.md

@@ -12,7 +12,7 @@ You need to create an Azure SignalR resource.
 1. Navigate to the `setup-resources` subdirectory to create the resource.
 
     ```bash
-    cd stock-prototype/setup-resources && bash create-signalr-resources.sh & cd ..
+    cd setup-resources && bash create-signalr-resources.sh & cd ..
     ```
 
 1. Copy the connection string for the SignalR resource. You'll need this to update the server code.
@@ -97,14 +97,15 @@ Create a function app and related resources in Azure to which you can publish th
 
     | Name                                   | Value                          |
     | -------------------------------------- | ------------------------------ |
+    | Hosting                                | Select **Consumption Plan**.|
     | Resource group                         | Create a new resource group names `stock-prototype`.|
     | Function App name                      | Postpend your name to `api`. For example, `api-jamie`.|
     | Code or container                          | Select **code**.                       |
     | Runtime stack                        | Select **Node.js**.                       |
     | Version            |  Select an LTS version of Node.js.                    |
     | Region  | Select a region close to you.                           |
     | Operating System | Select **Linux**.|
-    | Hosting | Select **Consumption Plan**.|
+
 
 1. Don't fill out any other tabs and select **Review + create** then select **Create**. Wait for the deployment to complete before continuing.
 1. Select **Go to resource** to open the new function app.
@@ -137,7 +138,8 @@ At this point, your GitHub deployment might generate an error because of a wrong
 
 1. In your new function app page in the Azure portal, select your resource group in **Overview** > **Essentials**, then select the managed identity under **Resources**. This managed identity was created by Functions when you enabled the GitHub deployment.  
 1. In the **Managed Identity** page, select **Settings** > **Federated credentials** and then select the existing credential.
-1. In **Connect your Github account**, change the setting for **Entity** to **Environment** and enter `Production` for **Environment**.  
+1. In **Connect your Github account**, change these settings:
+    * **Entity**: from **Branch** to **Environment**
 1. Select **Update** to update the credential.
 <!--- end removal section -->
 
@@ -182,7 +184,7 @@ At this point, your GitHub deployment might generate an error because of a wrong
 
 ## Configure the environment variables for the API functions
 
-1. In the Azure portal, locate your function app and select **Settings** > **Configuration** then select **New application setting**.
+1. In the Azure portal, locate your function app and select **Settings** > **Environment variables** then select **+ Add**.
 1. Enter the settings for the Cosmos DB and SignalR connection strings. You can find the values in the `local.settings.json` in the `start/server` folder. 
 
     | Name | Value |