Merge pull request #188670 from spelluru/egridedgeretire

hmacgregor1 · web-flow · commit 878d12caa6a4 · 2022-03-16T20:31:30.000-07:00
Event Grid on IoT Edge - retirement announcement
diff --git a/articles/event-grid/edge/advanced-filtering.md b/articles/event-grid/edge/advanced-filtering.md
@@ -4,7 +4,7 @@ description: Advanced filtering in Event Grid on IoT Edge.
 manager: rajarv
 ms.reviewer: spelluru
 ms.subservice: iot-edge
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.topic: article
 ---
 
@@ -15,6 +15,10 @@ Event Grid allows specifying filters on any property in the json payload. These
 * `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.
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
 ## JSON syntax
 
 The JSON syntax for an advanced filter is as follows:
@@ -65,7 +69,7 @@ The `Key` property can either be a well-known top-level property, or be a json p
 
 Event Grid doesn't have any special meaning for the `$` character in the Key, unlike the JSONPath specification.
 
-### Event grid schema
+### Event Grid schema
 
 For events in the Event Grid schema:
 
diff --git a/articles/event-grid/edge/api.md b/articles/event-grid/edge/api.md
@@ -6,14 +6,18 @@ manager: rajarv
 ms.author: vkukke
 ms.reviewer: spelluru
 ms.subservice: iot-edge
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.topic: article
 ---
 
 
 # REST API
 This article describes the REST APIs of Azure Event Grid on IoT Edge
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
 ## Common API behavior
 
 ### Base URL
diff --git a/articles/event-grid/edge/concepts.md b/articles/event-grid/edge/concepts.md
@@ -5,7 +5,7 @@ author: VidyaKukke
 manager: rajarv
 ms.author: vkukke
 ms.reviewer: spelluru
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.subservice: iot-edge
 ms.topic: article
 ---
@@ -14,6 +14,10 @@ ms.topic: article
 
 This article describes the main concepts in Azure Event Grid.
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
 ## Events
 
 An event is the smallest amount of information that fully describes something that happened in the system. Every event has common information like: source of the event, time the event took place, and unique identifier. Every event also has specific information that is only relevant to the specific type of event. The support for an event of size up to 1 MB is currently in preview.
diff --git a/articles/event-grid/edge/configure-api-protocol.md b/articles/event-grid/edge/configure-api-protocol.md
@@ -5,7 +5,7 @@ author: VidyaKukke
 manager: rajarv
 ms.author: vkukke
 ms.reviewer: spelluru
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.subservice: iot-edge
 ms.topic: article
 ---
@@ -21,6 +21,10 @@ This guide gives examples of the possible protocol configurations of an Event Gr
 
 See [Security and authentication](security-authentication.md) guide for all the possible configurations.
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
 ## Expose HTTPS to IoT Modules on the same edge network
 
 ```json
diff --git a/articles/event-grid/edge/configure-client-auth.md b/articles/event-grid/edge/configure-client-auth.md
@@ -5,7 +5,7 @@ author: VidyaKukke
 manager: rajarv
 ms.author: vkukke
 ms.reviewer: spelluru
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.subservice: iot-edge
 ms.topic: article
 ---
@@ -19,6 +19,11 @@ This guide gives examples of the possible client authentication configurations f
 
 See [Security and authentication](security-authentication.md) guide for all the possible configurations.
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
+
 ## Enable certificate-based client authentication, no self-signed certificates
 
 ```json
diff --git a/articles/event-grid/edge/configure-event-grid.md b/articles/event-grid/edge/configure-event-grid.md
@@ -6,14 +6,19 @@ manager: rajarv
 ms.author: vkukke
 ms.reviewer: spelluru
 ms.subservice: iot-edge
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.topic: article
 ---
 
 # Event Grid Configuration
 
 Event Grid provides many configurations that can be modified per environment. The following section is a reference to all the available options and their defaults.
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
+
 ## TLS configuration
 
 To learn about client authentication in general, see [Security and Authentication](security-authentication.md). Examples of its usage can be found in [this article](configure-api-protocol.md).
diff --git a/articles/event-grid/edge/configure-identity-auth.md b/articles/event-grid/edge/configure-identity-auth.md
@@ -6,7 +6,7 @@ manager: rajarv
 ms.author: vkukke
 ms.reviewer: spelluru
 ms.subservice: iot-edge
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.topic: article
 ---
 
@@ -16,6 +16,11 @@ This article gives shows how to configure identity for Grid on Edge. By default,
 
 See [Security and authentication](security-authentication.md) guide for all the possible configurations.
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
+
 ## Always present identity certificate
 Here's an example configuration for always presenting an identity certificate on outgoing calls. 
 
diff --git a/articles/event-grid/edge/configure-webhook-subscriber-auth.md b/articles/event-grid/edge/configure-webhook-subscriber-auth.md
@@ -6,14 +6,19 @@ manager: rajarv
 ms.author: vkukke
 ms.reviewer: spelluru
 ms.subservice: iot-edge
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.topic: article
 ---
 
 # Configure webhook subscriber authentication
 
 This guide gives examples of the possible webhook subscriber configurations for an Event Grid module. By default, only HTTPS endpoints are accepted for webhook subscribers. The Event Grid module will reject if the subscriber presents a self-signed certificate.
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
+
 ## Allow only HTTPS subscriber
 
 ```json
diff --git a/articles/event-grid/edge/delivery-output-batching.md b/articles/event-grid/edge/delivery-output-batching.md
@@ -4,14 +4,18 @@ description: Output batching in Event Grid on IoT Edge.
 manager: rajarv
 ms.reviewer: spelluru
 ms.subservice: iot-edge
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.topic: article
 ---
 
 # Output batching
 
 Event Grid 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 paying the HTTP per-request overheads. Batching is turned off by default and can be turned on per-subscription.
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge](transition.md). 
+
+
 > [!WARNING]
 > The maximum allowed duration to process each delivery request does not change, even though the subscriber code potentially has to do more work per batched request. Delivery timeout defaults to 60 seconds.
 
diff --git a/articles/event-grid/edge/delivery-retry.md b/articles/event-grid/edge/delivery-retry.md
@@ -6,14 +6,18 @@ manager: rajarv
 ms.author: vkukke
 ms.reviewer: spelluru
 ms.subservice: iot-edge
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.topic: article
 ---
 
 # Delivery and retry
 
 Event Grid provides durable delivery. It tries to deliver each message at least once for each matching subscription immediately. If a subscriber's endpoint doesn't acknowledge receipt of an event or if there is a failure, Event Grid retries delivery based on a fixed **retry schedule** and **retry policy**.  By default, the Event Grid module delivers one event at a time to the subscriber. The payload is however an array with a single event. You can have the module deliver more than one event at a time by enabling the output batching feature. For details about this feature, see [output batching](delivery-output-batching.md).  
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
 > [!IMPORTANT]
 >There is no persistence support for event data. This means redeploying or restart of the Event Grid module will cause you to lose any events that aren't yet delivered.
 
diff --git a/articles/event-grid/edge/event-handlers.md b/articles/event-grid/edge/event-handlers.md
@@ -2,14 +2,19 @@
 title: Event Handlers and destinations - Azure Event Grid IoT Edge | Microsoft Docs 
 description: Event Handlers and destinations in Event Grid on Edge 
 ms.subservice: iot-edge
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.topic: article
 ---
 
 # Event Handlers and destinations in Event Grid on Edge
 
 An event handler is the place where the event for further action or to process the event. With the Event Grid on Edge module, the event handler can be on the same edge device, another device, or in the cloud. You may can use any WebHook to handle events, or send events to one of the native handlers like Azure Event Grid.
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
+
 This article provides information on how to configure each.
 
 ## WebHook
diff --git a/articles/event-grid/edge/event-schemas.md b/articles/event-grid/edge/event-schemas.md
@@ -6,7 +6,7 @@ manager: rajarv
 ms.author: vkukke
 ms.reviewer: spelluru
 ms.subservice: iot-edge
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.topic: article
 ---
 
@@ -23,6 +23,11 @@ You can configure the schema that a publisher must conform to during topic creat
 Subscribers can also configure the schema in which they want the events delivered. If unspecified, default is topic's schema.
 Currently subscriber delivery schema has to match its topic's input schema. 
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
+
 ## EventGrid schema
 
 EventGrid schema consists of a set of required properties that a publishing entity must conform to. Each publisher has to populate the top-level fields.
diff --git a/articles/event-grid/edge/forward-events-event-grid-cloud.md b/articles/event-grid/edge/forward-events-event-grid-cloud.md
@@ -6,7 +6,7 @@ manager: rajarv
 ms.author: vkukke
 ms.reviewer: spelluru
 ms.subservice: iot-edge
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.topic: article
 ---
 
@@ -19,6 +19,11 @@ This article walks through all the steps needed to forward edge events to Event
 
  To complete this tutorial, you need have an understanding of Event Grid concepts on [edge](concepts.md) and [Azure](../concepts.md). For additional destination types, see [event handlers](event-handlers.md). 
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
+
 ## Prerequisites 
 In order to complete this tutorial, you will need:
 
diff --git a/articles/event-grid/edge/forward-events-iothub.md b/articles/event-grid/edge/forward-events-iothub.md
@@ -6,7 +6,7 @@ manager: rajarv
 ms.author: vkukke
 ms.reviewer: spelluru
 ms.subservice: iot-edge
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.topic: article
 ---
 
@@ -17,6 +17,11 @@ This article walks through all the steps needed to forward Event Grid events to
 * Continue to use any existing investments already in place with edgeHub's routing
 * Prefer to route all events from a device only via IoT Hub
 
+
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
 To complete this tutorial, you need to understand the following concepts:
 
 - [Event Grid Concepts](concepts.md)
diff --git a/articles/event-grid/edge/monitor-topics-subscriptions.md b/articles/event-grid/edge/monitor-topics-subscriptions.md
@@ -10,6 +10,11 @@ ms.subservice: iot-edge
 
 Event Grid on Edge exposes a number of metrics for topics and event subscriptions in the [Prometheus exposition format](https://prometheus.io/docs/instrumenting/exposition_formats/). This article describes the available metrics and how to enable them.
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
+
 ## Enable metrics
 
 Configure the module to emit metrics by setting the `metrics__reporterType` environment variable to `prometheus` in the container create options:
diff --git a/articles/event-grid/edge/overview.md b/articles/event-grid/edge/overview.md
@@ -2,7 +2,7 @@
 title: Event driven architectures on edge — Azure Event Grid on IoT Edge
 description: Use Azure Event Grid as a module on IoT Edge for forward events between modules, edge devices, and the cloud.
 ms.topic: overview
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.subservice: iot-edge
 ---
 
diff --git a/articles/event-grid/edge/persist-state-windows.md b/articles/event-grid/edge/persist-state-windows.md
@@ -6,7 +6,7 @@ manager: rajarv
 ms.author: vkukke
 ms.reviewer: spelluru
 ms.subservice: iot-edge
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.topic: article
 ---
 
@@ -18,6 +18,11 @@ By default only metadata is persisted and events are still stored in-memory for
 
 This article provides the steps needed to deploy Event Grid module with persistence in Windows deployments.
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
+
 > [!NOTE]
 >The Event Grid module runs as a low-privileged user **ContainerUser** in Windows.
 
diff --git a/articles/event-grid/edge/pub-sub-events-webhook-cloud.md b/articles/event-grid/edge/pub-sub-events-webhook-cloud.md
@@ -6,7 +6,7 @@ manager: rajarv
 ms.author: vkukke
 ms.reviewer: spelluru
 ms.subservice: iot-edge
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.topic: article
 ms.devlang: csharp
 ms.custom: devx-track-csharp
@@ -18,6 +18,11 @@ This article walks through all the steps needed to publish and subscribe to even
 
 See [Event Grid Concepts](concepts.md) to understand what an event grid topic and subscription are before proceeding.
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
+
 ## Prerequisites 
 In order to complete this tutorial, you will need:
 
diff --git a/articles/event-grid/edge/pub-sub-events-webhook-local.md b/articles/event-grid/edge/pub-sub-events-webhook-local.md
@@ -6,14 +6,19 @@ manager: rajarv
 ms.author: vkukke
 ms.reviewer: spelluru
 ms.subservice: iot-edge
-ms.date: 05/10/2021
+ms.date: 02/15/2022
 ms.topic: article
 ---
 
 # Tutorial: Publish, subscribe to events locally
 
 This article walks you through all the steps needed to publish and subscribe to events using Event Grid on IoT Edge.
 
+> [!IMPORTANT]
+> On March 31, 2023, Event Grid on Azure IoT Edge support will be retired, so make sure to transition to IoT Edge native capabilities prior to that date. For more information, see [Transition from Event Grid on Azure IoT Edge to Azure IoT Edge ](transition.md). 
+
+
+
 > [!NOTE]
 > To learn about Azure Event Grid topics and subscriptions, see [Event Grid Concepts](concepts.md).
 
diff --git a/articles/event-grid/edge/react-blob-storage-events-locally.md b/articles/event-grid/edge/react-blob-storage-events-locally.md
diff --git a/articles/event-grid/edge/release-notes.md b/articles/event-grid/edge/release-notes.md
diff --git a/articles/event-grid/edge/security-authentication.md b/articles/event-grid/edge/security-authentication.md
diff --git a/articles/event-grid/edge/toc.yml b/articles/event-grid/edge/toc.yml
diff --git a/articles/event-grid/edge/transition.md b/articles/event-grid/edge/transition.md
diff --git a/articles/event-grid/edge/troubleshoot.md b/articles/event-grid/edge/troubleshoot.md
diff --git a/articles/event-grid/edge/twin-json.md b/articles/event-grid/edge/twin-json.md
