Merge pull request #245727 from spelluru/egridpreview0720

JamesJBarnett · web-flow · commit 263e9d124081 · 2023-07-21T10:55:26.000-07:00
added preview &amp; preview note to Event Grid V2  articles
diff --git a/articles/event-grid/concepts-pull-delivery.md b/articles/event-grid/concepts-pull-delivery.md
@@ -12,6 +12,8 @@ This article describes the main concepts related to the new resource model that
 > [!NOTE]
 > For Event Grid concepts related to push delivery exclusively used in custom, system, partner, and domain topics, see this [concepts](concepts.md) article.
 
+[!INCLUDE [pull-preview-note](./includes/pull-preview-note.md)]
+
 ## Events
 
 An event is the smallest amount of information that fully describes something that happened in a system. Every event has common information like `source` of the event, `time` the event took place, and a unique identifier. Every event also has specific information that is only relevant to the specific type of event. For example, an event about a new file being created in Azure Storage has details about the file, such as the `lastTimeModified` value. An Event Hubs event has the `URL` of the Capture file. An event about a new order in your Orders microservice may have an `orderId` attribute and a `URL` attribute to the order’s state representation.
diff --git a/articles/event-grid/create-view-manage-event-subscriptions.md b/articles/event-grid/create-view-manage-event-subscriptions.md
@@ -8,6 +8,9 @@ ms.date: 05/24/2023
 ---
 
 # Create, view, and manage event subscriptions in namespace topics
+This article shows you how to create, view, and manage event subscriptions to namespace topics in Azure Event Grid. 
+
+[!INCLUDE [pull-preview-note](./includes/pull-preview-note.md)]
 
 ## Create an event subscription
 
diff --git a/articles/event-grid/create-view-manage-namespace-topics.md b/articles/event-grid/create-view-manage-namespace-topics.md
@@ -9,6 +9,9 @@ ms.date: 05/23/2023
 ---
 
 # Create, view, and manage namespace topics
+This article shows you how to create, view, and manage namespace topics in Azure Event Grid. 
+
+[!INCLUDE [pull-preview-note](./includes/pull-preview-note.md)]
 
 ## Create a namespace topic
 
diff --git a/articles/event-grid/create-view-manage-namespaces.md b/articles/event-grid/create-view-manage-namespaces.md
@@ -12,6 +12,8 @@ ms.date: 05/23/2023
 
 A namespace in Azure Event Grid is a logical container for one or more topics, clients, client groups, topic spaces and permission bindings. It provides a unique namespace, allowing you to have multiple resources in the same Azure region. With an Azure Event Grid namespace you can group now together related resources and manage them as a single unit in your Azure subscription.
 
+[!INCLUDE [mqtt-pull-preview-note](./includes/mqtt-pull-preview-note.md)]
+
 This article shows you how to use the Azure portal to create, view and manage an Azure Event Grid namespace.
 
 ## Create a namespace
diff --git a/articles/event-grid/custom-disaster-recovery-client-side.md b/articles/event-grid/custom-disaster-recovery-client-side.md
@@ -25,6 +25,9 @@ The following table illustrates the client-side failover and geo disaster recove
 | Partner Namespaces  | Supported                                 | Not supported                         |
 | Namespaces          | Supported                                 | Not supported                         |
 
+
+[!INCLUDE [mqtt-pull-preview-note](./includes/mqtt-pull-preview-note.md)]
+
 ## Client-side failover considerations
 
 1. Create and configure your **primary** Event Grid resource.
diff --git a/articles/event-grid/includes/mqtt-preview-note.md b/articles/event-grid/includes/mqtt-preview-note.md
@@ -0,0 +1,14 @@
+---
+ title: include file
+ description: include file
+ services: event-grid
+ author: spelluru
+ ms.service: event-grid
+ ms.topic: include
+ ms.date: 07/20/2023
+ ms.author: spelluru
+ ms.custom: include file
+---
+
+> [!IMPORTANT]
+> The MQTT Messaging feature is currently in PREVIEW. 
diff --git a/articles/event-grid/includes/mqtt-pull-preview-note.md b/articles/event-grid/includes/mqtt-pull-preview-note.md
@@ -0,0 +1,14 @@
+---
+ title: include file
+ description: include file
+ services: event-grid
+ author: spelluru
+ ms.service: event-grid
+ ms.topic: include
+ ms.date: 07/20/2023
+ ms.author: spelluru
+ ms.custom: include file
+---
+
+> [!IMPORTANT]
+> The MQTT Messaging and Pull Delivery features are currently in PREVIEW. 
diff --git a/articles/event-grid/includes/pull-preview-note.md b/articles/event-grid/includes/pull-preview-note.md
@@ -0,0 +1,14 @@
+---
+ title: include file
+ description: include file
+ services: event-grid
+ author: spelluru
+ ms.service: event-grid
+ ms.topic: include
+ ms.date: 07/20/2023
+ ms.author: spelluru
+ ms.custom: include file
+---
+
+> [!IMPORTANT]
+> The Pull Delivery feature is currently in PREVIEW.
diff --git a/articles/event-grid/index.yml b/articles/event-grid/index.yml
@@ -34,7 +34,7 @@ landingContent:
           - text: MQTT Messaging
             url: mqtt-overview.md
  # Card
-  - title: MQTT messaging
+  - title: MQTT messaging (Preview)
     linkLists:
       - linkListType: overview
         links:
@@ -102,7 +102,7 @@ landingContent:
             url: onboard-partner.md
 
  # Card
-  - title: Pull delivery
+  - title: Pull delivery (Preview)
     linkLists:
       - linkListType: concept
         links:
diff --git a/articles/event-grid/monitor-mqtt-delivery-reference.md b/articles/event-grid/monitor-mqtt-delivery-reference.md
@@ -9,6 +9,8 @@ ms.date: 05/23/2023
 # Monitor data reference for Azure Event Grid's MQTT delivery
 This article provides a reference of log and metric data collected to analyze the performance and availability of Azure Event Grid's MQTT delivery. 
 
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
 ## Metrics
 
 | Metric | Display name | Unit | Aggregation | Description | Dimensions | 
diff --git a/articles/event-grid/monitor-pull-reference.md b/articles/event-grid/monitor-pull-reference.md
@@ -9,6 +9,8 @@ ms.date: 04/28/2023
 # Monitor data reference for Azure Event Grid's pull event delivery
 This article provides a reference of log and metric data collected to analyze the performance and availability of Azure Event Grid's pull delivery. 
 
+[!INCLUDE [pull-preview-note](./includes/pull-preview-note.md)]
+
 ## Metrics
 
 ### Microsoft.EventGrid/namespaces 
diff --git a/articles/event-grid/mqtt-access-control.md b/articles/event-grid/mqtt-access-control.md
@@ -8,7 +8,11 @@ ms.author: geguirgu
 ---
 # Access control for MQTT clients
 
-Access control enables you to manage the authorization of clients to publish or subscribe to topics, using a role-based access control model. Given the enormous scale of IoT environments, assigning permission for each client to each topic is incredibly tedious. Event Grid’s flexible access control tackles this scale challenge through grouping clients and topics into client groups and topic spaces. The main components of the access control model are:
+Access control enables you to manage the authorization of clients to publish or subscribe to topics, using a role-based access control model. Given the enormous scale of IoT environments, assigning permission for each client to each topic is incredibly tedious. Event Grid’s flexible access control tackles this scale challenge through grouping clients and topics into client groups and topic spaces. 
+
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
+The main components of the access control model are:
 
 A **[client](mqtt-clients.md)** represents the device or application that needs to publish and/or subscribe to MQTT topics.
 
@@ -20,6 +24,8 @@ A **permission binding** grants access to a specific client group to publish or
 
 :::image type="content" source="media/mqtt-overview/access-control-high-res.png" alt-text="Diagram of the access control model." border="false":::
 
+
+
 ## Examples:
 
 The following examples detail how to configure the access control model based on the following requirements.
diff --git a/articles/event-grid/mqtt-automotive-connectivity-and-data-solution.md b/articles/event-grid/mqtt-automotive-connectivity-and-data-solution.md
@@ -11,6 +11,8 @@ ms.author: marioo
 
 This reference architecture is designed to support automotive OEMs and Mobility Providers in the development of advanced connected vehicle applications and digital services. Its goal is to provide reliable and efficient messaging, data and analytics infrastructure. The architecture includes message processing, command processing, and state storage capabilities to facilitate the integration of various services through managed APIs. It also describes a data and analytics solution that ensures the storage and accessibility of data in a scalable and secure manner for digital engineering and data sharing with the wider mobility ecosystem.
 
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
 ## Architecture
 
 :::image type="content" source="media/mqtt-automotive-connectivity-and-data-solution/high-level-architecture.png" alt-text="Diagram of the high-level architecture." border="false" lightbox="media/mqtt-automotive-connectivity-and-data-solution/high-level-architecture.png":::
diff --git a/articles/event-grid/mqtt-certificate-chain-client-authentication.md b/articles/event-grid/mqtt-certificate-chain-client-authentication.md
@@ -11,6 +11,8 @@ ms.author: veyaddan
 # Client authentication using CA certificate chain
 Use CA certificate chain in Azure Event Grid to authenticate clients while connecting to the service.
 
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
 In this guide, you perform the following tasks:
 1. Upload a CA certificate, the immediate parent certificate of the client certificate, to the namespace.
 2. Configure client authentication settings.
diff --git a/articles/event-grid/mqtt-client-authentication.md b/articles/event-grid/mqtt-client-authentication.md
@@ -12,6 +12,8 @@ ms.author: veyaddan
 
 We support authentication of clients using X.509 certificates.  X.509 certificate provides the credentials to associate a particular client with the tenant.  In this model, authentication generally happens once during session establishment.  Then, all future operations using the same session are assumed to come from that identity.  
 
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
 ## Supported authentication modes
 
 - Certificates issued by a Certificate Authority (CA)
diff --git a/articles/event-grid/mqtt-client-groups.md b/articles/event-grid/mqtt-client-groups.md
@@ -11,6 +11,8 @@ ms.author: veyaddan
 # Client groups
 Client groups allow you to group a set of client together based on commonalities.  The main purpose of client groups is to make configuring authorization easy.  You can authorize a client group to publish or subscribe to a topic space.  All the clients in the client group are authorized to perform the publish or subscribe action on the topic space.
 
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
 In a namespace, we provide a default client group named "$all".  The client group includes all the clients in the namespace.  For ease of testing, you can use $all to configure permissions.
 
 > [!NOTE]
diff --git a/articles/event-grid/mqtt-client-life-cycle-events.md b/articles/event-grid/mqtt-client-life-cycle-events.md
@@ -11,6 +11,8 @@ ms.author: geguirgu
 
 Client Life Cycle events allow applications to react to client connection or disconnection events. For example, you can build an application that updates a database, creates a ticket, and delivers an email notification every time a client is disconnected for mitigating action.
 
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
 ## Event types
 
 The Event Grid namespace publishes the following event types:
diff --git a/articles/event-grid/mqtt-clients.md b/articles/event-grid/mqtt-clients.md
@@ -11,6 +11,8 @@ ms.author: veyaddan
 # MQTT clients
 In this article, you learn about configuring MQTT clients and client groups.
 
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
 ## Clients
 Clients can be devices or applications, such as devices or vehicles that send/receive MQTT messages.
 
diff --git a/articles/event-grid/mqtt-establishing-multiple-sessions-per-client.md b/articles/event-grid/mqtt-establishing-multiple-sessions-per-client.md
@@ -12,6 +12,8 @@ ms.author: veyaddan
 
 In this guide, you learn how to establish multiple sessions for a single client to an Event Grid namespace.
 
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
 ## Prerequisites
 - You have an Event Grid namespace created.  Refer to this [Quickstart - Publish and subscribe on a MQTT topic](mqtt-publish-and-subscribe-portal.md) to create the namespace, subresources, and to publish/subscribe on a topic.
 
diff --git a/articles/event-grid/mqtt-event-grid-namespace-terminology.md b/articles/event-grid/mqtt-event-grid-namespace-terminology.md
@@ -11,6 +11,8 @@ ms.author: veyaddan
 # Terminology
 Key terms relevant for Event Grid namespace and MQTT resources are explained.
 
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
 ## Namespace
 
 An Event Grid namespace is a declarative space that provides a scope to all the nested resources or subresources such as topics, certificates, clients, client groups, topic spaces, permission bindings.  
diff --git a/articles/event-grid/mqtt-overview.md b/articles/event-grid/mqtt-overview.md
@@ -1,5 +1,5 @@
 ---
-title: 'Overview of the MQTT Support in Azure Event Grid'
+title: 'Overview of MQTT Support in Azure Event Grid (preview)'
 description: 'Describes the main concepts for the MQTT Support in Azure Event Grid.'
 ms.topic: conceptual
 ms.date: 05/23/2023
@@ -8,7 +8,12 @@ ms.author: geguirgu
 ---
 # Overview of the MQTT Support in Azure Event Grid (Preview)
 
-Azure Event Grid enables your MQTT clients to communicate with each other and with Azure services, to support your Internet of Things (IoT) solutions. Event Grid’s MQTT support enables you to accomplish the following scenarios:
+Azure Event Grid enables your MQTT clients to communicate with each other and with Azure services, to support your Internet of Things (IoT) solutions. 
+
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
+Event Grid’s MQTT support enables you to accomplish the following scenarios:
+
 - Ingest telemetry using a many-to-one messaging pattern. This pattern enables the application to offload the burden of managing the high number of connections with devices to Event Grid.
 - Control your MQTT clients using the request-response (one-to-one) messaging pattern. This pattern enables any client to communicate with any other client without restrictions, regardless of the clients' roles.
 - Broadcast alerts to a fleet of clients using the one-to-many messaging pattern. This pattern enables the application to publish only one message that the service replicates for every interested client.
@@ -20,8 +25,7 @@ The MQTT support in Event Grid is ideal for the implementation of automotive and
 
 :::image type="content" source="media/overview/mqtt-messaging-high-res.png" alt-text="High-level diagram of Event Grid that shows bidirectional MQTT communication with publisher and subscriber clients." border="false":::
 
-> [!NOTE]
-> This feature is currently in preview. It's provided without a service level agreement, and is not recommended for production workloads. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+
 
 ## Key concepts:
 The following are a list of key concepts involved in MQTT messaging on Event Grid.
diff --git a/articles/event-grid/mqtt-publish-and-subscribe-cli.md b/articles/event-grid/mqtt-publish-and-subscribe-cli.md
@@ -12,6 +12,8 @@ ms.author: veyaddan
 
 Azure Event Grid supports messaging using the MQTT protocol.  Clients (both devices and cloud applications) can publish and subscribe MQTT messages over flexible hierarchical topics for scenarios such as high scale broadcast, and command & control.
 
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
 In this article, you use the Azure CLI to do the following tasks:
 1. Create an Event Grid namespace and enable MQTT
 2. Create subresources such as clients, client groups, and topic spaces
diff --git a/articles/event-grid/mqtt-publish-and-subscribe-portal.md b/articles/event-grid/mqtt-publish-and-subscribe-portal.md
@@ -17,6 +17,8 @@ In this article, you use the Azure portal to do the following tasks:
 3. Grant clients access to publish and subscribe to topic spaces
 4. Publish and receive messages between clients
 
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)] 
+
 ## Prerequisites
 
 - If you don't have an Azure subscription, create an Azure free account before you begin.
diff --git a/articles/event-grid/mqtt-routing-enrichment.md b/articles/event-grid/mqtt-routing-enrichment.md
@@ -8,22 +8,22 @@ author: george-guirguis
 ms.author: geguirgu
 ---
 # Enrichments for MQTT Routed Messages
-
-
 The enrichments support enables you to add up to 20 custom key-value properties to your messages before they're sent to the Event Grid custom topic. These enrichments enable you to:
 
 - Add contextual data to your messages. For example, enriching the message with the client's name or the namespace name could provide endpoints with information about the source of the message.
 - Reduce computing load on endpoints. For example, enriching the message with the MQTT publish request's payload format indicator or the content type informs endpoints how to process the message's payload without trying multiple parsers first.
 - Filter your routed messages through Event Grid event subscriptions based on the added data. For example, enriching a client attribute enables you to filter the messages to be routed to the endpoint based on the different attribute's values.
 
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)] 
+
 ## Configuration
 
 ### Enrichment Key:
 
 The enrichment key is a string that needs to comply with these requirements:
 - Include only lower-case alphanumerics: only (a-z) and (0-9)
-- Must not be "specversion", "id", "time", "type", "source", "subject", "datacontenttype", "dataschema", "data", or "data_base64".
-- Must not start with “azsp”.
+- Must not be `specversion`, `id`, `time`, `type`, `source`, `subject`, `datacontenttype`, `dataschema`, `data`, or `data_base64`.
+- Must not start with `azsp`.
 - Must not be duplicated.
 - Must not be more than 20 characters.
 
@@ -165,8 +165,8 @@ The following CloudEvent is a sample output of a MQTTv5 message with PFI=0 after
 
 ### Handling special cases:
 
-- Unspecified client attributes/user properties: if a dynamic enrichment pointed to a client attribute/user property that doesn’t exist, the enrichment will include the specified key with an empty string for a value. For example, "emptyproperty": "".
-- Arrays: Arrays in client attributes and duplicate user properties are transformed to a comma-separated string. For example: if the enriched client attribute is set to be “array”: “value1”, “value2”, “value3”, the resulting enriched property will be “array”: “value1,value2,value3”. Another example: if the same MQTT publish request has the following user properties > "userproperty1": "value1", "userproperty1": "value2", resulting enriched property will be “userproperty1”: “value1,value2”.
+- Unspecified client attributes/user properties: if a dynamic enrichment pointed to a client attribute/user property that doesn’t exist, the enrichment will include the specified key with an empty string for a value. For example, `emptyproperty`: "".
+- Arrays: Arrays in client attributes and duplicate user properties are transformed to a comma-separated string. For example: if the enriched client attribute is set to be “array”: “value1”, “value2”, “value3”, the resulting enriched property will be `array`: `value1,value2,value3`. Another example: if the same MQTT publish request has the following user properties > "userproperty1": "value1", "userproperty1": "value2", resulting enriched property will be `userproperty1`: `value1,value2`.
 
 ## Next steps:
 
diff --git a/articles/event-grid/mqtt-routing-event-schema.md b/articles/event-grid/mqtt-routing-event-schema.md
@@ -8,6 +8,9 @@ author: george-guirguis
 ms.author: geguirgu
 ---
 # Event Schema for MQTT Routed Messages
+
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
 MQTT Messages are routed to an Event Grid topic as CloudEvents according to the following logic:
 
 For MQTT v3 messages or MQTT v5 messages of a payload format indicator=0, the payload will be forwarded in the data_base64 object and encoded as a base 64 string according to the following schema sample.
diff --git a/articles/event-grid/mqtt-routing-filtering.md b/articles/event-grid/mqtt-routing-filtering.md
@@ -10,6 +10,8 @@ ms.author: geguirgu
 # Filtering of MQTT Routed Messages
 You can use the Event Grid Subscription’s filtering capability to filter the routed MQTT messages.
 
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
 ## Topic filtering
 
 You can filter on the messages’ MQTT topics through filtering on the "subject" property in the Cloud Event schema. Event Grid Subscriptions supports free simple subject filtering by specifying a starting or ending value for the subject. For example,
diff --git a/articles/event-grid/mqtt-routing-to-event-hubs-cli.md b/articles/event-grid/mqtt-routing-to-event-hubs-cli.md
@@ -13,6 +13,8 @@ ms.author: veyaddan
 
 Use message routing in Azure Event Grid to send data from your MQTT clients to Azure services such as storage queues, and Event Hubs.
 
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
 In this article, you perform the following tasks:
 - Create Event Subscription in your Event Grid topic
 - Configure routing in your Event Grid Namespace
diff --git a/articles/event-grid/mqtt-routing-to-event-hubs-portal.md b/articles/event-grid/mqtt-routing-to-event-hubs-portal.md
@@ -16,6 +16,8 @@ In this tutorial, you perform the following tasks:
 - Configure routing in your Event Grid Namespace.
 - View the MQTT messages in the Event Hubs using Azure Stream Analytics.
 
+[!INCLUDE [mqtt-preview-note](./includes/mqtt-preview-note.md)]
+
 ## Prerequisites
 
 - If you don't have an [Azure subscription](/azure/guides/developer/azure-developer-guide#understanding-accounts-subscriptions-and-billing), create an [Azure free account](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio) before you begin.
diff --git a/articles/event-grid/mqtt-routing.md b/articles/event-grid/mqtt-routing.md
diff --git a/articles/event-grid/mqtt-support.md b/articles/event-grid/mqtt-support.md
diff --git a/articles/event-grid/mqtt-topic-spaces.md b/articles/event-grid/mqtt-topic-spaces.md
diff --git a/articles/event-grid/mqtt-troubleshoot-errors.md b/articles/event-grid/mqtt-troubleshoot-errors.md
diff --git a/articles/event-grid/overview.md b/articles/event-grid/overview.md
diff --git a/articles/event-grid/publish-events-using-namespace-topics.md b/articles/event-grid/publish-events-using-namespace-topics.md
diff --git a/articles/event-grid/pull-delivery-overview.md b/articles/event-grid/pull-delivery-overview.md
diff --git a/articles/event-grid/whats-new.md b/articles/event-grid/whats-new.md
