Skip to content

Commit 9df0136

Browse files
committed
upload changes
1 parent a0a14fd commit 9df0136

8 files changed

+26
-61
lines changed

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

Lines changed: 4 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -6,20 +6,14 @@ author: spelluru
66

77
ms.service: event-grid
88
ms.topic: conceptual
9-
ms.date: 01/21/2020
9+
ms.date: 05/11/2020
1010
ms.author: spelluru
1111
---
1212

1313
# Event hub as an event handler for Event Grid events
14+
An event handler is the place where the event is sent. The handler takes an action to process the event. Several Azure services are automatically configured to handle events and **Azure Event Hubs** is one of them.
1415

15-
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.
16-
17-
Use Event Hubs when your solution gets events faster than it can process the events. Your application processes the events from Event Hubs at it own schedule. You can scale your event processing to handle the incoming events.
18-
19-
Event Hubs can act as either an event source or event handler. The following article shows how to use Event Hubs as a handler.
20-
21-
## Schema
22-
16+
Use **Event Hubs** when your solution gets events faster than it can process the events. Then, your application can process events from Event Hubs at its own schedule. You can scale your event processing to handle the incoming events.
2317

2418
## Examples
2519

@@ -29,6 +23,4 @@ Event Hubs can act as either an event source or event handler. The following art
2923
| [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. |
3024

3125
## Next steps
32-
33-
* For an introduction to Event Grid, see [About Event Grid](overview.md).
34-
* To quickly get started using Event Grid, see [Create and route custom events with Azure Event Grid](custom-event-quickstart.md).
26+
For an introduction to Event Grid, see [About Event Grid](overview.md).

articles/event-grid/handler-functions.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,21 +6,18 @@ author: spelluru
66

77
ms.service: event-grid
88
ms.topic: conceptual
9-
ms.date: 05/06/2020
9+
ms.date: 05/11/2020
1010
ms.author: spelluru
1111
---
1212

1313
# Azure function as an event handler for Event Grid events
14-
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.
1514

16-
Use Azure Functions for serverless response to events.
15+
An event handler is the place where the event is sent. The handler takes an action to process the event. Several Azure services are automatically configured to handle events and **Azure Functions** is one of them.
1716

18-
When using Azure Functions as the handler, use the Event Grid trigger instead of generic HTTP triggers. Event Grid automatically validates Event Grid Function triggers. With generic HTTP triggers, you must implement the [validation response](webhook-event-delivery.md).
17+
Use **Azure Functions** for serverless response to events. When using an Azure function as the handler, use the Event Grid trigger instead of generic HTTP triggers. Event Grid automatically validates Event Grid Function triggers. With generic HTTP triggers, you must implement the [validation response](webhook-event-delivery.md).
1918

2019
For more information, see [Event Grid trigger for Azure Functions](../azure-functions/functions-bindings-event-grid.md) for an overview of using the Event Grid trigger in functions.
2120

22-
## Schema
23-
2421
## Examples
2522

2623
|Title |Description |
@@ -32,6 +29,4 @@ For more information, see [Event Grid trigger for Azure Functions](../azure-func
3229

3330

3431
## Next steps
35-
36-
* For an introduction to Event Grid, see [About Event Grid](overview.md).
37-
* To quickly get started using Event Grid, see [Create and route custom events with Azure Event Grid](custom-event-quickstart.md).
32+
For an introduction to Event Grid, see [About Event Grid](overview.md).

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

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,16 +6,12 @@ author: spelluru
66

77
ms.service: event-grid
88
ms.topic: conceptual
9-
ms.date: 01/21/2020
9+
ms.date: 05/11/2020
1010
ms.author: spelluru
1111
---
1212

1313
# Logic app as an event handler for Azure Event Grid events
14-
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.
15-
16-
Use Logic Apps to automate business processes for responding to events.
17-
18-
## Schema
14+
An event handler is the place where the event is sent. The handler takes an action to process the event. Several Azure services are automatically configured to handle events and **Azure Logic Apps** is one of them. Use **Logic Apps** to implement business processes to process Event Grid events.
1915

2016
## Tutorials
2117

@@ -26,6 +22,4 @@ Use Logic Apps to automate business processes for responding to events.
2622
| [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. |
2723

2824
## Next steps
29-
30-
* For an introduction to Event Grid, see [About Event Grid](overview.md).
31-
* To quickly get started using Event Grid, see [Create and route custom events with Azure Event Grid](custom-event-quickstart.md).
25+
For an introduction to Event Grid, see [About Event Grid](overview.md).

articles/event-grid/handler-relay-hybrid-connections.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,15 +6,12 @@ author: spelluru
66

77
ms.service: event-grid
88
ms.topic: conceptual
9-
ms.date: 01/21/2020
9+
ms.date: 05/11/2020
1010
ms.author: spelluru
1111
---
1212

1313
# Relay Hybrid connection as an event handler for Azure Event Grid events
14-
15-
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.
16-
17-
Use Azure Relay Hybrid Connections to send events to applications that are within an enterprise network and don't have a publicly accessible endpoint.
14+
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 and **Azure Relay** is one of them. Use Azure **Relay Hybrid Connections** to send events to applications that are within an enterprise network and don't have a publicly accessible endpoint.
1815

1916
## Tutorials
2017

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

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,18 +6,14 @@ author: spelluru
66

77
ms.service: event-grid
88
ms.topic: conceptual
9-
ms.date: 01/21/2020
9+
ms.date: 05/11/2020
1010
ms.author: spelluru
1111
---
1212

1313
# Service Bus queues and topics as event handlers for Azure Event Grid events
14-
15-
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.
16-
17-
## Schema
14+
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 and **Azure Service Bus** is one of them.
1815

1916
## Service Bus queues
20-
2117
You can route events in Event Grid directly to Service Bus queues for use in buffering or command & control scenarios in enterprise applications.
2218

2319
In the Azure portal, while creating an event subscription, select "Service Bus Queue" as endpoint type and then click "select an endpoint" in order to choose a Service Bus queue.

articles/event-grid/handler-storage-queues.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,16 @@ author: spelluru
66

77
ms.service: event-grid
88
ms.topic: conceptual
9-
ms.date: 01/21/2020
9+
ms.date: 05/11/2020
1010
ms.author: spelluru
1111
---
1212

1313
# Storage queue as an event handler for Azure Event Grid events
14-
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.
14+
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 and **Azure Queue Storage** is one of them.
1515

16-
Use Queue storage to receive events that need to be pulled. You might use Queue storage when you have a long running process that takes too long to respond. By sending events to Queue storage, the app can pull and process events on its own schedule.
16+
Use **Queue Storage** to receive events that need to be pulled. You might use Queue storage when you have a long running process that takes too long to respond. By sending events to Queue storage, the app can pull and process events on its own schedule.
17+
18+
## Examples
1719

1820
|Title |Description |
1921
|---------|---------|

articles/event-grid/handler-webhooks.md

Lines changed: 3 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,11 @@ author: spelluru
66

77
ms.service: event-grid
88
ms.topic: conceptual
9-
ms.date: 01/21/2020
9+
ms.date: 05/11/2020
1010
ms.author: spelluru
1111
---
1212

13-
# Webhooks, Automation runbooks, and logic apps as event handlers for Azure Event Grid events
14-
13+
# Webhooks and Automation runbooks as event handlers for Azure Event Grid events
1514
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.
1615

1716

@@ -28,25 +27,13 @@ Use webhooks for customizable endpoints that respond to events.
2827

2928

3029
## Azure Automation
31-
32-
Use Azure Automation to process events with automated runbooks.
30+
Processing of events by using automated runbooks is supported via webhooks. You create a webhook for the runbook and then use the webhook handler as mentioned in the [WebHooks](#webhooks) section.
3331

3432
|Title |Description |
3533
|---------|---------|
3634
|[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. |
3735

3836

39-
## Logic Apps
40-
41-
Use Logic Apps to automate business processes for responding to events.
42-
43-
|Title |Description |
44-
|---------|---------|
45-
| [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. |
46-
| [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. |
47-
| [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. |
48-
49-
5037
## Next steps
5138

5239
* For an introduction to Event Grid, see [About Event Grid](overview.md).

articles/event-grid/toc.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -141,13 +141,15 @@
141141
- name: Event handlers
142142
href: event-handlers.md
143143
items:
144-
- name: Webhooks, Azure Automation, Logic Apps
144+
- name: Webhooks, Azure Automation
145145
displayName: Azure Automation, Logic Apps, Webhooks
146146
href: handler-webhooks.md
147147
- name: Azure Functions
148148
href: handler-functions.md
149149
- name: Event Hubs
150150
href: handler-event-hubs.md
151+
- name: Logic Apps
152+
href: handler-logic-apps.md
151153
- name: Service Bus
152154
href: handler-service-bus.md
153155
- name: Relay hybrid connections

0 commit comments

Comments
 (0)