Merge pull request #266613 from vicancy/patch-12

Update signalr-concept-authenticate-oauth.md

Author: prmerger-automator[bot]

articles/azure-signalr/signalr-concept-authenticate-oauth.md

@@ -4,7 +4,7 @@ description: Learn how to implement your own authentication and integrate it wit
 author: vicancy
 ms.service: signalr
 ms.topic: conceptual
-ms.date: 11/13/2023
+ms.date: 02/18/2024
 ms.author: lianwei
 ms.devlang: csharp
 ms.custom: devx-track-csharp, devx-track-azurecli
@@ -205,10 +205,9 @@ In this section, you implement a `Login` API that authenticates clients using th
 
 ### Update the Hub class
 
-By default, web client connects to SignalR Service using an internal access. This access token isn't associated with an authenticated identity.
-Basically, it's anonymous access.
+By default, web client connects to SignalR Service using an access token generated by the Azure SignalR SDK automatically.
 
-In this section, you turn on real authentication by adding the `Authorize` attribute to the hub class, and updating the hub methods to read the username from the authenticated user's claim.
+In this section, you integrate the real authentication workflow by adding the `Authorize` attribute to the hub class, and update the hub methods to read the username from the authenticated user's claim.
 
 1. Open _Hub\ChatSampleHub.cs_ and update the code to the below code snippet. The code adds the `Authorize` attribute to the `ChatSampleHub` class, and uses the user's authenticated identity in the hub methods. Also, the `OnConnectedAsync` method is added, which logs a system message to the chat room each time a new client connects.
 

articles/azure-signalr/signalr-quickstart-azure-signalr-service-arm-template.md

@@ -65,7 +65,7 @@ On the **Deploy an Azure SignalR Service** page:
 
 3. If you created a new resource group, select a **Region** for the resource group.
 
-4. If you want, enter a new **Name** and the **Location** (For example **eastus2**) of the Azure SignalR Service. If you don't specify a name, it generates automatically. The Azure SignalR Service's location can be the same or different from the region of the resource group. If you don't specify a location, it defaults to the same region as your resource group.
+4. If you want, enter a new **Name** and the **Location** (For example **eastus2**) of the Azure SignalR Service. If **Name** is not specified, it is generated automatically. The **Location** can be the same or different from the region of the resource group. If **Location** is not specified, it defaults to the same region as your resource group.
 
 5. Choose the **Pricing Tier** (**Free_F1** or **Standard_S1**), enter the **Capacity** (number of SignalR units), and choose a **Service Mode** of **Default** (requires hub server), **Serverless** (doesn't allow any server connection), or **Classic** (routed to hub server only if hub has server connection). Now, choose whether to **Enable Connectivity Logs** or **Enable Messaging Logs**.
 

articles/azure-signalr/signalr-tutorial-build-blazor-server-chat-app.md

@@ -419,7 +419,7 @@ When you deploy the Blazor app to Azure App Service, we recommend that you use [
 1. Add a reference to the Azure SignalR SDK using the following command.
 
    ```dotnetcli
-   dotnet add package Microsoft.Azure.SignalR --version 1.5.1
+   dotnet add package Microsoft.Azure.SignalR
    ```
 
 1. Add a call to `AddAzureSignalR()` in `Startup.ConfigureServices()` as demonstrated below.