Copied Javier's changes

Author: spelluru

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

@@ -2,13 +2,12 @@
 title: CloudEvents v1.0 schema with Azure Event Grid
 description: Describes how to use the CloudEvents v1.0 schema for events in Azure Event Grid. The service supports events in the JSON implementation of Cloud Events. 
 ms.topic: conceptual
-ms.custom: ignite-2022
-ms.date: 11/03/2022
+ms.date: 05/24/2023
 ---
 
 # CloudEvents v1.0 schema with Azure Event Grid
 
-In addition to its [default event schema](event-schema.md), Azure Event Grid natively supports events in the [JSON implementation of CloudEvents v1.0](https://github.com/cloudevents/spec/blob/v1.0/json-format.md) and [HTTP protocol binding](https://github.com/cloudevents/spec/blob/v1.0/http-protocol-binding.md). [CloudEvents](https://cloudevents.io/) is an [open specification](https://github.com/cloudevents/spec/blob/v1.0/spec.md) for describing event data.
+Azure Event Grid natively supports events in the [JSON implementation of CloudEvents v1.0](https://github.com/cloudevents/spec/blob/v1.0/json-format.md) and [HTTP protocol binding](https://github.com/cloudevents/spec/blob/v1.0/http-protocol-binding.md). [CloudEvents](https://cloudevents.io/) is an [open specification](https://github.com/cloudevents/spec/blob/v1.0/spec.md) for describing event data.
 
 CloudEvents simplifies interoperability by providing a common event schema for publishing, and consuming cloud based events. This schema allows for uniform tooling, standard ways of routing & handling events, and universal ways of deserializing the outer event schema. With a common schema, you can more easily integrate work across platforms.
 
@@ -51,16 +50,16 @@ The headers values for events delivered in the CloudEvents schema and the Event
 
 ## Event Grid for CloudEvents
 
-You can use Event Grid for both input and output of events in CloudEvents schema. You can use CloudEvents for system events, like Blob Storage events and IoT Hub events, and custom events. It can also transform those events on the wire back and forth.
-
+You can use Event Grid for both input and output of events in CloudEvents schema. You can use CloudEvents for system events, like Blob Storage events and IoT Hub events, and custom events. In addition to supporting CloudEvents, Event Grid suppports a proprietary, non-extensible, yet fully-functional [Event Grid event format](event-schema.md). The following table describes the transformation supported when using CloudEvents and Event Grid formats as an input schema in topics and as an output schema in event subscriptions. Note that an Event Grid output schema cannot be used when using CloudEvents as an input schema because CloudEvents supports [extension attributes](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/primer.md#cloudevent-attribute-extensions) which are not supported by the Event Grid schema.
 
 | Input schema       | Output schema
 |--------------------|---------------------
 | CloudEvents format | CloudEvents format
 | Event Grid format  | CloudEvents format
 | Event Grid format  | Event Grid format
 
+
 For all event schemas, Event Grid requires validation when publishing to an event grid topic and when creating an event subscription. For more information, see [Event Grid security and authentication](security-authentication.md).
 
 ## Next steps
-See [How to use CloudEvents v1.0 schema with Event Grid](cloudevents-schema.md).  
+See [How to use CloudEvents v1.0 schema with Event Grid](cloudevents-schema.md).  

articles/event-grid/concepts-pull-delivery.md

@@ -2,13 +2,15 @@
 title: Azure Event Grid concepts (pull delivery)
 description: Describes Azure Event Grid and its concepts in the pull delivery model. Defines several key components of Event Grid.
 ms.topic: conceptual
-ms.custom: build-2023
-ms.date: 04/27/2023
+ms.date: 05/24/2023
 ---
 
 # Azure Event Grid's pull delivery - Concepts
 
-This article describes the main concepts in the pull delivery (HTTP) model of Azure Event Grid.
+This article describes the main concepts related to the new resource model that uses namespaces.
+
+> [!NOTE]
+> For Event Grid concepts related to push delivery exclusively used in custom, system, partner, and domain topics, see this [concepts](concepts.md) article.
 
 ## Events
 
@@ -76,6 +78,9 @@ Namespace topics support [pull delivery](pull-delivery-overview.md#pull-delivery
 
 A subscription tells Event Grid which events on a namespace topic you're interested in receiving. You can filter the events consumers receive. You can filter by event type or event subject, for example. For more information on resource properties, look for control plane operations in the Event Grid [REST API](/rest/api/eventgrid).
 
+> [!NOTE]
+> The event subscriptions under a namespace topic feature a simplified resource model when compared to that used for custom, domain, partner, and system topics. For more information, see Create, view, and managed [event subscriptions](create-view-manage-event-subscriptions.md#simplified-resource-model).
+
 For an example of creating subscriptions for namespace topics, refer to:
 
 - [Publish and consume messages using namespace topics using CLI](publish-events-using-namespace-topics.md)
@@ -89,4 +94,4 @@ For both custom or namespace topics, your application should  batch several even
 ## Next steps
 
 - For an introduction to Event Grid, see [About Event Grid](overview.md).
-- To get started using namespace topics, refer to [publish events using namespace topics](publish-events-using-namespace-topics.md).
+- To get started using namespace topics, refer to [publish events using namespace topics](publish-events-using-namespace-topics.md).

articles/event-grid/concepts.md

@@ -1,14 +1,16 @@
 ---
 title: Azure Event Grid concepts (push delivery)
-description: Describes Azure Event Grid and its concepts. Defines several key components of Event Grid.
+description: Describes Azure Event Grid concepts that pertains to push delivery. Defines several key components of Event Grid.
 ms.topic: conceptual
-ms.custom: build-2023
-ms.date: 05/08/2023
+ms.date: 05/24/2023
 ---
 
 # Azure Event Grid's push delivery - concepts
 
-This article describes the main concepts in Azure Event Grid.
+This article describes the main Event Grid concepts related to push delivery.
+
+> [!NOTE]
+> For Event Grid concepts related to the new resource model that uses namespaces, see this [concepts](concepts-pull-delivery.md) article.
 
 ## Events
 
@@ -63,6 +65,9 @@ Partner topics are a kind of topic used to subscribe to events published by a [p
 
 ## Event subscriptions
 
+> [!NOTE]
+> For information on event subscriptions under a namespace topic see this [concepts](concepts-pull-delivery.md) artcle.
+
 A subscription tells Event Grid which events on a topic you're interested in receiving. When creating a subscription, you provide an endpoint for handling the event. Endpoints can be a webhook or an Azure service resource. You can filter the events that are sent to an endpoint. You can filter by event type or event subject, for example. For more information, see [Event subscriptions](subscribe-through-portal.md) and [CloudEvents schema](cloud-event-schema.md). Event subscriptions for custom, system, and partner topics as well as Domains feature the same resource properties. 
 
 For examples of creating subscriptions for custom, system, and partner topics as well as Domains, see:
@@ -108,4 +113,4 @@ Azure availability zones are physically separate locations within each Azure reg
 ## Next steps
 
 - For an introduction to Event Grid, see [About Event Grid](overview.md).
-- To get started using custom topics, see [Create and route custom events with Azure Event Grid](custom-event-quickstart.md).
+- To get started using custom topics, see [Create and route custom events with Azure Event Grid](custom-event-quickstart.md).

articles/event-grid/create-view-manage-event-subscriptions.md

@@ -3,9 +3,8 @@ title: Create, view, and manage Azure Event Grid event subscriptions in namespac
 description: This article describes how to create, view and manage event subscriptions in namespace topics
 author: robece
 ms.topic: how-to
-ms.custom: build-2023
 ms.author: robece
-ms.date: 05/23/2023
+ms.date: 05/24/2023
 ---
 
 # Create, view, and manage event subscriptions in namespace topics
@@ -74,8 +73,32 @@ ms.date: 05/23/2023
 
 1. To configure the filters associated to the subscription, select **Filters** option in the **Settings** section and add the names of the event types you want to filter in the subscription and add context attribute filters you want to use in the subscription, once you finish the filters configuration select **Save**.
 
-    :::image type="content" source="media/create-view-manage-event-subscriptions/event-subscription-settings-filters.png" alt-text="Screenshot showing Event Grid event subscription filters settings.":::
+    :::image type="content" source="media/create-view-manage-event-subscriptions/event-subscription-settings-filters.png" alt-text="Screenshot showing Event Grid event subscription filters settings." border="false":::
+
+### Simplified resource model
+
+The event subscriptions under a [Namespace Topic](concepts-pull-delivery.md#namespace-topics) feature a simplified filtering configuration model when compared to that of event subscriptions to domains and to custom, system, partner, and domain topics. The filtering capabilities are the  the same except for the scenarios documented in the following sections.
+
+#### Filter on event data
+
+Filtering on event `data` is not currently supported. This capability will be available in a future release.
+
+#### Subject begins with
+
+There is no dedicated configuration properties to specify filters on `subject`. You can configure filters in the following way to filter the context attribute `subject` with a value that begins with a string.
+
+| key value  | operator   |   value |
+|-----------|:---------:|-----------|
+|  subject  |  String begins with   |  **your string**  |
+
+#### Subject ends with
+
+There is no dedicated configuration properties to specify filters on `subject`. You can configure filters in the following way to filter the context attribute `subject` with a value that ends with a string.
+
+| key value  | operator   |   value |
+|-----------|:---------:|-----------|
+|  subject  |  String ends with   |  **your string**  |
 
 ## Next steps
 
-- See the [Publish to namespace topics and consume events](publish-events-using-namespace-topics.md) steps to learn more about how to publish and subscribe events in Azure Event Grid namespaces.
+- See the [Publish to namespace topics and consume events](publish-events-using-namespace-topics.md) steps to learn more about how to publish and subscribe events in Azure Event Grid namespaces.

articles/event-grid/event-schema.md

@@ -1,13 +1,15 @@
 ---
 title: Azure Event Grid event schema
-description: Describes the properties and schema that are present for all events. Events consist of a set of four required string properties.
+description: Describes the properties and schema for the proprietary, non-extensible, yet fully-functional Event Grid format. 
 ms.topic: reference
-ms.date: 09/15/2021
+ms.date: 05/24/2023
 ---
 
 # Azure Event Grid event schema
 
-This article describes the properties and schema that are present for all events. Events consist of a set of four required string properties. The properties are common to all events from any publisher. The data object has properties that are specific to each publisher. For system topics, these properties are specific to the resource provider, such as Azure Storage or Azure Event Hubs.
+This article describes the Event Grid schema, which is a proprietary, non-extensible, yet fully-functional event format. Event Grid still supports this event format and will continue to support it. However, [CloudEvents](cloud-event-schema.md) is the recommended event format to use. If you are using applications that use the Event Grid format, you may find useful the information in the [CloudEvents] section that describes the transformations between the Event Grid and CloudEvents format supported by Event Grid.
+
+This article describes in detail the properties and schema for the Event Grid format. Events consist of a set of four required string properties. The properties are common to all events from any publisher. The data object has properties that are specific to each publisher. For system topics, these properties are specific to the resource provider, such as Azure Storage or Azure Event Hubs.
 
 Event sources send events to Azure Event Grid in an array, which can have several event objects. When posting events to an event grid topic, the array can have a total size of up to 1 MB. Each event in the array is limited to 1 MB. If an event or the array is greater than the size limits, you receive the response **413 Payload Too Large**. 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.
 
@@ -101,7 +103,16 @@ When publishing events to custom topics, create subjects for your events that ma
 
 Sometimes your subject needs more detail about what happened. For example, the **Storage Accounts** publisher provides the subject `/blobServices/default/containers/<container-name>/blobs/<file>` when a file is added to a container. A subscriber could filter by the path `/blobServices/default/containers/testcontainer` to get all events for that container but not other containers in the storage account. A subscriber could also filter or route by the suffix `.txt` to only work with text files.
 
+## CloudEvents
+CloudEvents is the recommended event format to use. Azure Event Grid will continue investing in features related to at least [CloudEvents JSON](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/formats/json-format.md) format. Given the fact that some event sources like Azure services use the Event Grid format, the following table is provided to help help you understand the transformation supported when using CloudEvents and Event Grid formats as an input schema in topics and as an output schema in event subscriptions. Note that an Event Grid output schema cannot be used when using CloudEvents as an input schema because CloudEvents supports [extension attributes](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/primer.md#cloudevent-attribute-extensions) which are not supported by the Event Grid schema.
+
+| Input schema       | Output schema
+|--------------------|---------------------
+| CloudEvents format | CloudEvents format
+| Event Grid format  | CloudEvents format
+| Event Grid format  | Event Grid format
+
 ## Next steps
 
 * For an introduction to Azure Event Grid, see [What is Event Grid?](overview.md)
-* For more information about creating an Azure Event Grid subscription, see [Event Grid subscription schema](subscription-creation-schema.md).
+* For more information about creating an Azure Event Grid subscription, see [Event Grid subscription schema](subscription-creation-schema.md).