Merge branch 'MicrosoftDocs:main' into docs-editor/troubleshoot-resource-bridge-1695159450

Author: alt-key

.openpublishing.redirection.json

@@ -22362,6 +22362,11 @@
             "redirect_url": "/azure/communication-services/how-tos/calling-sdk/lobby",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/communication-services/tutorials/widgets/click-to-call-widget.md",
+            "redirect_url": "/azure/communication-services/tutorials/calling-widget/calling-widget-overview",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/load-balancer/tutorial-load-balancer-standard-manage-portal.md",
             "redirect_url": "/azure/load-balancer/quickstart-load-balancer-standard-public-portal",

articles/communication-services/tutorials/widgets/click-to-call-widget.md

@@ -295,7 +295,7 @@
               href: connect-spark-configuration.md
             - name: Connect using Databricks
               href: spark-databricks.md
-            - name: Connect using HDInsight
+            - name: Connect from Spark on YARN
               href: spark-hdinsight.md
             - name: Create keyspace and table
               href: spark-ddl-operations.md

articles/cosmos-db/cassandra/TOC.yml

@@ -2,15 +2,15 @@
 title: Azure Active Directory events
 description: This article describes Azure AD event types and provides event samples.
 ms.topic: conceptual
-ms.date: 06/09/2022
+ms.date: 09/19/2023
 ---
 
 # Azure Active Directory events
 
 This article provides the properties and schema for Azure Active Directory (Azure AD) events, which are published by Microsoft Graph API. For an introduction to event schemas, see [CloudEvents schema](cloud-event-schema.md). 
 
 ## Available event types
-These events are triggered when a [User](/graph/api/resources/user) or [Group](/graph/api/resources/group) is created, updated or deleted in Azure AD or by operating over those resources using Microsoft Graph API. 
+These events are triggered when a [User](/graph/api/resources/user) or [Group](/graph/api/resources/group) is created, updated, or deleted in Azure AD or by operating over those resources using Microsoft Graph API. 
 
  | Event name | Description |
  | ---------- | ----------- |
@@ -173,7 +173,7 @@ The data object has the following properties:
 | `@odata.id` | string | The Graph API resource identifier for which the event was raised. |
 | `id` | string | The resource identifier for which the event was raised. |
 | `organizationId` | string | The Azure AD tenant identifier.  |
-| `eventTime` | string | The time at which the resource state occurred. |
+| `eventTime` | string | The time when the resource state changed. |
 | `sequenceNumber` | string | A sequence number. |
 | `subscriptionExpirationDateTime` | string | The time in [RFC 3339](https://tools.ietf.org/html/rfc3339) format at which the Graph API subscription expires.  |
 | `subscriptionId` | string | The Graph API subscription identifier. |
@@ -186,4 +186,4 @@ The data object has the following properties:
 * For information on how to subscribe to Microsoft Graph API to receive Azure AD events, see [subscribe to Azure Graph API events](subscribe-to-graph-api-events.md).
 * For information about Azure Event Grid event handlers, see [event handlers](event-handlers.md).
 * For more information about creating an Azure Event Grid subscription, see [create event subscription](subscribe-through-portal.md#create-event-subscriptions) and [Event Grid subscription schema](subscription-creation-schema.md).
-* For information about how to configure an event subscription to select specific events to be delivered, consult [event filtering](event-filtering.md). You may also want to refer to [filter events](how-to-filter-events.md).
+* For information about how to configure an event subscription to select specific events to be delivered, see [event filtering](event-filtering.md). You may also want to refer to [filter events](how-to-filter-events.md).

articles/event-grid/azure-active-directory-events.md

@@ -2,13 +2,13 @@
 title: Azure Communication Services as an Event Grid source - Overview
 description: This article describes how to use Azure Communication Services as an Event Grid event source.
 ms.topic: conceptual
-ms.date: 06/11/2021
+ms.date: 09/19/2023
 ms.author: mikben
 ---
 
 # Event Handling in Azure Communication Services
 
-Azure Communication Services integrates with [Azure Event Grid](https://azure.microsoft.com/services/event-grid/) to deliver real-time event notifications in a reliable, scalable and secure manner. The purpose of this article is to help you configure your applications to listen to Communication Services events. For example, you may want to update a database, create a work item and deliver a push notification whenever an SMS message is received by a phone number associated with your Communication Services resource.
+Azure Communication Services integrates with [Azure Event Grid](https://azure.microsoft.com/services/event-grid/) to deliver real-time event notifications in a reliable, scalable, and secure manner. The purpose of this article is to help you configure your applications to listen to Communication Services events. For example, you may want to update a database, create a work item and deliver a push notification whenever an SMS message is received by a phone number associated with your Communication Services resource.
 
 Azure Event Grid is a fully managed event routing service, which uses a publish-subscribe model. Event Grid has built-in support for Azure services like [Azure Functions](../azure-functions/functions-overview.md) and [Azure Logic Apps](../azure-functions/functions-overview.md). It can deliver event alerts to non-Azure services using webhooks. For a complete list of the event handlers that Event Grid supports, see [An introduction to Azure Event Grid](overview.md).
 
@@ -34,7 +34,7 @@ You can use the Azure portal or Azure CLI to subscribe to events emitted by your
 
 ## Event subjects
 
-The `subject` field of all Communication Services events identifies the user, phone number or entity that is targeted by the event. Common prefixes are used to allow simple [Event Grid Filtering](event-filtering.md).
+The `subject` field of all Communication Services events identifies the user, phone number, or entity that is targeted by the event. Common prefixes are used to allow simple [Event Grid filtering](event-filtering.md).
 
 | Subject Prefix                              | Communication Service Entity |
 | ------------------------------------------- | ---------------------------- |

articles/event-grid/event-schema-communication-services.md

@@ -2,7 +2,7 @@
 title: Event hub as an event handler for Azure Event Grid events
 description: Describes how you can use event hubs as event handlers for Azure Event Grid events.
 ms.topic: conceptual
-ms.date: 09/30/2021
+ms.date: 09/19/2023
 ---
 
 # Event hub as an event handler for Azure Event Grid events
@@ -69,7 +69,7 @@ See the following examples:
 ```
 
 ## Delivery properties
-Event subscriptions allow you to set up HTTP headers that are included in delivered events. This capability allows you to set custom headers that are required by a destination. You can set custom headers on the events that are delivered to Azure Event Hubs.
+Event subscriptions allow you to set up HTTP headers that are included in delivered events. This capability allows you to set custom headers that the destination requires. You can set custom headers on the events that are delivered to Azure Event Hubs.
 
 If you need to publish events to a specific partition within an event hub, set the `PartitionKey` property on your event subscription to specify the partition key that identifies the target event hub partition.