freshness review & update

Author: spelluru

articles/service-bus-messaging/includes/event-grid-service-bus.md

@@ -5,7 +5,7 @@
  author: spelluru
  ms.service: event-grid
  ms.topic: include
- ms.date: 10/20/2021
+ ms.date: 12/08/2022
  ms.author: spelluru
  ms.custom: include file
 ---
@@ -16,16 +16,16 @@ Service Bus emits the following event types:
 
 | Event type | Description |
 | ---------- | ----------- |
-| Microsoft.ServiceBus.ActiveMessagesAvailableWithNoListeners | Raised when there are active messages in a Queue or Subscription and no receivers listening. |
-| Microsoft.ServiceBus.DeadletterMessagesAvailableWithNoListeners | Raised when there are active messages in a Dead Letter Queue and no active listeners. |
-| Microsoft.ServiceBus.ActiveMessagesAvailablePeriodicNotifications | Raised every 30 seconds if there are active messages in a queue or subscription, even if there are active listeners on that specific queue or subscription. It's also raised when the active message count transitions from 0 to a positive value for the queue or subscription. |
-| Microsoft.ServiceBus.DeadletterMessagesAvailablePeriodicNotifications | Raised every 30 seconds if there are messages in the dead-letter entity of a queue or subscription, even if there are active listeners on the dead-letter entity of that specific queue or subscription. It's also raised when the dead-letter message count transitions from 0 to a positive value for the dead-letter entity of the queue or subscription. | 
+| `Microsoft.ServiceBus.ActiveMessagesAvailableWithNoListeners` | Raised when there are active messages in a queue or subscription and no receivers listening. |
+| `Microsoft.ServiceBus.DeadletterMessagesAvailableWithNoListeners` | Raised when there are active messages in a dead letter queue and no active listeners. |
+| `Microsoft.ServiceBus.ActiveMessagesAvailablePeriodicNotifications` | Raised every 30 seconds if there are active messages in a queue or subscription, even if there are active listeners on that specific queue or subscription. It's also raised when the active message count transitions from 0 to a positive value for the queue or subscription. |
+| `Microsoft.ServiceBus.DeadletterMessagesAvailablePeriodicNotifications` | Raised every 30 seconds if there are messages in the dead-letter entity of a queue or subscription, even if there are active listeners on the dead-letter entity of that specific queue or subscription. It's also raised when the dead-letter message count transitions from 0 to a positive value for the dead-letter entity of the queue or subscription. | 
 
 ## Example event
 
 # [Event Grid event schema](#tab/event-grid-event-schema)
 
-### Active Messages Available With No Listeners
+### Active messages available with no listeners
 This event is generated if you have active messages in a queue or a subscription and there are no receivers listening.
 
 ```json
@@ -48,7 +48,7 @@ This event is generated if you have active messages in a queue or a subscription
 }]
 ```
 
-#### Deadletter Messages Available With No Listeners
+#### Dead-letter messages available with no listeners
 
 The schema for a dead letter queue event is similar. You get at least one event per dead-letter queue that has messages and no active receivers.
 
@@ -72,8 +72,8 @@ The schema for a dead letter queue event is similar. You get at least one event
 }]
 ```
 
-#### Active Messages Available Periodic Notifications
-This event is generated periodically if you have active messages on the specific queue or subscription, even if there are active listeners on that specific queue or subscription.
+#### Active messages available periodic notifications
+This event is generated periodically if you have active messages in the specific queue or subscription, even if there are active listeners for that specific queue or subscription.
 
 ```json
 [{
@@ -95,7 +95,7 @@ This event is generated periodically if you have active messages on the specific
 }]
 ```
 
-#### Deadletter Messages Available Periodic Notifications
+#### Dead-letter messages available periodic notifications
 This event is generated periodically if you have deadletter messages on the specific queue or subscription, even if there are active listeners on the deadletter entity of that specific queue or subscription.
 
 ```json
@@ -120,7 +120,7 @@ This event is generated periodically if you have deadletter messages on the spec
 
 # [Cloud event schema](#tab/cloud-event-schema)
 
-### Active Messages Available With No Listeners
+### Active messages available with no listeners
 This event is generated if you have active messages in a queue or a subscription and there are no receivers listening.
 
 ```json
@@ -142,7 +142,7 @@ This event is generated if you have active messages in a queue or a subscription
 }]
 ```
 
-#### Deadletter Messages Available With No Listeners
+#### Deadletter messages available with no listeners
 
 The schema for a dead letter queue event is similar. You get at least one event per dead-letter queue that has messages and no active receivers.
 
@@ -165,7 +165,7 @@ The schema for a dead letter queue event is similar. You get at least one event
 }]
 ```
 
-#### Active Messages Available Periodic Notifications
+#### Active messages available periodic notifications
 This event is generated periodically if you have active messages on the specific queue or subscription, even if there are active listeners on that specific queue or subscription.
 
 ```json
@@ -187,7 +187,7 @@ This event is generated periodically if you have active messages on the specific
 }]
 ```
 
-#### Deadletter Messages Available Periodic Notifications
+#### Deadletter messages available periodic notifications
 This event is generated periodically if you have deadletter messages on the specific queue or subscription, even if there are active listeners on the deadletter entity of that specific queue or subscription.
 
 ```json
@@ -220,7 +220,7 @@ An event has the following top-level data:
 
 | Property | Type | Description |
 | -------- | ---- | ----------- |
-| `topic` | string | Full resource path to the event source. This field is not writeable. Event Grid provides this value. |
+| `topic` | string | Full resource path to the event source. This field isn't writeable. Event Grid provides this value. |
 | `subject` | string | Publisher-defined path to the event subject. |
 | `eventType` | string | One of the registered event types for this event source. |
 | `eventTime` | string | The time the event is generated based on the provider's UTC time. |
@@ -235,7 +235,7 @@ An event has the following top-level data:
 
 | Property | Type | Description |
 | -------- | ---- | ----------- |
-| `source` | string | Full resource path to the event source. This field is not writeable. Event Grid provides this value. |
+| `source` | string | Full resource path to the event source. This field isn't writeable. Event Grid provides this value. |
 | `subject` | string | Publisher-defined path to the event subject. |
 | `type` | string | One of the registered event types for this event source. |
 | `time` | string | The time the event is generated based on the provider's UTC time. |

articles/service-bus-messaging/includes/service-bus-event-grid-prerequisites.md

@@ -5,7 +5,7 @@ services: service-bus-messaging
 author: spelluru
 ms.service: service-bus-messaging
 ms.topic: include
-ms.date: 09/29/2021
+ms.date: 12/08/2022
 ms.author: spelluru
 ms.custom: "include file"
 

articles/service-bus-messaging/media/service-bus-to-event-grid-integration-example/logic-app-shared-access-key.png

@@ -4,13 +4,13 @@ description: This article provides a description of how Azure Service Bus messag
 documentationcenter: .net
 author: spelluru
 ms.topic: conceptual
-ms.date: 12/02/2022
+ms.date: 12/08/2022
 ms.author: spelluru 
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
 ---
 
 # Azure Service Bus to Event Grid integration overview
-Service Bus can now emit events to Event Grid when there are messages in a queue or a subscription when no receivers are present. You can create Event Grid subscriptions to your Service Bus namespaces, listen to these events, and then react to the events by starting a receiver. With this feature, you can use Service Bus in reactive programming models. The key scenario of this feature is that Service Bus queues or subscriptions with a low volume of messages do not need to have a receiver that polls for messages continuously. 
+Service Bus can emit events to Event Grid when there are messages in a queue or a subscription when no receivers are present. You can create Event Grid subscriptions to your Service Bus namespaces, listen to these events, and then react to the events by starting a receiver. With this feature, you can use Service Bus in reactive programming models. The key scenario of this feature is that Service Bus queues or subscriptions with a low volume of messages do not need to have a receiver that polls for messages continuously. 
 
 To enable the feature, you need the following items:
 
@@ -43,7 +43,7 @@ You can create Event Grid subscriptions for Service Bus namespaces in three diff
     ```
 ### How many events are emitted, and how often?
 
-If you have multiple queues and topics or subscriptions in the namespace, you get at least one event per queue and one per subscription. The events are emitted immediately if there are no messages in the Service Bus entity and a new message arrives. Or the events are emitted every two minutes unless Service Bus detects an active receiver. Message browsing does not interrupt the events.
+If you have multiple queues and topics or subscriptions in the namespace, you get at least one event per queue and one per subscription. The events are emitted immediately if there are no messages in the Service Bus entity and a new message arrives. Or the events are emitted every two minutes unless Service Bus detects an active receiver. Message browsing doesn't interrupt the events.
 
 By default, Service Bus emits events for all entities in the namespace. If you want to get events for specific entities only, see the next section.
 

articles/service-bus-messaging/service-bus-to-event-grid-integration-concept.md

@@ -4,7 +4,7 @@ description: This article provides steps for handling Service Bus events via Eve
 documentationcenter: .net
 author: spelluru
 ms.topic: tutorial
-ms.date: 10/04/2021
+ms.date: 12/08/2022
 ms.author: spelluru
 ---
 
@@ -33,7 +33,7 @@ In this step, you create an Azure logic app that receives Service Bus events via
     1. Search for **Event Grid**. 
     2. Select **When a resource event occurs - Azure Event Grid**. 
 
-        ![Logic Apps Designer - select Event Grid trigger](./media/service-bus-to-event-grid-integration-example/logic-apps-event-grid-trigger.png)
+        :::image type="content" source="./media/service-bus-to-event-grid-integration-example/logic-apps-event-grid-trigger.png" alt-text="Screenshot of showing the Logic Apps Designer with Event Grid trigger selected.":::
 4. Select **Sign in**, enter your Azure credentials, and select **Allow Access**. 
 5. On the **When a resource event occurs** page, do the following steps:
     1. Select your Azure subscription. 
@@ -43,23 +43,26 @@ In this step, you create an Azure logic app that receives Service Bus events via
 
         :::image type="content" source="./media/service-bus-to-event-grid-integration-example/add-new-parameter-suffix-filter.png" alt-text="Image showing the addition of a suffix filter.":::
     1. For **Suffix Filter**, enter the name of your Service Bus topic subscription. 
-        ![Logic Apps Designer - configure event](./media/service-bus-to-event-grid-integration-example/logic-app-configure-event.png)
+    
+        :::image type="content" source="./media/service-bus-to-event-grid-integration-example/logic-apps-event-grid-trigger.png" alt-text="Screenshot of showing the Logic Apps Designer with connection configuration for the Service Bus namespace.":::
 1. Select **+ New Step** in the designer, and do the following steps:
     1. Search for **Service Bus**.
     2. Select **Service Bus** in the list. 
     3. Select for **Get messages** in the **Actions** list. 
     4. Select **Get messages from a topic subscription (peek-lock)**. 
 
-        ![Logic Apps Designer - get messages action](./media/service-bus-to-event-grid-integration-example/service-bus-get-messages-step.png)
-    5. Enter a **name for the connection**. For example: **Get messages from the topic subscription**, and select the Service Bus namespace. 
-
-        ![Logic Apps Designer - select the Service Bus namespace](./media/service-bus-to-event-grid-integration-example/logic-apps-select-namespace.png) 
-    6. Select **RootManageSharedAccessKey**, and then select **Create**.
-
-        ![Logic Apps Designer - select the shared access key](./media/service-bus-to-event-grid-integration-example/logic-app-shared-access-key.png) 
+        :::image type="content" source="./media/service-bus-to-event-grid-integration-example/service-bus-get-messages-step.png" alt-text="Screenshot of showing the Logic Apps Designer with Get messages from a topic subscription selected.":::
+    5. Follow these steps:
+        1. Enter a **name for the connection**. For example: **Get messages from the topic subscription**. 
+        1. Confirm that **Authentication Type** is set to **Access Key**.
+        1. For **Connection String**, copy and paste the connection string to the Service Bus namespace that you saved earlier.
+        1. Select **Create**. 
+    
+            :::image type="content" source="./media/service-bus-to-event-grid-integration-example/logic-app-shared-access-key.png" alt-text="Screenshot of showing the Logic Apps Designer with the Service Bus connection string specified.":::
     8. Select your **topic** and **subscription**. 
 
-        ![Screenshot that shows where you select your topic and subscription.](./media/service-bus-to-event-grid-integration-example/logic-app-select-topic-subscription.png)
+
+        :::image type="content" source="./media/service-bus-to-event-grid-integration-example/logic-app-shared-access-key.png" alt-text="Screenshot of showing the Logic Apps Designer with the Service Bus topic and subscription specified.":::
 
 ### Add a step to process and complete received messages
 In this step, you'll add steps to send the received message in an email and then complete the message. In a real-world scenario, you'll process a message in the logic app before completing the message.