Notifications restore to TOC and refresh

Author: vac0224

articles/communication-services/concepts/notifications.md

@@ -1,25 +1,25 @@
 ---
-title: Notifications in Azure Communication Services
-titleSuffix: An Azure Communication Services concept document
-description: Send notifications to users of apps built on Azure Communication Services.
+title: Push notifications overview
+titleSuffix: An Azure Communication Services article
+description: This article describes how to send notifications to users of apps built on Azure Communication Services.
 author: tophpalmer
 manager: chpalm
 services: azure-communication-services
 
 ms.author: chpalm
-ms.date: 06/30/2021
+ms.date: 06/27/2025
 ms.topic: conceptual
 ms.service: azure-communication-services
 ---
-# Communication Services notifications
+# Push notifications overview
 
-The Azure Communication Services chat and calling SDKs create a real-time messaging channel that allows signaling messages to be pushed to connected clients in an efficient, reliable manner. This enables you to build rich, real-time communication functionality into your applications without the need to implement complicated HTTP polling logic. However, on mobile applications, this signaling channel only remains connected when your application is active in the foreground. If you want your users to receive incoming calls or chat messages while your application is in the background, you should use push notifications.
+The Azure Communication Services Chat SDK and Calling SDK create a real-time messaging channel that enables signaling messages to be pushed to connected clients in an efficient, reliable manner. This ability enables you to build rich, real-time communication functionality into your applications without the need to implement complicated HTTP polling logic. However, on mobile applications, this signaling channel only remains connected when your application is active in the foreground. If you want your users to receive incoming calls or chat messages while your application is in the background, you should use push notifications.
 
-Push notifications allow you to send information from your application to users' mobile devices. You can use push notifications to show a dialog, play a sound, or display incoming call UI. Azure Communication Services provides integrations with [Azure Event Grid](../../event-grid/overview.md) and [Azure Notification Hubs](../../notification-hubs/notification-hubs-push-notification-overview.md) that enable you to add push notifications to your apps.
+Push notifications enable you to send information from your application to users' mobile devices. You can use push notifications to show a dialog, play a sound, or display incoming call UI. Azure Communication Services provides integrations with [Azure Event Grid](../../event-grid/overview.md) and [Azure Notification Hubs](../../notification-hubs/notification-hubs-push-notification-overview.md) that enable you to add push notifications to your apps.
 
 ## Trigger push notifications via Azure Event Grid
 
-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. You can leverage this integration to create a notification service that delivers mobile push notifications to your users by creating an event grid subscription that triggers an [Azure Function](../../azure-functions/functions-overview.md) or webhook.
+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. You can use this integration to create a notification service that delivers mobile push notifications to your users by creating an Event Grid subscription that triggers an [Azure Function](../../azure-functions/functions-overview.md) or webhook.
 
 :::image type="content" source="./media/notifications/acs-events-int.png" alt-text="Diagram showing how Communication Services integrates with Event Grid.":::
 
@@ -28,13 +28,13 @@ Learn more about [event handling in Azure Communication Services](../../event-gr
 ## Deliver push notifications via Azure Notification Hubs
 
 > [!IMPORTANT]
-> Azure Notification Hubs has announced that Firebase Cloud Messaging (FCM) legacy API will be deprecated in July 2024. This will affect all Azure Communication Services Calling and Chat applications who send Android push notifications. Customers impacted will need to migrate their registrations from FCM legacy to FCM v1, and can start doing so in March 2024. For more information including migration steps, please see [Notification Hub documentation](../../notification-hubs/notification-hubs-gcm-to-fcm.md).
+> Azure Notification Hubs announced that Firebase Cloud Messaging (FCM) legacy API was deprecated in July 2024. This affects all Azure Communication Services Calling and Chat applications who send Android push notifications. Customers impacted need to migrate their registrations from FCM legacy to FCM v1, and can start doing so in March 2024. For more information including migration steps, see [Notification Hub documentation](../../notification-hubs/notification-hubs-gcm-to-fcm.md).
 
 You can connect an Azure Notification Hub to your Communication Services resource in order to automatically send push notifications to a user's mobile device when they receive an incoming call or to notify them about missed chat activity. You should use these push notifications to wake up your application from the background and display UI that lets the user accept or decline the call or read the newly received chat message. 
 
 :::image type="content" source="./media/notifications/acs-anh-int.png" alt-text="Diagram showing how communication services integrates with Azure Notification Hubs.":::
 
-Communication Services uses Azure Notification Hub as a pass-through service to communicate with the various platform-specific push notification services using the [Direct Send](/rest/api/notificationhubs/direct-send) API. This allows you to reuse your existing Azure Notification Hub resources and configurations to deliver low latency, reliable notifications to your applications.
+Communication Services uses Azure Notification Hub as a pass-through service to communicate with the various platform-specific push notification services using the [Direct Send](/rest/api/notificationhubs/direct-send) API. This feature enables you to reuse your existing Azure Notification Hub resources and configurations to deliver low latency, reliable notifications to your applications.
 
 > [!NOTE]
 > Currently calling and chat push notifications are supported for both Android and iOS.
@@ -45,6 +45,7 @@ To deliver push notifications to client devices using Notification Hubs, [create
 
 > [!NOTE]
 > Currently the APNs and FCM platforms are supported.
+
 The APNs platform needs to be configured with token authentication mode. Certificate authentication mode isn't supported as of now.
 
 Once your Notification hub is configured, you can associate it to your Communication Services resource by supplying a connection string for the hub using the Azure Resource Manager Client or through the Azure portal. The connection string should contain `Send` permissions. We recommend creating another access policy with `Send` only permissions specifically for your hub. Learn more about [Notification Hubs security and access policies](../../notification-hubs/notification-hubs-push-notification-security.md)
@@ -69,15 +70,15 @@ armclient POST /subscriptions/<sub_id>/resourceGroups/<resource_group>/providers
 
 1. Inside the Communication Services resource, select **Push Notifications** from the left menu of the Communication Services page, and connect the Notification Hub that you provisioned earlier.
 
-1. Select **Connect notification hub**. You'll see a list of notification hubs available to connect.
+1. Select **Connect notification hub**. You see a list of notification hubs available to connect.
 
 1. Select the notification hub that you'd like to use for this resource.
 
    - If you need to create a new hub, select **Create new notification hub** to get a new hub provisioned for this resource.
 
    :::image type="content" source="./media/notifications/acs-anh-portal-int.png" alt-text="Screenshot showing the Push Notifications settings within the Azure portal.":::
 
-Now you'll see the notification hub that you linked with the connected state.
+Now you see the notification hub that you linked with the connected state.
 
 If you'd like to use a different hub for the resource, select **Disconnect**, and then repeat the steps to link the different notification hub.
 
@@ -90,13 +91,13 @@ Refer to the [voice calling quickstart](../quickstarts/voice-video-calling/getti
 
 ### Troubleshooting guide for push notifications
 
-When you don't see push notifications on your device, there are three places where the notifications could have been dropped:
+When you don't see push notifications on your device, there are three places where the notifications might be dropped:
 
 - Azure Notification Hubs didn't accept the notification from Azure Communication Services
 - The Platform Notification System (for example APNs and FCM) didn't accept the notification from Azure Notification Hubs
 - The Platform Notification System didn't deliver the notification to the device.
 
-The first place where a notification can be dropped (Azure Notification Hubs didn't accept the notifications from Azure Communication Services) is covered below. For the other two places, see [Diagnose dropped notifications in Azure Notification Hubs](../../notification-hubs/notification-hubs-push-notification-fixer.md).
+The first place where a notification can be dropped (Azure Notification Hubs didn't accept the notifications from Azure Communication Services) is covered in the following description. For more information, see [Diagnose dropped notifications in Azure Notification Hubs](../../notification-hubs/notification-hubs-push-notification-fixer.md).
 
 One way to see if your Communication Services resource sends notifications to Azure Notification Hubs is by looking at the `incoming messages` metric from the linked [Azure Notification Hub metrics](/azure/azure-monitor/essentials/metrics-supported#microsoftnotificationhubsnamespacesnotificationhubs).
 
@@ -116,21 +117,21 @@ The Azure Notification Hub linked to your Communication Services resource doesn'
 
 #### The Azure Notification Hub APNs platform is configured with certificate authentication mode
 
-In case you want to use the APNs platform with certificate authentication mode, it is not currently supported. You should configure the APNs platform with token authentication mode as specified in [Set up push notifications in a notification hub](../../notification-hubs/configure-notification-hub-portal-pns-settings.md).
+In case you want to use the APNs platform with certificate authentication mode, it isn't currently supported. You should configure the APNs platform with token authentication mode as specified in [Set up push notifications in a notification hub](../../notification-hubs/configure-notification-hub-portal-pns-settings.md).
 
 #### The linked connection string doesn't have `Send` permission
 
-The connection string that you used to link your Notification Hub to your Communication Services resource needs to have the `Send` permission. For more details about how you can create a new connection string or see the current connection string from your Azure Notification Hub you can take a look in [Notification Hubs security and access policies](../../notification-hubs/notification-hubs-push-notification-security.md)
+The connection string that you used to link your Notification Hub to your Communication Services resource needs to have the `Send` permission. For more details about how you can create a new connection string or see the current connection string from your Azure Notification Hub, see [Notification Hubs security and access policies](../../notification-hubs/notification-hubs-push-notification-security.md)
 
 #### The linked connection string or Azure Notification Hub resourceId aren't valid
 
 Make sure that you configure Communication Services resource with the correct connection string and Azure Notification Hub resourceId
 
 #### The linked connection string is regenerated
 
-In case that you regenerated the connection string of your linked Azure Notification Hub, you have to update the connection string with the new one in your Communication Services resource by [relinking the Notification Hub](#notification-hub-provisioning).
+If you regenerated the connection string of your linked Azure Notification Hub, you need to update the connection string with the new one in your Communication Services resource by [relinking the Notification Hub](#notification-hub-provisioning).
 
 ## Next steps
 
-* For an introduction to Azure Event Grid, see [What is Event Grid?](../../event-grid/overview.md)
-* To learn more on the Azure Notification Hub concepts, see [Azure Notification Hubs documentation](../../notification-hubs/index.yml)
+* For an introduction to Azure Event Grid, see [What is Event Grid?](../../event-grid/overview.md).
+* To learn more on the Azure Notification Hub concepts, see [Azure Notification Hubs documentation](../../notification-hubs/index.yml).

articles/communication-services/toc.yml

@@ -88,6 +88,8 @@ items:
     href: concepts/chat/concepts.md#real-time-notifications
   - name: Push notifications
     href: concepts/chat/concepts.md#push-notifications
+  - name: Push notifications overview
+    href: concepts/notifications.md
   - name: Archive chats
     href: how-tos/chat-sdk/archive-chat-threads.md
   - name: Government clouds
@@ -446,6 +448,8 @@ items:
     items:
     - name: Voice and video terminology
       href: concepts/voice-video-calling/about-call-types.md
+    - name: Push notifications overview
+      href: concepts/notifications.md
     - name: Connect to a call
       items:
       - name: Create an access token