Merge pull request #259066 from spelluru/patch-22

Preview note

Author: prmerger-automator[bot]

articles/event-grid/namespace-handler-event-hubs.md

@@ -7,12 +7,14 @@ ms.custom:
 ms.date: 11/15/2023
 ---
 
-# Azure Event hubs as a handler destination in subscriptions to Azure Event Grid namespace topics
+# Azure Event hubs as a handler destination in subscriptions to Azure Event Grid namespace topics (Preview)
 
 An event handler is the place where the event is sent. The handler takes an action to process the event. Currently, **Azure Event Hubs** is the only handler supported as a destination for subscriptions to namespace topics.
 
 Use **Event Hubs** when your solution gets events from Event Grid faster than it can process the events. Once the events are in an event hub, your application can process events from the event hub at its own schedule. You can scale your event processing to handle the incoming events.
 
+[!INCLUDE [simple-preview-note](./includes/simple-preview-note.md)]
+
 ## Message headers
 
 Here are the properties you receive in the header of an event or message sent to Event Hubs:

articles/event-grid/namespace-push-delivery-overview.md

@@ -9,7 +9,7 @@ author: robece
 ms.author: robece
 ---
 
-# Azure Event Grid namespaces - Push delivery
+# Azure Event Grid namespaces - Push delivery (Preview)
 
 This article builds on [push delivery with HTTP for Event Grid basic](push-delivery-overview.md) and provides essential information before you start using push delivery on Event Grid namespaces over HTTP protocol. This article is suitable for users who need to build applications to react to discrete events using Event Grid namespaces. If you're interested to know more about the difference between the Event Grid basic tier and the standard tier with namespaces, see [choose the right Event Grid tier for your solution](choose-right-tier.md).