MQTT broker change

Author: Venkata Yaddanapudi

articles/event-grid/mqtt-overview.md

@@ -1,6 +1,6 @@
 ---
-title: 'Overview of MQTT Support in Azure Event Grid'
-description: 'Describes the main concepts for the MQTT Support in Azure Event Grid.'
+title: 'Overview of MQTT broker feature in Azure Event Grid'
+description: 'Describes the main concepts for the MQTT broker feature in Azure Event Grid.'
 ms.topic: conceptual
 ms.custom:
   - ignite-2023
@@ -9,11 +9,11 @@ author: george-guirguis
 ms.author: geguirgu
 ---
 
-# Overview of the MQTT Support in Azure Event Grid
+# Overview of the MQTT broker feature in Azure Event Grid
 
 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’s MQTT broker feature 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.
@@ -57,7 +57,7 @@ MQTT is a publish-subscribe messaging transport protocol that was designed for c
 
 The publish-subscribe messaging model provides a scalable and asynchronous communication to clients. It enables clients to offload the burden of handling a high number of connections and messages to the service. Through the Publish-Subscribe messaging model, your clients can communicate efficiently using one-to-many, many-to-one, and one-to-one messaging patterns. 
 - The one-to-many messaging pattern enables clients to publish only one message that the service replicates for every interested client. 
-- The many-to-one messaging pattern enables clients to offload the burden of managing the high number of connections to MQTT broker. 
+- The many-to-one messaging pattern enables clients to offload the burden of managing the high number of connections to MQTT broker.
 - The one-to-one messaging pattern enables any client to communicate with any other client without restrictions, regardless of the clients' roles.
 
 ### Namespace
@@ -74,7 +74,7 @@ IoT applications are software designed to interact with and process data from Io
 
 ### Client authentication
 
-Event Grid has a client registry that stores information about the clients permitted to connect to it. Before a client can connect, there must be an entry for that client in the client registry. As a client connects to MQTT broker, it needs to authenticate with MQTT broker based on credentials stored in the identity registry. MQTT broker supports X.509 certificate authentication that is the industry authentication standard in IoT devices and [Microsoft Entra ID (formerly Azure Active Directory)](mqtt-client-azure-ad-token-and-rbac.md) that is Azure's authentication standard for applications.[Learn more about MQTT client authentication.](mqtt-client-authentication.md)
+Event Grid has a client registry that stores information about the clients permitted to connect to it. Before a client can connect, there must be an entry for that client in the client registry. As a client connects to MQTT broker, it needs to authenticate with MQTT broker based on credentials stored in the identity registry.  MQTT broker supports X.509 certificate authentication that is the industry authentication standard in IoT devices and [Microsoft Entra ID (formerly Azure Active Directory)](mqtt-client-azure-ad-token-and-rbac.md) that is Azure's authentication standard for applications.[Learn more about MQTT client authentication.](mqtt-client-authentication.md)
 
 ### Access control
 
@@ -93,9 +93,9 @@ Event Grid allows you to route your MQTT messages to Azure services or webhooks
 :::image type="content" source="media/mqtt-overview/routing-high-res.png" alt-text="Diagram of the MQTT message routing." border="false":::
 
 ### Edge MQTT broker integration
-Event Grid integrates with [Azure IoT MQ](https://aka.ms/iot-mq) to bridge its MQTT broker capability on the edge with Event Grid’s MQTT broker capability in the cloud. Azure IoT MQ is a new distributed MQTT broker for edge computing, running on Arc enabled Kubernetes clusters. It can connect to Event Grid MQTT broker with Microsoft Entra ID (formerly Azure Active Directory) authentication using system-assigned managed identity, which simplifies credential management. Azure IoT MQ provides high availability, scalability, and security for your IoT devices and applications. It's now available in [public preview](https://aka.ms/iot-mq-preview) as part of Azure IoT Operations. [Learn more about connecting Azure IoT MQ to Azure Event Grid's MQTT broker](https://aka.ms/iot-mq-eg-bridge)
+Event Grid integrates with [Azure IoT MQ](https://aka.ms/iot-mq) to bridge its MQTT broker capability on the edge with Azure Event Grid’s MQTT broker feature in the cloud.  Azure IoT MQ is a new distributed MQTT broker for edge computing, running on Arc enabled Kubernetes clusters. It can connect to Event Grid MQTT broker with Microsoft Entra ID (formerly Azure Active Directory) authentication using system-assigned managed identity, which simplifies credential management. Azure IoT MQ provides high availability, scalability, and security for your IoT devices and applications. It's now available in [public preview](https://aka.ms/iot-mq-preview) as part of Azure IoT Operations. [Learn more about connecting Azure IoT MQ to Azure Event Grid's MQTT broker](https://aka.ms/iot-mq-eg-bridge)
 
-### MQTT Clients Life Cycle Events 
+### MQTT Clients Life Cycle Events
 
 Client Life Cycle events allow applications to react to events about the client connection status or the client resource operations. It allows you to keep track of your client's connection status, react with a mitigation action for client disconnections, and track the namespace that your clients are attached to during automated failovers.Learn more about [MQTT Client Life Cycle Events](mqtt-client-life-cycle-events.md).
 

articles/event-grid/mqtt-publish-and-subscribe-cli.md

@@ -17,7 +17,7 @@ Azure Event Grid’s MQTT broker feature supports messaging using the MQTT proto
 
 
 In this article, you use the Azure CLI to do the following tasks:
-1. Create an Event Grid namespace and enable MQTT
+1. Create an Event Grid namespace and enable MQTT broker
 2. Create subresources such as clients, client groups, and topic spaces
 3. Grant clients access to publish and subscribe to topic spaces
 4. Publish and receive MQTT messages

articles/event-grid/mqtt-publish-and-subscribe-portal.md

@@ -14,7 +14,7 @@ ms.author: veyaddan
 
 In this article, you use the Azure portal to do the following tasks:
 
-1. Create an Event Grid namespace and enable MQTT
+1. Create an Event Grid namespace and enable MQTT broker
 2. Create sub resources such as clients, client groups, and topic spaces
 3. Grant clients access to publish and subscribe to topic spaces
 4. Publish and receive messages between clients
@@ -81,15 +81,15 @@ After a successful installation of Step, you should open a command prompt in you
     > [!NOTE]
     > To keep the QuickStart simple, you'll be using only the Basics page to create a namespace. For detailed steps about configuring network, security, and other settings on other pages of the wizard, see [Create a Namespace](create-view-manage-namespaces.md).
 1. After the deployment succeeds, select **Go to resource** to navigate to the Event Grid Namespace Overview page for your namespace.
-1. In the Overview page, you see that the **MQTT** is in **Disabled** state. To enable MQTT, select the **Disabled** link, it will redirect you to Configuration page.
-1. On **Configuration** page, select the **Enable MQTT** option, and then select **Apply** to apply the settings.
+1. In the Overview page, you see that the **MQTT broker** is in **Disabled** state. To enable MQTT broker, select the **Disabled** link, it will redirect you to Configuration page.
+1. On **Configuration** page, select the **Enable MQTT broker** option, and then select **Apply** to apply the settings.
 
     :::image type="content" source="./media/mqtt-publish-and-subscribe-portal/mqtt-enable-mqtt-on-configuration.png" alt-text="Screenshot showing Event Grid namespace configuration page to enable MQTT." lightbox="./media/mqtt-publish-and-subscribe-portal/mqtt-enable-mqtt-on-configuration.png":::
 
 
 ## Create clients
 
-1. On the left menu, select **Clients** in the **MQTT** section.
+1. On the left menu, select **Clients** in the **MQTT broker** section.
 2. On the **Clients** page, select **+ Client** on the toolbar.
 
     :::image type="content" source="./media/mqtt-publish-and-subscribe-portal/add-client-menu.png" alt-text="Screenshot of the Clients page with Add button selected." lightbox="./media/mqtt-publish-and-subscribe-portal/add-client-menu.png":::
@@ -109,7 +109,7 @@ After a successful installation of Step, you should open a command prompt in you
     
 ## Create topic spaces
 
-1. On the left menu, select **Topic spaces** in the **MQTT** section.
+1. On the left menu, select **Topic spaces** in the **MQTT broker** section.
 2. On the **Topic spaces** page, select **+ Topic space** on the toolbar.
 
     :::image type="content" source="./media/mqtt-publish-and-subscribe-portal/create-topic-space-menu.png" alt-text="Screenshot of Topic spaces page with create button selected." lightbox="./media/mqtt-publish-and-subscribe-portal/create-topic-space-menu.png":::
@@ -123,7 +123,7 @@ After a successful installation of Step, you should open a command prompt in you
 
 ## Configuring access control using permission bindings
 
-1. On the left menu, select **Permission bindings** in the **MQTT** section.
+1. On the left menu, select **Permission bindings** in the **MQTT broker** section.
 2. On the Permission bindings page, select **+ Permission binding** on the toolbar.
 
     :::image type="content" source="./media/mqtt-publish-and-subscribe-portal/create-permission-binding-menu.png" alt-text="Screenshot that shows the Permission bindings page with the Create button selected." lightbox="./media/mqtt-publish-and-subscribe-portal/create-permission-binding-menu.png":::