updates

Author: spelluru

articles/event-grid/event-schema-resource-groups.md

@@ -24,9 +24,6 @@ To programmatically handle events, you can sort events by looking at the `operat
 
 The event subject is the resource ID of the resource that is the target of the operation. To filter events for a resource, provide that resource ID when creating the event subscription.  To filter by a resource type, use a value in following format: `/subscriptions/<subscription-id>/resourcegroups/<resource-group>/providers/Microsoft.Compute/virtualMachines`
 
-> [!NOTE]
-> Resource creation doesn't always map to a single write operation. For a lot of resources, this isn't true since resource creation is a 2 step process. An initial write when the resource creation request is accepted followed by a write when the resource is actually created (or can involve more write for cases where VMs with extension are provisioned). You should explicitly query Azure Resource Manager when processing a write event to get correct state of the resource.
-
 
 ## Event Grid event schema
 

articles/event-grid/event-schema-subscriptions.md

@@ -24,8 +24,6 @@ To programmatically handle events, you can sort events by looking at the `operat
 
 The event subject is the resource ID of the resource that is the target of the operation. To filter events for a resource, provide that resource ID when creating the event subscription. To filter by a resource type, use a value in following format: `/subscriptions/<subscription-id>/resourcegroups/<resource-group>/providers/Microsoft.Compute/virtualMachines`
 
-> [!NOTE]
-> Resource creation doesn't always map to a single write operation. For a lot of resources, this isn't true since resource creation is a 2 step process. An initial write when the resource creation request is accepted followed by a write when the resource is actually created (or can involve more write for cases where VMs with extension are provisioned). You should explicitly query Azure Resource Manager when processing a write event to get correct state of the resource.
 
 ## Event Grid event schema
 

articles/event-grid/handler-event-hubs.md

@@ -22,16 +22,18 @@ Use **Event Hubs** when your solution gets events faster than it can process the
 | [Quickstart: route custom events to Azure Event Hubs with Azure CLI and Event Grid](custom-event-to-eventhub.md) | Sends a custom event to an event hub for processing by an application. |
 | [Resource Manager template: custom topic and Event Hubs endpoint](https://github.com/Azure/azure-quickstart-templates/tree/master/101-event-grid-event-hubs-handler)| A Resource Manager template that creates a subscription for a custom topic. It sends events to an Azure Event Hubs. |
 
-## Message headers
-Set the following message headers when sending events as messages to a Service Bus endpoint.
+## Message properties
+Set the following message headers when sending events as messages to an **event hub**.
 
 | Property name | Description |
 | ------------- | ----------- | 
 | aeg-subscription-name | Name of event subscription. |
 | aeg-delivery-count | Number of attempts made for the event. Example: "1" |
-| aeg-data-version | Data version of the event. Example: "1" |
-| aeg-metadata-version | Metadata version of the event. Example: "1" |
 | aeg-event-type | Event type. Example: "Microsoft.Storage.blobCreated" | 
+| aeg-metadata-version | Metadata version of the event. Example: "1". For **Event Grid event schema**, this property represents the metadata version and for **cloud event schema**, it represents the **spec version**. |
+| aeg-data-version | Data version of the event. Example: "1". Default value: "". For **Event Grid event schema**, this property represents the data version and for **cloud event schema**, it doesn't apply. |
+| aeg-output-event-id | ID of the Event Grid event. |
+
 
 ## Next steps
 For an introduction to Event Grid, see [About Event Grid](overview.md).

articles/event-grid/handler-logic-apps.md

@@ -57,20 +57,22 @@ az eventgrid event-subscription create \
     --endpoint /subscriptions/{SubID}/resourceGroups/TestRG/providers/Microsoft.ServiceBus/namespaces/ns1/topics/topic1
 ```
 
-## Message headers
-Set the following message headers when sending events as messages to a Service Bus endpoint.
+## Message properties
+Set the following message properties when sending events as messages to a Service Bus endpoint.
 
 | Property name | Description |
 | ------------- | ----------- | 
 | aeg-subscription-name | Name of event subscription. |
 | aeg-delivery-count | Number of attempts made for the event. Example: "1" |
-| aeg-data-version | Data version of the event. Example: "1" |
-| aeg-metadata-version | Metadata version of the event. Example: "1" |
 | aeg-event-type | Event type. Example: "Microsoft.Storage.blobCreated" | 
+| aeg-metadata-version | Metadata version of the event. Example: "1". For **Event Grid event schema**, this property represents the metadata version and for **cloud event schema**, it represents the **spec version**. |
+| aeg-data-version | Data version of the event. Example: "1". Default value: "". For **Event Grid event schema**, this property represents the data version and for **cloud event schema**, it doesn't apply. |
+| aeg-output-event-id | ID of the Event Grid event. |
 
+## Message headers
+When sending events to a Service Bus endpoint (queue or topic) as brokered messages, the `messageid` of the brokered message is the **event ID**.
 
-## Duplicate detection
-When sending events to a Service Bus endpoint as brokered messages, the `messageid` of the brokered message is the event ID. This will be maintained across redelivery of the event so that you can avoid duplicate deliveries by turning on **duplicate detection** on service bus entity. We recommend that you enable duration of the duplicate detection on the Service Bus entity to be either the time-to-live (TTL) of the event or max retry duration, which ever is longer.
+The event ID will be maintained across redelivery of the event so that you can avoid duplicate deliveries by turning on **duplicate detection** on the service bus entity. We recommend that you enable duration of the duplicate detection on the Service Bus entity to be either the time-to-live (TTL) of the event or max retry duration, whichever is longer.
 
 ## Next steps
 

articles/event-grid/handler-service-bus.md

@@ -1,6 +1,6 @@
 ---
 title: Webhooks as event handlers for Azure Event Grid events
-description: Describes how you can use Webhooks (Azure Automation runbooks and loigc apps) as event handlers for Azure Event Grid events.
+description: Describes how you can use Webhooks (Azure Automation runbooks and logic apps) as event handlers for Azure Event Grid events.
 services: event-grid
 author: spelluru
 
@@ -10,9 +10,11 @@ ms.date: 05/11/2020
 ms.author: spelluru
 ---
 
-# Webhooks and Automation runbooks as event handlers for Azure Event Grid events
+# Webhooks, Automation runbooks, Logic apps as event handlers for Azure Event Grid events
 An event handler is the place where the event is sent. The handler takes some further action to process the event. Several Azure services are automatically configured to handle events. You can also use any WebHook for handling events. The WebHook doesn't need to be hosted in Azure to handle events. Event Grid only supports HTTPS WebHook endpoints.
 
+> [!NOTE]
+> Using Azure Automation runbooks or logic apps as event handlers is supported via webhooks. 
 
 ## WebHooks
 
@@ -34,6 +36,19 @@ Processing of events by using automated runbooks is supported via webhooks. You
 |[Tutorial: Azure Automation with Event Grid and Microsoft Teams](ensure-tags-exists-on-new-virtual-machines.md) |Create a virtual machine, which sends an event. The event triggers an Automation runbook that tags the virtual machine, and triggers a message that is sent to a Microsoft Teams channel. |
 
 
+## Logic Apps
+Use **Logic Apps** to implement business processes to process Event Grid events. 
+
+|Title  |Description  |
+|---------|---------|
+| [Tutorial: monitor virtual machine changes with Azure Event Grid and Logic Apps](monitor-virtual-machine-changes-event-grid-logic-app.md) | A logic app monitors changes to a virtual machine and sends emails about those changes. |
+| [Tutorial: send email notifications about Azure IoT Hub events using Logic Apps](publish-iot-hub-events-to-logic-apps.md) | A logic app sends a notification email every time a device is added to your IoT hub. |
+| [Tutorial: Azure Service Bus to Azure Event Grid integration examples](../service-bus-messaging/service-bus-to-event-grid-integration-example.md?toc=%2fazure%2fevent-grid%2ftoc.json) | Event Grid sends messages from Service Bus topic to function app and logic app. |
+
+## Next steps
+For an introduction to Event Grid, see [About Event Grid](overview.md).
+
+
 ## Next steps
 
 * For an introduction to Event Grid, see [About Event Grid](overview.md).

articles/event-grid/handler-webhooks.md

@@ -148,8 +148,6 @@
       href: handler-functions.md
     - name: Event Hubs 
       href: handler-event-hubs.md
-    - name: Logic Apps
-      href: handler-logic-apps.md
     - name: Relay hybrid connections
       href: handler-relay-hybrid-connections.md
     - name: Service Bus

articles/event-grid/toc.yml

@@ -19,14 +19,9 @@ The following limits apply to Azure Event Grid system topics and custom topics,
 | Publish rate for a custom topic (ingress) | 5,000 events per second per topic |
 | Publish requests | 250 per second |
 | Event size | 1 MB. Operations are charged in 64 KB increments though. So, events over 64 KB will incur operations charges as though they were multiple events. For example, an event that is 130 KB would incur operations as though it were 3 separate events.  |
-
-The following limits apply to event domains only.
-
-| Resource | Limit |
-| --- | --- |
 | Topics per event domain | 100,000 |
 | Event subscriptions per topic within a domain | 500 |
 | Domain scope event subscriptions | 50 |
 | Publish rate for an event domain (ingress) | 5,000 events per second |
-| Publish requests | 250 per second |
+| Publish requests for an event domain | 250 per second |
 | Event Domains per Azure Subscription | 100 |