Adding .NET Isolated to event based blob trigger tutorial

Author: nzthiago

articles/azure-functions/functions-event-grid-blob-trigger.md

@@ -85,10 +85,11 @@ When you create a Blob Storage-triggered function using Visual Studio Code, you
 1. At the prompts, provide the following information:
 
     ::: zone pivot="programming-language-csharp"
+    # [In-process](#tab/in-process) 
     |Prompt|Action|
     |--|--|
     |**Select a language**| Select `C#`. |
-    |**Select a .NET runtime**| Select `.NET 6.0 LTS`. Event-driven blob triggers aren't yet supported when running in an isolated worker process. |
+    |**Select a .NET runtime**| Select `.NET 6.0 Isolated LTS` for running in an isolated worker process or `.NET 6.0 LTS` for in-process. |
     |**Select a template for your project's first function**| Select `Azure Blob Storage trigger`. |
     |**Provide a function name**| Enter `BlobTriggerEventGrid`. |
     |**Provide a namespace** | Enter `My.Functions`. |
@@ -156,27 +157,27 @@ To use the Event Grid-based Blob Storage trigger, your function requires at leas
 ::: zone pivot="programming-language-csharp"
 To upgrade your project with the required extension version, in the Terminal window, run the following command: [dotnet add package](/dotnet/core/tools/dotnet-add-package)
 
-<!---# [In-process](#tab/in-process) -->
+# [Isolated process](#tab/isolated-process)
 ```bash
-dotnet add package Microsoft.Azure.WebJobs.Extensions.Storage --version 5.0.1 
+dotnet add package Microsoft.Azure.Functions.Worker.Extensions.Storage.Blobs --version 6.1.0
 ```
-<!---# [Isolated process](#tab/isolated-process)
+# [In-process](#tab/in-process)
 ```bash
-dotnet add package Microsoft.Azure.Functions.Worker.Extensions.Storage --version 5.0.0
+dotnet add package Microsoft.Azure.WebJobs.Extensions.Storage --version 5.1.3 
 ```
 ---
--->
+
 ::: zone-end
 ::: zone pivot="programming-language-javascript,programming-language-powershell,programming-language-python,programming-language-java"  
 
 1. Open the host.json project file, and inspect the `extensionBundle` element. 
 
-1. If `extensionBundle.version` isn't at least `3.3.0 `, replace `extensionBundle` with the following version:
+1. If `extensionBundle.version` isn't at least `3.3.0 `, replace `extensionBundle` with the latest:
 
    ```json
    "extensionBundle": {
        "id": "Microsoft.Azure.Functions.ExtensionBundle",
-       "version": "[3.3.0, 4.0.0)"
+       "version": "[4.0.0, 5.0.0)"
    }
    ```
 
@@ -186,14 +187,26 @@ dotnet add package Microsoft.Azure.Functions.Worker.Extensions.Storage --version
 
 ::: zone pivot="programming-language-csharp"
 In the BlobTriggerEventGrid.cs file, add `Source = BlobTriggerSource.EventGrid` to the parameters for the Blob trigger attribute, for example:
-    
+
+# [Isolated process](#tab/isolated-process)
+```csharp
+[Function("BlobTriggerCSharp")]
+public async Task Run([BlobTrigger("samples-workitems/{name}", Source = BlobTriggerSource.EventGrid, Connection = "<NAMED_STORAGE_CONNECTION>")] Stream myBlob, string name, FunctionContext executionContext)
+{
+    var logger = executionContext.GetLogger("BlobTriggerCSharp");
+    logger.LogInformation($"C# Blob trigger function Processed blob\n Name: {name} \n Size: {myBlob.Length} Bytes");
+}
+```
+# [In-process](#tab/in-process)
 ```csharp
 [FunctionName("BlobTriggerCSharp")]
 public static void Run([BlobTrigger("samples-workitems/{name}", Source = BlobTriggerSource.EventGrid, Connection = "<NAMED_STORAGE_CONNECTION>")]Stream myBlob, string name, ILogger log)
 {
     log.LogInformation($"C# Blob trigger function Processed blob\n Name:{name} \n Size: {myBlob.Length} Bytes");
 }
 ```
+---
+
 ::: zone-end
 ::: zone pivot="programming-language-python"
 After you create the function, in the function.json configuration file, add `"source": "EventGrid"` to the `myBlob` binding, for example:
@@ -270,10 +283,17 @@ Event Grid validates the endpoint URL when you create an event subscription in t
 
 When your function runs locally, the default endpoint used for an event-driven blob storage trigger looks like the following URL:
 
-::: zone pivot="programming-language-csharp"  
+::: zone pivot="programming-language-csharp"
+# [Isolated process](#tab/isolated-process)
+```http
+http://localhost:7071/runtime/webhooks/blobs?functionName=Host.Functions.BlobTriggerEventGrid
+```
+# [In-process](#tab/in-process)
 ```http
 http://localhost:7071/runtime/webhooks/blobs?functionName=BlobTriggerEventGrid
 ```
+---
+
 ::: zone-end  
 ::: zone pivot="programming-language-javascript,programming-language-powershell,programming-language-python,programming-language-java"   
 ```http
@@ -317,12 +337,17 @@ The endpoint used in the event subscription is made up of three different parts,
 | --- | --- |
 | Prefix and server name |  When your function runs locally, the server name with an `https://` prefix comes from the **Forwarding** URL generated by *ngrok*. In the localhost URL, the *ngrok* URL replaces `http://localhost:7071`. When running in Azure, you'll instead use the published function app server, which is usually in the form `https://<FUNCTION_APP_NAME>.azurewebsites.net`. |
 | Path | The path portion of the endpoint URL comes from the localhost URL copied earlier, and looks like `/runtime/webhooks/blobs` for a Blob Storage trigger. The path for an Event Grid trigger would be `/runtime/webhooks/EventGrid` | 
-| Query string | The `functionName=BlobTriggerEventGrid` parameter in the query string sets the name of the function that handles the event. For functions other than C#, the function name is qualified by `Host.Functions.`. If you used a different name for your function, you'll need to change this value. An access key isn't required when running locally. When running in Azure, you'll also need to include a `code=` parameter in the URL, which contains a key that you can get from the portal. |
+| Query string | For all languages including .NET Isolated the `functionName=Host.Functions.BlobTriggerEventGrid` parameter, except for .NET In-process which should be `functionName=BlobTriggerEventGrid` in the query string sets the name of the function that handles the event. If you used a different name for your function, you'll need to change this value. An access key isn't required when running locally. When running in Azure, you'll also need to include a `code=` parameter in the URL, which contains a key that you can get from the portal. |
 
 The following screenshot shows an example of how the final endpoint URL should look when using a Blob Storage trigger named `BlobTriggerEventGrid`:
 
 ::: zone pivot="programming-language-csharp"  
+# [Isolated process](#tab/isolated-process)
+  ![Endpoint selection](./media/functions-event-grid-blob-trigger/functions-event-grid-local-dev-event-subscription-endpoint-selection-qualified.png)
+# [In-process](#tab/in-process)
   ![Endpoint selection](./media/functions-event-grid-blob-trigger/functions-event-grid-local-dev-event-subscription-endpoint-selection.png)
+---
+
 ::: zone-end  
 ::: zone pivot="programming-language-javascript,programming-language-powershell,programming-language-python,programming-language-java"   
   ![Endpoint selection](./media/functions-event-grid-blob-trigger/functions-event-grid-local-dev-event-subscription-endpoint-selection-qualified.png)
@@ -368,7 +393,7 @@ An event subscription, powered by Azure Event Grid, raises events based on chang
     | **Name** | *myBlobLocalNgrokEventSub* | Name that identifies the event subscription. You can use the name to quickly find the event subscription. |
     | **Event Schema** | **Event Grid Schema** | Use the default schema for events. |
     | **System Topic Name** | *samples-workitems-blobs* | Name for the topic, which represents the container. The topic is created with the first subscription, and you'll use it for future event subscriptions. |
-    | **Filter to Event Types** | *Blob Created*<br/>*Blob Deleted*| 
+    | **Filter to Event Types** | *Blob Created*| 
     | **Endpoint Type** |  **Web Hook** | The blob storage trigger uses a web hook endpoint. You would use Azure Functions for an Event Grid trigger. |
     | **Endpoint** | Your ngrok-based URL endpoint | Use the ngrok-based URL endpoint that you determined earlier. |
 
@@ -449,9 +474,16 @@ You'll include this value in the query string of new endpoint URL.
 Create a new endpoint URL for the Blob Storage trigger based on the following example: 
 
 ::: zone pivot="programming-language-csharp"  
+# [Isolated process](#tab/isolated-process)
+```http
+https://<FUNCTION_APP_NAME>.azurewebsites.net/runtime/webhooks/blobs?functionName=Host.Functions.BlobTriggerEventGrid&code=<BLOB_EXTENSION_KEY>
+```
+# [In-process](#tab/in-process)
 ```http
 https://<FUNCTION_APP_NAME>.azurewebsites.net/runtime/webhooks/blobs?functionName=BlobTriggerEventGrid&code=<BLOB_EXTENSION_KEY>
 ```
+---
+
 ::: zone-end  
 ::: zone pivot="programming-language-javascript,programming-language-powershell,programming-language-python,programming-language-java"  
 ```http
@@ -479,7 +511,7 @@ This time, you'll include the filter on the event subscription so that only JPEG
     | ------------ | ---------------- | ----------- |
     | **Name** | *myBlobAzureEventSub* | Name that identifies the event subscription. You can use the name to quickly find the event subscription. |
     | **Event Schema** | **Event Grid Schema** | Use the default schema for events. |
-    | **Filter to Event Types** | *Blob Created*<br/>*Blob Deleted*| 
+    | **Filter to Event Types** | *Blob Created*| 
     | **Endpoint Type** |  **Web Hook** | The blob storage trigger uses a web hook endpoint. You would use Azure Functions for an Event Grid trigger. |
     | **Endpoint** | Your new Azure-based URL endpoint | Use the URL endpoint that you built, which includes the key value. |