Add the C# function deployment to the readme. (Azure#48121)

* The draft of changes

* Recird the tests and add fuction deployment instructions.

* Remove unrelated changes

* Remove non needed line

Author: nick863

sdk/ai/Azure.AI.Projects/README.md

@@ -541,7 +541,7 @@ await foreach (StreamingUpdate streamingUpdate in client.CreateRunStreamingAsync
 
 #### Azure function call
 
-We also can use Azure Function from inside the agent. In the example below we are calling function "foo", which responds "Bar". In this example we create `AzureFunctionToolDefinition` object, with the function name, description, input and output queues, followed by function parameters.
+We also can use Azure Function from inside the agent. In the example below we are calling function "foo", which responds "Bar". In this example we create `AzureFunctionToolDefinition` object, with the function name, description, input and output queues, followed by function parameters. See below for the instructions on function deployment.
 ```C# Snippet:AzureFunctionsDefineFunctionTools
 AzureFunctionToolDefinition azureFnTool = new(
     name: "foo",
@@ -616,6 +616,107 @@ while (runResponse.Value.Status == RunStatus.Queued
     || runResponse.Value.Status == RunStatus.RequiresAction);
 ```
 
+To make a function call we need to create and deploy the Azure function. In the code snippet below, we have an example of function on C# which can be used by the code above.
+
+```C#
+namespace FunctionProj
+{
+    public class Response
+    {
+        public required string Value { get; set; }
+        public required string CorrelationId { get; set; }
+    }
+
+    public class Arguments
+    {
+        public required string OutputQueueUri { get; set; }
+        public required string CorrelationId { get; set; }
+    }
+
+    public class Foo
+    {
+        private readonly ILogger<Foo> _logger;
+
+        public Foo(ILogger<Foo> logger)
+        {
+            _logger = logger;
+        }
+
+        [Function("Foo")]
+        public void Run([QueueTrigger("azure-function-foo-input")] Arguments input, FunctionContext executionContext)
+        {
+            var logger = executionContext.GetLogger("Foo");
+            logger.LogInformation("C# Queue function processed a request.");
+
+            // We have to provide the Managed identity for function resource
+            // and allow this identity a Queue Data Contributor role on the storage account.
+            var cred = new DefaultAzureCredential();
+            var queueClient = new QueueClient(new Uri(input.OutputQueueUri), cred,
+                    new QueueClientOptions { MessageEncoding = QueueMessageEncoding.Base64 });
+
+            var response = new Response
+            {
+                Value = "Bar",
+                // Important! Correlation ID must match the input correlation ID.
+                CorrelationId = input.CorrelationId
+            };
+
+            var jsonResponse = JsonSerializer.Serialize(response);
+            queueClient.SendMessage(jsonResponse);
+        }
+    }
+}
+```
+
+In this code we define function input and output class: `Arguments` and `Response` respectively. These two data classes will be serialized in JSON. It is important that these both contain field `CorrelationId`, which is the same between input and output.
+
+In our example the function will be stored in the storage account, created with the AI hub. For that we need to allow key access to that storage. In Azure portal go to Storage account > Settings > Configuration and set "Allow storage account key access" to Enabled. If it is not done, the error will be displayed "The remote server returned an error: (403) Forbidden." To create the function resource that will host our function, install azure-cli python package and run the next command:
+
+```shell
+pip install -U azure-cli
+az login
+az functionapp create --resource-group your-resource-group --consumption-plan-location region --runtime dotnet-isolated --functions-version 4 --name function_name --storage-account storage_account_already_present_in_resource_group --app-insights existing_or_new_application_insights_name
+```
+
+This function writes data to the output queue and hence needs to be authenticated to Azure, so we will need to assign the function system identity and provide it `Storage Queue Data Contributor`. To do that in Azure portal select the function, located in `your-resource-group` resource group and in Settings>Identity, switch it on and click Save. After that assign the `Storage Queue Data Contributor` permission on storage account used by our function (`storage_account_already_present_in_resource_group` in the script above) for just assigned System Managed identity.
+
+Now we will create the function itself. Install [.NET](https://dotnet.microsoft.com/download) and [Core Tools](https://go.microsoft.com/fwlink/?linkid=2174087) and create the function project using next commands. 
+```
+func init FunctionProj --worker-runtime dotnet-isolated --target-framework net8.0
+cd FunctionProj
+func new --name foo --template "HTTP trigger" --authlevel "anonymous"
+dotnet add package Azure.Identity
+dotnet add package Microsoft.Azure.Functions.Worker.Extensions.Storage.Queues --prerelease
+```
+
+**Note:** There is a "Azure Queue Storage trigger", however the attempt to use it results in error for now.
+We have created a project, containing HTTP-triggered azure function with the logic in `Foo.cs` file. As far as we need to trigger Azure function by a new message in the queue, we will replace the content of a Foo.cs by the C# sample code above. 
+To deploy the function run the command from dotnet project folder:
+
+```
+func azure functionapp publish function_name
+```
+
+In the `storage_account_already_present_in_resource_group` select the `Queue service` and create two queues: `azure-function-foo-input` and `azure-function-tool-output`. Note that the same queues are used in our sample. To check that the function is working, place the next message into the `azure-function-foo-input` and replace `storage_account_already_present_in_resource_group` by the actual resource group name, or just copy the output queue address.
+```json
+{
+  "OutputQueueUri": "https://storage_account_already_present_in_resource_group.queue.core.windows.net/azure-function-tool-output",
+  "CorrelationId": "42"
+}
+```
+
+Next, we will monitor the output queue or the message. You should receive the next message.
+```json
+{
+  "Value": "Bar",
+  "CorrelationId": "42"
+}
+```
+Please note that the input `CorrelationId` is the same as output.
+*Hint:* Place multiple messages to input queue and keep second internet browser window with the output queue open and hit the refresh button on the portal user interface, so that you will not miss the message. If the message instead went to `azure-function-foo-input-poison` queue, the function completed with error, please check your setup.
+After we have tested the function and made sure it works, please make sure that the Azure AI Project have the next roles for the storage account: `Storage Account Contributor`, `Storage Blob Data Contributor`, `Storage File Data Privileged Contributor`, `Storage Queue Data Contributor` and `Storage Table Data Contributor`. Now the function is ready to be used by the agent.
+
+
 #### Create Agent With OpenAPI
 
 OpenAPI specifications describe REST operations against a specific endpoint. Agents SDK can read an OpenAPI spec, create a function from it, and call that function against the REST endpoint without additional client-side execution.

sdk/ai/Azure.AI.Projects/assets.json

@@ -2,5 +2,5 @@
   "AssetsRepo": "Azure/azure-sdk-assets",
   "AssetsRepoPrefixPath": "net",
   "TagPrefix": "net/ai/Azure.AI.Projects",
-  "Tag": "net/ai/Azure.AI.Projects_d15b826ff9"
+  "Tag": "net/ai/Azure.AI.Projects_c34fc3243d"
 }

sdk/ai/Azure.AI.Projects/tests/AgentClientTests.cs

@@ -973,9 +973,10 @@ public async Task TestIncludeFileSearchContent(bool useStream, bool includeConte
         }
 
         [RecordedTest]
-        [Ignore("Azure function call is not supported in all regions yet.")]
         public async Task TestAzureFunctionCall()
         {
+            // Note: This test was recorded in westus region as for now
+            // 2025-02-05 it is not supported in test region (East US 2)
             AzureFunctionToolDefinition azureFnTool = new(
                 name: "foo",
                 description: "Get answers from the foo bot.",
@@ -1032,9 +1033,10 @@ public async Task TestAzureFunctionCall()
             await WaitForRun(client, run);
             PageableList<ThreadMessage> afterRunMessages = await client.GetMessagesAsync(thread.Id);
 
+            Assert.Greater(afterRunMessages.Count(), 1);
+            bool foundResponse = false;
             foreach (ThreadMessage msg in afterRunMessages)
             {
-                bool foundResponse = false;
                 foreach (MessageContent contentItem in msg.ContentItems)
                 {
                     if (contentItem is MessageTextContent textItem)
@@ -1046,8 +1048,8 @@ public async Task TestAzureFunctionCall()
                         }
                     }
                 }
-                Assert.True(foundResponse);
             }
+            Assert.True(foundResponse);
         }
 
         [RecordedTest]