Merge pull request #203670 from robece/robece-inline-event-types

Restored commit for inline event types definitions

Author: PRMerger19

articles/event-grid/concepts.md

@@ -80,6 +80,8 @@ If Event Grid can't confirm that an event has been received by the subscriber's
 
 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. 
 
+## Inline event type definitions
+Event Grid lets you define the types of events that will be published to a channel. With inline event type definitions, subscribers will be able to easily filter by event type when creating an event subscription. 
 
 ## Next steps
 

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

@@ -59,8 +59,8 @@ Registrations are global. That is, they aren't associated with a particular Azur
 
 ### Channel
 A Channel is a nested resource to a Partner Namespace. A channel has two main purposes:
-  - It's the resource type that allows you to create partner resources on a customer's Azure subscription.  When you create a channel of type `partner topic`, a partner topic is created on a customer's Azure subscription. A partner topic is the customer's resource where events from a partner system. Similarly, when a channel of type `partner destination` is created, a partner destination is created on a customer's Azure subscription. Partner destinations are resources that represent a partner system endpoint to where events are delivered. A channel along with partner topics and partner destinations enables bi-directional event integration.
-   
+  - It's the resource type that allows you to create partner resources on a customer's Azure subscription.  When you create a channel of type `partner topic`, a partner topic is created on a customer's Azure subscription. A partner topic is the customer's resource where events from a partner system. Similarly, when a channel of type `partner destination` is created, a partner destination is created on a customer's Azure subscription. Partner destinations are resources that represent a partner system endpoint to where events are delivered. A channel is the kind of resource, along with partner topics and partner destinations that enable bi-directional event integration.
+  
       A channel has the same lifecycle as its associated customer partner topic or destination. When a channel of type `partner topic` is deleted, for example, the associated customer's partner topic is deleted. Similarly, if the partner topic is deleted by the customer, the associated channel on your Azure subscription is deleted.
   - It's a resource that is used to route events. A channel of type ``partner topic`` is used to route events to a customer's partner topic. It supports two types of routing modes. 
       - **Channel name routing**. With this kind of routing, you publish events using an http header called `aeg-channel-name` where you provide the name of the channel to which events should be routed. As channels are a partner's representation of partner topics, the events routed to the channel show on the customer's parter topic. This kind of routing is a new capability not present in `event channels`, which support only source-based routing. Channel name routing enables more use cases than the source-based routing and it's the recommended routing mode to choose. For example, with channel name routing a customer can request events that originate in different event sources to land on a single partner topic.
@@ -70,6 +70,11 @@ A Channel is a nested resource to a Partner Namespace. A channel has two main pu
 
       A customer can use your partner destination to send your service any kind of events available to [Event Grid](overview.md).
 
+    - A channel can store definitions for event types. These definitions can be added during the creation of a channel or once the channel is created in the configuration. The event type definitions allow a customer to subscribe to these events when using partner topics. [Learn more](concepts.md#inline-event-type-definitions).
+
+      >[!IMPORTANT]
+      >Event types can be managed in the channel and once the values are updated, changes will be reflected immediately in the associated partner topic.
+
 ### Partner namespace
 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. 
 
@@ -128,4 +133,4 @@ You have two options:
 - [Partner topics onboarding form](https://aka.ms/gridpartnerform)
 - [Partner topics overview](partner-events-overview.md)
 - [Auth0 partner topic](auth0-overview.md)
-- [How to use the Auth0 partner topic](auth0-how-to.md)
+- [How to use the Auth0 partner topic](auth0-how-to.md)