add signalr to identity-based connection supporting service lists

Author: Y-Sindo

articles/azure-functions/functions-reference.md

@@ -1,5 +1,5 @@
 ---
-title: Guidance for developing Azure Functions 
+title: Guidance for developing Azure Functions
 description: Learn the Azure Functions concepts and techniques that you need to develop functions in Azure, across all programming languages and bindings.
 ms.assetid: d8efe41a-bef8-4167-ba97-f3e016fcd39e
 ms.topic: conceptual
@@ -43,7 +43,7 @@ The `bindings` property is where you configure both triggers and bindings. Each
 | name | Function identifier.<br><br>For example, `myQueue`. | string | The name that is used for the bound data in the function. For C#, this is an argument name; for JavaScript, it's the key in a key/value list. |
 
 ## Function app
-A function app provides an execution context in Azure in which your functions run. As such, it is the unit of deployment and management for your functions. A function app is comprised of one or more individual functions that are managed, deployed, and scaled together. All of the functions in a function app share the same pricing plan, deployment method, and runtime version. Think of a function app as a way to organize and collectively manage your functions. To learn more, see [How to manage a function app](functions-how-to-use-azure-function-app-settings.md). 
+A function app provides an execution context in Azure in which your functions run. As such, it is the unit of deployment and management for your functions. A function app is comprised of one or more individual functions that are managed, deployed, and scaled together. All of the functions in a function app share the same pricing plan, deployment method, and runtime version. Think of a function app as a way to organize and collectively manage your functions. To learn more, see [How to manage a function app](functions-how-to-use-azure-function-app-settings.md).
 
 > [!NOTE]
 > All functions in a function app must be authored in the same language. In [previous versions](functions-versions.md) of the Azure Functions runtime, this wasn't required.
@@ -105,7 +105,7 @@ For example, the `connection` property for an Azure Blob trigger definition migh
 
 > [!NOTE]
 > When using [Azure App Configuration](../azure-app-configuration/quickstart-azure-functions-csharp.md) or [Key Vault](../key-vault/general/overview.md) to provide settings for Managed Identity connections, setting names should use a valid key separator such as `:` or `/` in place of the `__` to ensure names are resolved correctly.
-> 
+>
 > For example, `Storage1:blobServiceUri`.
 
 ### Configure an identity-based connection
@@ -123,7 +123,7 @@ Identity-based connections are supported by the following components:
 | Azure Service Bus triggers and bindings       | All             | [Azure Service Bus extension version 5.0.0 or later][servicebusv5],<br/>[Extension bundle 3.3.0 or later][servicebusv5] |
 | Azure Cosmos DB triggers and bindings         | All | [Azure Cosmos DB extension version 4.0.0 or later][cosmosv4],<br/> [Extension bundle 4.0.2 or later][cosmosv4]|
 | Azure SignalR triggers and bindings           | All | [Azure SignalR extension version 1.7.0 or later][signalr] <br/>[Extension bundle 3.6.1 or later][signalr]
-| Durable Functions storage provider (Azure Storage) | All | [Durable Functions extension version 2.7.0 or later][durable-identity],<br/>[Extension bundle 3.3.0 or later][durable-identity] | 
+| Durable Functions storage provider (Azure Storage) | All | [Durable Functions extension version 2.7.0 or later][durable-identity],<br/>[Extension bundle 3.3.0 or later][durable-identity] |
 | Host-required storage ("AzureWebJobsStorage") - Preview | All             | [Connecting to host storage with an identity](#connecting-to-host-storage-with-an-identity-preview)                        |
 
 [blobv5]: ./functions-bindings-storage-blob.md#install-extension
@@ -163,6 +163,8 @@ Choose a tab below to learn about permissions for each component:
 
 [!INCLUDE [functions-cosmos-permissions](../../includes/functions-cosmos-permissions.md)]
 
+# [Azure SignalR extension](#tab/signalr)
+[!INCLUDE [functions-signalr-permissions](../../includes/functions-signalr-permissions.md)]
 
 # [Durable Functions storage provider (preview)](#tab/durable)
 
@@ -188,7 +190,7 @@ Additional options may be supported for a given connection type. Please refer to
 ##### Local development with identity-based connections
 
 > [!NOTE]
-> Local development with identity-based connections requires updated versions of the [Azure Functions Core Tools](./functions-run-local.md). You can check your currently installed version by running `func -v`. For Functions v3, use version `3.0.3904` or later. For Functions v4, use version `4.0.3904` or later. 
+> Local development with identity-based connections requires updated versions of the [Azure Functions Core Tools](./functions-run-local.md). You can check your currently installed version by running `func -v`. For Functions v3, use version `3.0.3904` or later. For Functions v4, use version `4.0.3904` or later.
 
 When running locally, the above configuration tells the runtime to use your local developer identity. The connection will attempt to get a token from the following locations, in order:
 
@@ -209,7 +211,7 @@ In some cases, you may wish to specify use of a different identity. You can add
 | Client ID | `<CONNECTION_NAME_PREFIX>__clientId` |  The client (application) ID of an app registration in the tenant. |
 | Client secret | `<CONNECTION_NAME_PREFIX>__clientSecret` | A client secret that was generated for the app registration. |
 
-Here is an example of `local.settings.json` properties required for identity-based connection to Azure Blobs: 
+Here is an example of `local.settings.json` properties required for identity-based connection to Azure Blobs:
 
 ```json
 {

includes/functions-signalr-permissions.md

@@ -0,0 +1,9 @@
+---
+author: Y-Sindo
+ms.service: azure-functions
+ms.topic: include
+ms.date: 03/01/2023
+ms.author: zityang
+---
+
+You'll need to create a role assignment that provides access to Azure SignalR Service data plane REST APIs. We recommend you to use the built-in role [SignalR Service Owner](../articles/role-based-access-control/built-in-roles.md#signalr-service-owner). Management roles like [Owner](../articles/role-based-access-control/built-in-roles.md#owner) aren't sufficient.