More updates

spelluru · spelluru · commit 04a4f97430e9 · 2023-03-14T23:35:52.000-04:00
diff --git a/articles/event-grid/auth0-how-to.md b/articles/event-grid/auth0-how-to.md
@@ -21,7 +21,7 @@ To send Auth0 events to Azure:
 5. [Subscribe to events](#subscribe-to-events).
 
 
-[!INCLUDE [register-event-grid-provider](includes/register-event-grid-provider.md)]
+[!INCLUDE [register-provider](includes/register-provider.md)]
 
 [!INCLUDE [authorize-verified-partner-to-create-topic](includes/authorize-verified-partner-to-create-topic.md)]
 
diff --git a/articles/event-grid/handler-event-hubs.md b/articles/event-grid/handler-event-hubs.md
@@ -18,7 +18,7 @@ See the following examples:
 | [Quickstart: Route custom events to Azure Event Hubs with Azure CLI](custom-event-to-eventhub.md) | Sends a custom event to an event hub for processing by an application. |
 | [Resource Manager template: Create an Event Grid custom topic and send events to an event hub](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.eventgrid/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. |
 
-[!INCLUDE [event-grid-message-headers](./includes/event-grid-message-headers.md)]
+[!INCLUDE [message-headers](./includes/message-headers.md)]
 
 
 ## REST examples (for PUT)
diff --git a/articles/event-grid/handler-service-bus.md b/articles/event-grid/handler-service-bus.md
@@ -84,7 +84,7 @@ New-AzEventGridSubscription -ResourceGroup MyResourceGroup `
 You can also use the [`New-AzEventGridSystemTopicEventSubscription`](/powershell/module/az.eventgrid/new-azeventgridsystemtopiceventsubscription) command for system topics, and the [`New-AzEventGridPartnerTopicEventSubscription`](/powershell/module/az.eventgrid/new-azeventgridpartnertopiceventsubscription) command for partner topics.
 
 
-[!INCLUDE [event-grid-message-headers](./includes/event-grid-message-headers.md)]
+[!INCLUDE [message-headers](./includes/message-headers.md)]
 
 When sending an event to a Service Bus queue or topic as a brokered message, the `messageid` of the brokered message is an internal system ID.
 
diff --git a/articles/event-grid/includes/media/register-provider/event-grid-registered.png b/articles/event-grid/includes/media/register-provider/event-grid-registered.png
diff --git a/articles/event-grid/includes/media/register-provider/register-event-grid-provider.png b/articles/event-grid/includes/media/register-provider/register-event-grid-provider.png
diff --git a/articles/event-grid/includes/message-headers.md b/articles/event-grid/includes/message-headers.md
diff --git a/articles/event-grid/includes/preview-feature-note.md b/articles/event-grid/includes/preview-feature-note.md
diff --git a/articles/event-grid/includes/register-provider.md b/articles/event-grid/includes/register-provider.md
@@ -21,8 +21,8 @@ In the Azure portal, do the following steps:
 1. Search for **Microsoft.EventGrid**, and select it in the provider list. 
 1. Select **Register** on the command bar. 
 
-    :::image type="content" source="./media/register-event-grid-provider/register-event-grid-provider.png" alt-text="Image showing the registration of Microsoft.EventGrid provider with the Azure subscription.":::
+    :::image type="content" source="./media/register-provider/register-provider.png" alt-text="Image showing the registration of Microsoft.EventGrid provider with the Azure subscription.":::
 1. Refresh to make sure the status of **Microsoft.EventGrid** is changed to **Registered**. 
 
-    :::image type="content" source="./media/register-event-grid-provider/event-grid-registered.png" alt-text="Image showing the successful registration of Microsoft.EventGrid provider with the Azure subscription.":::
+    :::image type="content" source="./media/register-provider/event-grid-registered.png" alt-text="Image showing the successful registration of Microsoft.EventGrid provider with the Azure subscription.":::
 
diff --git a/articles/event-grid/kubernetes/batch-event-delivery.md b/articles/event-grid/kubernetes/batch-event-delivery.md
@@ -11,7 +11,7 @@ ms.topic: conceptual
 # Event Grid on Kubernetes - Batch event delivery 
 Event Grid on Kubernetes with Azure Arc has support to deliver more than one event in a single delivery request. This feature makes it possible to increase the overall delivery throughput without having the HTTP per-request overheads. Batch event delivery is turned off by default and can be turned on using the event subscription configuration. 
 
-[!INCLUDE [event-grid-preview-feature-note.md](../includes/event-grid-preview-feature-note.md)]
+[!INCLUDE [preview-feature-note.md](../includes/preview-feature-note.md)]
 
 > [!WARNING]
 > The maximum allowed duration to process each delivery request does not change, even though the event handler code potentially has to do more work per batched request. Delivery timeout defaults to 60 seconds.
diff --git a/articles/event-grid/kubernetes/concepts.md b/articles/event-grid/kubernetes/concepts.md
@@ -11,7 +11,7 @@ ms.topic: conceptual
 # Event Grid on Kubernetes - Concepts
 This article describes the main concepts in Event Grid on Kubernetes with Azure Arc (Preview).
 
-[!INCLUDE [event-grid-preview-feature-note.md](../includes/event-grid-preview-feature-note.md)]
+[!INCLUDE [preview-feature-note.md](../includes/preview-feature-note.md)]
 
 ## Events
 An event is a data record that announces a fact about the operation of a software system. Typically, an event announces a state change because of a signal raised by the system or a signal observed by the system. Events contain two types of information: 
diff --git a/articles/event-grid/kubernetes/create-topic-subscription.md b/articles/event-grid/kubernetes/create-topic-subscription.md
@@ -13,7 +13,7 @@ ms.devlang: azurecli
 # Route cloud events to Webhooks with Azure Event Grid on Kubernetes
 In this quickstart, you'll create a topic in Event Grid on Kubernetes, create a subscription for the topic, and then send a sample event to the topic to test the scenario. 
 
-[!INCLUDE [event-grid-preview-feature-note.md](../includes/event-grid-preview-feature-note.md)]
+[!INCLUDE [preview-feature-note.md](../includes/preview-feature-note.md)]
 
 
 ## Prerequisites
diff --git a/articles/event-grid/kubernetes/delivery-retry.md b/articles/event-grid/kubernetes/delivery-retry.md
@@ -13,7 +13,7 @@ Event Grid on Kubernetes with Azure Arc tries to deliver each message at least o
 
 By default, Event Grid on Kubernetes delivers one event at a time to the subscriber. However, the payload of the delivery request is an array with a single event. It can deliver more than one event at a time if you enable the output batching feature. For details about this feature, see [Batch event delivery](batch-event-delivery.md).
 
-[!INCLUDE [event-grid-preview-feature-note.md](../includes/event-grid-preview-feature-note.md)]
+[!INCLUDE [preview-feature-note.md](../includes/preview-feature-note.md)]
 
 > [!NOTE]
 > During the preview, Event Grid on Kubernetes features are supported through API version [2020-10-15-Preview](/rest/api/eventgrid/controlplane-version2021-10-15-preview/event-subscriptions/create-or-update). 
diff --git a/articles/event-grid/kubernetes/event-handlers.md b/articles/event-grid/kubernetes/event-handlers.md
@@ -15,7 +15,7 @@ The way to configure Event Grid to send events to a destination is through the c
 
 In general, Event Grid on Kubernetes can send events to any destination via **Webhooks**. Webhooks are HTTP(s) endpoints exposed by a service or workload to which Event Grid has access. The webhook can be a workload hosted in the same cluster, in the same network space, on the cloud, on-prem or anywhere that Event Grid can reach. 
 
-[!INCLUDE [event-grid-preview-feature-note.md](../includes/event-grid-preview-feature-note.md)]
+[!INCLUDE [preview-feature-note.md](../includes/preview-feature-note.md)]
 
 Through Webhooks, Event Grid supports the following destinations **hosted on a Kubernetes cluster**:
 
diff --git a/articles/event-grid/kubernetes/event-schemas.md b/articles/event-grid/kubernetes/event-schemas.md
@@ -11,7 +11,7 @@ ms.topic: conceptual
 # Event schemas in Event Grid on Kubernetes
 Event Grid on Kubernetes accepts and delivers events in JSON format. It supports the [Cloud Events 1.0 schema specification](https://github.com/cloudevents/spec/blob/v1.0/spec.md) and that's the schema that should be used when publishing events to Event Grid. 
 
-[!INCLUDE [event-grid-preview-feature-note.md](../includes/event-grid-preview-feature-note.md)]
+[!INCLUDE [preview-feature-note.md](../includes/preview-feature-note.md)]
 
 
 
diff --git a/articles/event-grid/kubernetes/features.md b/articles/event-grid/kubernetes/features.md
@@ -13,7 +13,7 @@ Event Grid on Kubernetes offers a rich set of features that help you integrate y
 
 Although Event Grid on Kubernetes and Azure Event Grid share many features and the goal is to provide the same user experience, there are some differences given the unique requirements they seek to meet and the stage in which they are on their software lifecycle. For example, the only type of topic available in Event Grid on Kubernetes are Event Grid Topics that sometimes are also referred as custom topics. Other types of topics (see below) are either not applicable or support for them is not yet available. The main differences between the two editions of Event Grid are presented in the table below.
 
-[!INCLUDE [event-grid-preview-feature-note.md](../includes/event-grid-preview-feature-note.md)]
+[!INCLUDE [preview-feature-note.md](../includes/preview-feature-note.md)]
 
 
 ## Event Grid on Kubernetes vs. Event Grid on Azure
diff --git a/articles/event-grid/kubernetes/filter-events.md b/articles/event-grid/kubernetes/filter-events.md
@@ -15,7 +15,7 @@ Event Grid on Kubernetes allows specifying filters on any property in the json p
 - Key - The json path to the property on which to apply the filter.
 - Value - The reference value against which the filter is run (or) Values - The set of reference values against which the filter is run.
 
-[!INCLUDE [event-grid-preview-feature-note.md](../includes/event-grid-preview-feature-note.md)]
+[!INCLUDE [preview-feature-note.md](../includes/preview-feature-note.md)]
 
 
 
diff --git a/articles/event-grid/kubernetes/install-k8s-extension.md b/articles/event-grid/kubernetes/install-k8s-extension.md
@@ -13,7 +13,7 @@ This article guides you through the steps to install Event Grid on an [Azure Arc
 
 For brevity, this article refers to "Event Grid on Kubernetes extension" as "Event Grid on Kubernetes" or just "Event Grid".
 
-[!INCLUDE [event-grid-preview-feature-note.md](../includes/event-grid-preview-feature-note.md)]
+[!INCLUDE [preview-feature-note.md](../includes/preview-feature-note.md)]
 
 
 ## Supported Kubernetes distributions
diff --git a/articles/event-grid/kubernetes/overview.md b/articles/event-grid/kubernetes/overview.md
@@ -11,7 +11,7 @@ ms.topic: overview
 # Event Grid on Kubernetes with Azure Arc (Preview) - overview
 This article provides an overview of Event Grid on Kubernetes, use cases for its use, features it offers, and how it differs from Azure Event Grid.
 
-[!INCLUDE [event-grid-preview-feature-note.md](../includes/event-grid-preview-feature-note.md)]
+[!INCLUDE [preview-feature-note.md](../includes/preview-feature-note.md)]
 
 ## What is Event Grid?
 Event Grid is an event broker used to integrate workloads that use event-driven architectures. An event-driven architecture uses events to communicate occurrences in system state changes and is a common integration approach in decoupled architectures such as those that use microservices. Event Grid offers a pub-sub, which is also described as a push-push, communication model where subscribers are sent (pushed) events and those subscribers are not necessarily aware of the publisher that is sending the events. This model contrasts with classic push-pull models, such as the ones used by Azure Service Bus or Azure Event Hubs, where clients pull messages from message brokers and as a consequence, there is a stronger coupling between message brokers and consuming clients.
diff --git a/articles/event-grid/onboard-partner.md b/articles/event-grid/onboard-partner.md
@@ -40,7 +40,7 @@ To complete the remaining steps, make sure you have:
 - An Azure [tenant](../active-directory/develop/quickstart-create-new-tenant.md).
 
 
-[!INCLUDE [register-event-grid-provider](includes/register-event-grid-provider.md)]
+[!INCLUDE [register-provider](includes/register-provider.md)]
 
 ## Create a partner registration 
 
diff --git a/articles/event-grid/receive-events.md b/articles/event-grid/receive-events.md
@@ -382,7 +382,7 @@ Finally, test that your function can now handle your custom event type:
 
 You can also test this functionality live by [sending a custom event with CURL from the Portal](./custom-event-quickstart-portal.md) or by [posting to a custom topic](./post-to-custom-topic.md)  using any service or application that can POST to an endpoint such as [Postman](https://www.getpostman.com/). Create a custom topic and an event subscription with the endpoint set as the Function URL.
 
-[!INCLUDE [event-grid-message-headers](./includes/event-grid-message-headers.md)]
+[!INCLUDE [message-headers](./includes/message-headers.md)]
 
 ## Next steps
 
diff --git a/articles/event-grid/subscribe-to-graph-api-events.md b/articles/event-grid/subscribe-to-graph-api-events.md
@@ -44,7 +44,7 @@ Besides the ability to subscribe to Microsoft Graph API events via Event Grid, y
 5. [Subscribe to events](#subscribe-to-events).
 
 
-[!INCLUDE [register-event-grid-provider](includes/register-event-grid-provider.md)]
+[!INCLUDE [register-provider](includes/register-provider.md)]
 
 [!INCLUDE [authorize-verified-partner-to-create-topic](includes/authorize-verified-partner-to-create-topic.md)]
 
diff --git a/articles/event-grid/subscribe-to-partner-events.md b/articles/event-grid/subscribe-to-partner-events.md
@@ -22,7 +22,7 @@ Here are the steps that a subscriber needs to perform to receive events from a p
 4. [Activate partner topic](#activate-a-partner-topic) so that your events start flowing to your partner topic.
 5. [Subscribe to events](#subscribe-to-events).
 
-[!INCLUDE [register-event-grid-provider](includes/register-event-grid-provider.md)]
+[!INCLUDE [register-provider](includes/register-provider.md)]
 
 [!INCLUDE [authorize-partner-to-create-topic](includes/authorize-partner-to-create-topic.md)]
 
diff --git a/articles/event-grid/subscribe-to-sap-events.md b/articles/event-grid/subscribe-to-sap-events.md
@@ -30,7 +30,7 @@ If you have any questions, contact us at <a href="mailto:ask-grid-and-ms-sap@mic
 4. [Activate partner topic](#activate-a-partner-topic) so that your events start flowing to your partner topic.
 5. [Subscribe to events](#subscribe-to-events).
 
-[!INCLUDE [register-event-grid-provider](includes/register-event-grid-provider.md)]
+[!INCLUDE [register-provider](includes/register-provider.md)]
 
 [!INCLUDE [authorize-verified-partner-to-create-topic](includes/authorize-verified-partner-to-create-topic.md)]
 
diff --git a/articles/event-grid/subscribe-to-tribal-group-events.md b/articles/event-grid/subscribe-to-tribal-group-events.md
@@ -25,7 +25,7 @@ Following are the prerequisites that your system needs to meet before attempting
 4. [Activate partner topic](#activate-a-partner-topic) so that your events start flowing to your partner topic.
 5. [Subscribe to events](#subscribe-to-events).
 
-[!INCLUDE [register-event-grid-provider](includes/register-event-grid-provider.md)]
+[!INCLUDE [register-provider](includes/register-provider.md)]
 
 [!INCLUDE [authorize-verified-partner-to-create-topic](includes/authorize-verified-partner-to-create-topic.md)]
 
