Merge pull request #210743 from spelluru/egridfilter0909

Filter examples are part of ARM templates

Author: prmerger-automator[bot]

articles/event-grid/event-filtering.md

@@ -2,7 +2,7 @@
 title: Event filtering for Azure Event Grid
 description: Describes how to filter events when creating an Azure Event Grid subscription.
 ms.topic: conceptual
-ms.date: 06/01/2022
+ms.date: 09/09/2022
 ---
 
 # Understand event filtering for Event Grid subscriptions
@@ -13,6 +13,70 @@ This article describes the different ways to filter which events are sent to you
 * Subject begins with or ends with
 * Advanced fields and operators
 
+## Azure Resource Manager template
+The examples shown in this article are JSON snippets for defining filters in Azure Resource Manager (ARM) templates. For an example of a complete ARM template and deploying an ARM template, see [Quickstart: Route Blob storage events to web endpoint by using an ARM template](blob-event-quickstart-template.md). Here's some more sections around the `filter` section from the example in the quickstart. The ARM template defines the following resources.
+
+- Azure storage account
+- System topic for the storage account
+- Event subscription for the system topic. You'll see the `filter` subsection in the event subscription section. 
+
+In the following example, the event subscription filters for `Microsoft.Storage.BlobCreated` and `Microsoft.Storage.BlobDeleted` events. 
+
+```json
+{
+  "resources": [
+    {
+      "type": "Microsoft.Storage/storageAccounts",
+      "apiVersion": "2021-08-01",
+      "name": "[parameters('storageAccountName')]",
+      "location": "[parameters('location')]",
+      "sku": {
+        "name": "Standard_LRS"
+      },
+      "kind": "StorageV2",
+      "properties": {
+        "accessTier": "Hot"
+      }
+    },
+    {
+      "type": "Microsoft.EventGrid/systemTopics",
+      "apiVersion": "2021-12-01",
+      "name": "[parameters('systemTopicName')]",
+      "location": "[parameters('location')]",
+      "properties": {
+        "source": "[resourceId('Microsoft.Storage/storageAccounts', parameters('storageAccountName'))]",
+        "topicType": "Microsoft.Storage.StorageAccounts"
+      },
+      "dependsOn": [
+        "[resourceId('Microsoft.Storage/storageAccounts', parameters('storageAccountName'))]"
+      ]
+    },
+    {
+      "type": "Microsoft.EventGrid/systemTopics/eventSubscriptions",
+      "apiVersion": "2021-12-01",
+      "name": "[format('{0}/{1}', parameters('systemTopicName'), parameters('eventSubName'))]",
+      "properties": {
+        "destination": {
+          "properties": {
+            "endpointUrl": "[parameters('endpoint')]"
+          },
+          "endpointType": "WebHook"
+        },
+        "filter": {
+          "includedEventTypes": [
+            "Microsoft.Storage.BlobCreated",
+            "Microsoft.Storage.BlobDeleted"
+          ]
+        }
+      },
+      "dependsOn": [
+        "[resourceId('Microsoft.EventGrid/systemTopics', parameters('systemTopicName'))]"
+      ]
+    }
+  ]
+}
+```
+
 ## Event type filtering
 
 By default, all [event types](event-schema.md) for the event source are sent to the endpoint. You can decide to send only certain event types to your endpoint. For example, you can get notified of updates to your resources, but not notified for other operations like deletions. In that case, filter by the `Microsoft.Resources.ResourceWriteSuccess` event type. Provide an array with the event types, or specify `All` to get all event types for the event source.
@@ -549,7 +613,7 @@ The IsNotNull operator evaluates to true if the key's value isn't NULL or undefi
 ```
 
 ## OR and AND
-If you specify a single filter with multiple values, an **OR** operation is performed, so the value of the key field must be one of these values. Here is an example:
+If you specify a single filter with multiple values, an **OR** operation is performed, so the value of the key field must be one of these values. Here's an example:
 
 ```json
 "advancedFilters": [