Skip to content

Commit edfee73

Browse files
committed
Restored commit for inline event types definitions
1 parent fb432b0 commit edfee73

File tree

2 files changed

+7
-0
lines changed

2 files changed

+7
-0
lines changed

articles/event-grid/concepts.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,8 @@ If Event Grid can't confirm that an event has been received by the subscriber's
8080

8181
When you use a custom topic, events must always be published in an array. This can be a batch of one for low-throughput scenarios, however, for high volume use cases, it's recommended that you batch several events together per publish to achieve higher efficiency. Batches can be up to 1 MB and the maximum size of an event is 1 MB.
8282

83+
## Inline event type definitions
84+
Event Grid allow to add to the channels the types of events that will be published, with inline event type definitions subscribers will be able to easily filter by event type when creating an event subscription.
8385

8486
## Next steps
8587

articles/event-grid/partner-events-overview-for-partners.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -70,6 +70,11 @@ A Channel is a nested resource to a Partner Namespace. A channel has two main pu
7070

7171
A customer can use your partner destination to send your service any kind of events available to [Event Grid](overview.md).
7272

73+
- A channel can store ``event types definitions``, these definitions can be added during the creation of a channel or once the channel is created in the configuration to allow a customer to subscribe to these events when using partner topics. [Learn more](concepts.md#inline-event-type-definitions).
74+
75+
>[!IMPORTANT]
76+
>Event types can be managed in the channel and once the values are updated, changes will be reflected immediately in the associated partner topic.
77+
7378
### Partner namespace
7479
A partner namespace is a regional resource that has an endpoint to publish events to Azure Event Grid. Partner namespaces contain either channels or event channels (legacy resource). You must create partner namespaces in regions where customers request partner topics or destinations because channels and their corresponding partner resources must reside in the same region. You can't have a channel in a given region with its related partner topic, for example, located in a different region.
7580

0 commit comments

Comments
 (0)