Skip to content

Commit adc63de

Browse files
committed
Rearrange
1 parent b037b25 commit adc63de

File tree

1 file changed

+15
-15
lines changed

1 file changed

+15
-15
lines changed

articles/event-grid/webhook-event-delivery.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -15,21 +15,6 @@ Like many other services that support webhooks, Event Grid requires you to prove
1515
## Endpoint validation with CloudEvents v1.0
1616
CloudEvents v1.0 implements its own abuse protection semantics using the **HTTP OPTIONS** method. You can read more about it [here](https://github.com/cloudevents/spec/blob/v1.0/http-webhook.md#4-abuse-protection). When you use the CloudEvents schema for output, Event Grid uses the CloudEvents v1.0 abuse protection in place of the Event Grid validation event mechanism.
1717

18-
## Event schema compatibility
19-
When a topic is created, an incoming event schema is defined. And, when a subscription is created, an outgoing event schema is defined. The following table shows you the compatibility allowed when creating a subscription.
20-
21-
| Incoming event schema | Outgoing event schema | Supported |
22-
| ---- | ---- | ---- |
23-
| Event Grid schema | Event Grid schema | Yes |
24-
| | Cloud Events v1.0 schema | Yes |
25-
| | Custom input schema | No |
26-
| Cloud Events v1.0 schema | Event Grid schema | No |
27-
| | Cloud Events v1.0 schema | Yes |
28-
| | Custom input schema | No |
29-
| Custom input schema | Event Grid schema | Yes |
30-
| | Cloud Events v1.0 schema | Yes |
31-
| | Custom input schema | Yes |
32-
3318
## Endpoint validation with Event Grid events
3419
When you use any of the following three Azure services, the Azure infrastructure automatically handles this validation:
3520

@@ -106,6 +91,21 @@ And, follow one of these steps:
10691

10792
For an example of handling the subscription validation handshake, see a [C# sample](https://github.com/Azure-Samples/event-grid-dotnet-publish-consume-events/blob/master/EventGridConsumer/EventGridConsumer/Function1.cs).
10893

94+
## Event schema compatibility
95+
When a topic is created, an incoming event schema is defined. And, when a subscription is created, an outgoing event schema is defined. The following table shows you the compatibility allowed when creating a subscription.
96+
97+
| Incoming event schema | Outgoing event schema | Supported |
98+
| ---- | ---- | ---- |
99+
| Event Grid schema | Event Grid schema | Yes |
100+
| | Cloud Events v1.0 schema | Yes |
101+
| | Custom input schema | No |
102+
| Cloud Events v1.0 schema | Event Grid schema | No |
103+
| | Cloud Events v1.0 schema | Yes |
104+
| | Custom input schema | No |
105+
| Custom input schema | Event Grid schema | Yes |
106+
| | Cloud Events v1.0 schema | Yes |
107+
| | Custom input schema | Yes |
108+
109109

110110
## Next steps
111111
See the following article to learn how to troubleshoot event subscription validations: [Troubleshoot event subscription validations](troubleshoot-subscription-validation.md).

0 commit comments

Comments
 (0)