Initial refresh of article

dksimpson · dksimpson · commit f289a0233ee6 · 2024-06-24T21:19:01.000-07:00
diff --git a/articles/azure-functions/functions-bindings-notification-hubs.md b/articles/azure-functions/functions-bindings-notification-hubs.md
@@ -1,39 +1,40 @@
 ---
-title: Notification Hubs bindings for Azure Functions
-description: Understand how to use Azure Notification Hub binding in Azure Functions.
+title: Azure Notification Hubs output bindings for Azure Functions
+description: Learn how to use Azure Notification Hub output bindings in Azure Functions.
+ms.service: azure-functions
 ms.topic: reference
 ms.devlang: csharp
+ms.date: 06/24/2024
 # ms.devlang: csharp, fsharp, javascript
 ms.custom: devx-track-csharp
-ms.date: 11/21/2017
 ---
 
-# Notification Hubs output binding for Azure Functions
+# Azure Notification Hubs output bindings for Azure Functions
 
 This article explains how to send push notifications by using [Azure Notification Hubs](../notification-hubs/notification-hubs-push-notification-overview.md) bindings in Azure Functions. Azure Functions supports output bindings for Notification Hubs.
 
-Azure Notification Hubs must be configured for the Platform Notifications Service (PNS) you want to use. To learn how to get push notifications in your client app from Notification Hubs, see [Getting started with Notification Hubs](../notification-hubs/notification-hubs-windows-store-dotnet-get-started-wns-push-notification.md) and select your target client platform from the drop-down list near the top of the page.
+You must configure Notification Hubs for the Platform Notifications Service (PNS) you want to use. For more information about how to get push notifications in your client app from Notification Hubs, see [Quickstart: Set up push notifications in a notification hub](../notification-hubs/configure-notification-hub-portal-pns-settings.md).
 
 > [!IMPORTANT]
-> Google has [deprecated Google Cloud Messaging (GCM) in favor of Firebase Cloud Messaging (FCM)](https://developers.google.com/cloud-messaging/faq). This output binding doesn't support FCM. To send notifications using FCM, use the [Firebase API](https://firebase.google.com/docs/cloud-messaging/server#choosing-a-server-option) directly in your function or use [template notifications](../notification-hubs/notification-hubs-templates-cross-platform-push-messages.md).
+> Google has [deprecated Google Cloud Messaging (GCM) in favor of Firebase Cloud Messaging (FCM)](https://developers.google.com/cloud-messaging/faq). However, output bindings for Notification Hubs doesn't support FCM. To send notifications using FCM, use the [Firebase API](https://firebase.google.com/docs/cloud-messaging/server#choosing-a-server-option) directly in your function or use [template notifications](../notification-hubs/notification-hubs-templates-cross-platform-push-messages.md).
 
-## Packages - Functions 1.x
+## Packages: Functions 1.x
 
 [!INCLUDE [functions-runtime-1x-retirement-note](../../includes/functions-runtime-1x-retirement-note.md)]
 
 The Notification Hubs bindings are provided in the [Microsoft.Azure.WebJobs.Extensions.NotificationHubs](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.NotificationHubs) NuGet package, version 1.x. Source code for the package is in the [azure-webjobs-sdk-extensions](https://github.com/Azure/azure-webjobs-sdk-extensions/tree/v2.x/src/WebJobs.Extensions.NotificationHubs) GitHub repository.
 
 [!INCLUDE [functions-package](../../includes/functions-package.md)]
 
-## Packages - Functions 2.x and higher
+## Packages: Functions 2.x and higher
 
-This binding is not available in Functions 2.x and higher.
+Output binding isn't available in Functions 2.x and higher.
 
-## Example - template
+## Example: template
 
-The notifications you send can be native notifications or [template notifications](../notification-hubs/notification-hubs-templates-cross-platform-push-messages.md). Native notifications target a specific client platform as configured in the `platform` property of the output binding. A template notification can be used to target multiple platforms.   
+The notifications you send can be native notifications or [template notifications](../notification-hubs/notification-hubs-templates-cross-platform-push-messages.md). A native notification targets a specific client platform, as configured in the `platform` property of the output binding. A template notification can be used to target multiple platforms.
 
-See the language-specific example:
+Template examples for each language:
 
 * [C# script - out parameter](#c-script-template-example---out-parameter)
 * [C# script - asynchronous](#c-script-template-example---asynchronous)
@@ -42,7 +43,7 @@ See the language-specific example:
 * [F#](#f-template-example)
 * [JavaScript](#javascript-template-example)
 
-### C# script template example - out parameter
+### C# script template example: out parameter
 
 This example sends a notification for a [template registration](../notification-hubs/notification-hubs-templates-cross-platform-push-messages.md) that contains a `message` placeholder in the template.
 
@@ -65,9 +66,9 @@ private static IDictionary<string, string> GetTemplateProperties(string message)
 }
 ```
 
-### C# script template example - asynchronous
+### C# script template example: asynchronous
 
-If you are using asynchronous code, out parameters are not allowed. In this case use `IAsyncCollector` to return your template notification. The following code is an asynchronous example of the code above. 
+If you're using asynchronous code, out parameters aren't allowed. In this case, use `IAsyncCollector` to return your template notification. The following code is an asynchronous example of the previous example.
 
 ```cs
 using System;
@@ -90,7 +91,7 @@ private static IDictionary<string, string> GetTemplateProperties(string message)
 }
 ```
 
-### C# script template example - JSON
+### C# script template example: JSON
 
 This example sends a notification for a [template registration](../notification-hubs/notification-hubs-templates-cross-platform-push-messages.md) that contains a `message` placeholder in the template using a valid JSON string.
 
@@ -104,9 +105,9 @@ public static void Run(string myQueueItem,  out string notification, TraceWriter
 }
 ```
 
-### C# script template example - library types
+### C# script template example: library types
 
-This example shows how to use types defined in the [Microsoft Azure Notification Hubs Library](https://www.nuget.org/packages/Microsoft.Azure.NotificationHubs/). 
+This example shows how to use types defined in the [Microsoft Azure Notification Hubs Library](https://www.nuget.org/packages/Microsoft.Azure.NotificationHubs/).
 
 ```cs
 #r "Microsoft.Azure.NotificationHubs"
@@ -158,9 +159,9 @@ module.exports = async function (context, myTimer) {
 };
 ```
 
-## Example - APNS native
+## Example: APNS native
 
-This C# script example shows how to send a native APNS notification. 
+This C# script example shows how to send a native Apple Push Notification Service (APNS) notification:
 
 ```cs
 #r "Microsoft.Azure.NotificationHubs"
@@ -177,7 +178,7 @@ public static async Task Run(string myQueueItem, IAsyncCollector<Notification> n
     // In this example the queue item is a new user to be processed in the form of a JSON string with 
     // a "name" value.
     //
-    // The JSON format for a native APNS notification is ...
+    // The JSON format for a native Apple Push Notification Service (APNS) notification is:
     // { "aps": { "alert": "notification message" }}  
 
     log.LogInformation($"Sending APNS notification of a new user");    
@@ -189,9 +190,9 @@ public static async Task Run(string myQueueItem, IAsyncCollector<Notification> n
 }
 ```
 
-## Example - WNS native
+## Example: WNS native
 
-This C# script example shows how to use types defined in the [Microsoft Azure Notification Hubs Library](https://www.nuget.org/packages/Microsoft.Azure.NotificationHubs/) to send a native WNS toast notification. 
+This C# script example shows how to use types defined in the [Microsoft Azure Notification Hubs Library](https://www.nuget.org/packages/Microsoft.Azure.NotificationHubs/) to send a native Windows Push Notification Service (WNS) toast notification:
 
 ```cs
 #r "Microsoft.Azure.NotificationHubs"
@@ -236,21 +237,21 @@ public static async Task Run(string myQueueItem, IAsyncCollector<Notification> n
 
 In [C# class libraries](functions-dotnet-class-library.md), use the [NotificationHub](https://github.com/Azure/azure-webjobs-sdk-extensions/blob/v2.x/src/WebJobs.Extensions.NotificationHubs/NotificationHubAttribute.cs) attribute.
 
-The attribute's constructor parameters and properties are described in the [configuration](#configuration) section.
+The attribute's constructor parameters and properties are described in the [Configuration](#configuration) section.
 
 ## Configuration
 
-The following table explains the binding configuration properties that you set in the *function.json* file and the `NotificationHub` attribute:
+The following table lists the binding configuration properties that you set in the *function.json* file and the `NotificationHub` attribute:
 
 |function.json property | Attribute property |Description|
 |---------|---------|----------------------|
-|**type** |n/a| Must be set to `notificationHub`. |
-|**direction** |n/a| Must be set to `out`. | 
+|**type** |n/a| Set to `notificationHub`. |
+|**direction** |n/a| Set to `out`. |
 |**name** |n/a| Variable name used in function code for the notification hub message. |
-|**tagExpression** |**TagExpression** | Tag expressions allow you to specify that notifications be delivered to a set of devices that have registered to receive notifications that match the tag expression.  For more information, see [Routing and tag expressions](../notification-hubs/notification-hubs-tags-segment-push-message.md). |
-|**hubName** | **HubName** | Name of the notification hub resource in the Azure portal. |
-|**connection** | **ConnectionStringSetting** | The name of an app setting that contains a Notification Hubs connection string.  The connection string must be set to the *DefaultFullSharedAccessSignature* value for your notification hub. See [Connection string setup](#connection-string-setup) later in this article.|
-|**platform** | **Platform** | The platform property indicates the client platform your notification targets. By default, if the platform property is omitted from the output binding, template notifications can be used to target any platform configured on the Azure Notification Hub. For more information on using templates in general to send cross platform notifications with an Azure Notification Hub, see [Templates](../notification-hubs/notification-hubs-templates-cross-platform-push-messages.md). When set, **platform** must be one of the following values: <ul><li><code>apns</code>&mdash;Apple Push Notification Service. For more information on configuring the notification hub for APNS and receiving the notification in a client app, see [Sending push notifications to iOS with Azure Notification Hubs](../notification-hubs/xamarin-notification-hubs-ios-push-notification-apns-get-started.md).</li><li><code>adm</code>&mdash;[Amazon Device Messaging](https://developer.amazon.com/device-messaging). For more information on configuring the notification hub for ADM and receiving the notification in a Kindle app, see [Getting Started with Notification Hubs for Kindle apps](../notification-hubs/notification-hubs-android-push-notification-google-fcm-get-started.md).</li><li><code>wns</code>&mdash;[Windows Push Notification Services](/windows/uwp/design/shell/tiles-and-notifications/windows-push-notification-services--wns--overview) targeting Windows platforms. Windows Phone 8.1 and later is also supported by WNS. For more information, see [Getting started with Notification Hubs for Windows Universal Platform Apps](../notification-hubs/notification-hubs-windows-store-dotnet-get-started-wns-push-notification.md).</li><li><code>mpns</code>&mdash;[Microsoft Push Notification Service](/previous-versions/windows/apps/ff402558(v=vs.105)). This platform supports Windows Phone 8 and earlier Windows Phone platforms. For more information, see [Sending push notifications with Azure Notification Hubs on Windows Phone](../notification-hubs/notification-hubs-windows-mobile-push-notifications-mpns.md).</li></ul> |
+|**tagExpression** |**TagExpression** | Tag expressions allow you to specify that notifications be delivered to a set of devices that are registered to receive notifications matching the tag expression. For more information, see [Routing and tag expressions](../notification-hubs/notification-hubs-tags-segment-push-message.md). |
+|**hubName** | **HubName** | The name of the notification hub resource in the Azure portal. |
+|**connection** | **ConnectionStringSetting** | The name of an app setting that contains a Notification Hubs connection string. Set the connection string to the *DefaultFullSharedAccessSignature* value for your notification hub. For more information, see [Connection string setup](#connection-string-setup). |
+|**platform** | **Platform** | The platform property indicates the client platform your notification targets. By default, if the platform property is omitted from the output binding, template notifications can be used to target any platform configured on the Azure Notification Hub. For more information about using templates to send cross-platform notifications with an Azure Notification Hub, see [Templates](../notification-hubs/notification-hubs-templates-cross-platform-push-messages.md). When **platform** is set, it must be one of the following values: <ul><li><code>apns</code>: Apple Push Notification Service. For more information on configuring the notification hub for APNS and receiving the notification in a client app, see [Send push notifications to iOS with Azure Notification Hubs](../notification-hubs/xamarin-notification-hubs-ios-push-notification-apns-get-started.md).</li><li><code>adm</code>: [Amazon Device Messaging](https://developer.amazon.com/device-messaging). For more information on configuring the notification hub for Azure Deployment Manager (ADM) and receiving the notification in a Kindle app, see [Send push notifications to Android devices using Firebase SDK](../notification-hubs/notification-hubs-android-push-notification-google-fcm-get-started.md).</li><li><code>wns</code>: [Windows Push Notification Services](/windows/uwp/design/shell/tiles-and-notifications/windows-push-notification-services--wns--overview) targeting Windows platforms. WNS also supports Windows Phone 8.1 and later. For more information, see [Send notifications to Universal Windows Platform apps using Azure Notification Hubs](../notification-hubs/notification-hubs-windows-store-dotnet-get-started-wns-push-notification.md).</li><li><code>mpns</code>: [Microsoft Push Notification Service](/previous-versions/windows/apps/ff402558(v=vs.105)). This platform supports Windows Phone 8 and earlier Windows Phone platforms. For more information, see [Send notifications to Universal Windows Platform apps using Azure Notification Hubs](../notification-hubs/notification-hubs-windows-mobile-push-notifications-mpns.md).</li></ul> |
 
 [!INCLUDE [app settings to local.settings.json](../../includes/functions-app-settings-local.md)]
 
@@ -277,15 +278,20 @@ Here's an example of a Notification Hubs binding in a *function.json* file.
 
 ### Connection string setup
 
-To use a notification hub output binding, you must configure the connection string for the hub. You can select an existing notification hub or create a new one right from the *Integrate* tab in the Azure portal. You can also configure the connection string manually. 
+To use a notification hub output binding, you must configure the connection string for the hub. You can select an existing notification hub or create a new one right from the **Integrate** tab in the Azure portal. You can also configure the connection string manually.
 
 To configure the connection string to an existing notification hub:
 
-1. Navigate to your notification hub in the [Azure portal](https://portal.azure.com), choose **Access policies**, and select the copy button next to the **DefaultFullSharedAccessSignature** policy. This copies the connection string for the *DefaultFullSharedAccessSignature* policy to your notification hub. This connection string lets your function send notification messages to the hub.
-    ![Copy the notification hub connection string](./media/functions-bindings-notification-hubs/get-notification-hub-connection.png)
-1. Navigate to your function app in the Azure portal, choose **Application settings**, add a key such as **MyHubConnectionString**, paste the copied *DefaultFullSharedAccessSignature*  for your notification hub as the value, and then click **Save**.
+1. Navigate to your notification hub in the [Azure portal](https://portal.azure.com), choose **Access policies**, and select the copy button next to the **DefaultFullSharedAccessSignature** policy.
 
-The name of this application setting is what goes in the output binding connection setting in *function.json* or the .NET attribute. See the [Configuration section](#configuration) earlier in this article.
+   The connection string for the *DefaultFullSharedAccessSignature* policy is copied to your notification hub. This connection string lets your function send notification messages to the hub.
+    ![Screenshot that shows how to copy the notification hub connection string.](./media/functions-bindings-notification-hubs/get-notification-hub-connection.png)
+
+1. Navigate to your function app in the Azure portal, expand **Settings**, and then select **Environment variables**.
+
+1. From the **App setting** tab, select **+ Add** to add a key such as **MyHubConnectionString**. The name of this app setting is the output binding connection setting in *function.json* or the .NET attribute. For more information, see [Configuration](#configuration).
+
+1. For the value, paste the copied *DefaultFullSharedAccessSignature* connection string from your notification hub, and then select **Apply**.
 
 [!INCLUDE [app settings to local.settings.json](../../includes/functions-app-settings-local.md)]
 
@@ -295,7 +301,6 @@ The name of this application setting is what goes in the output binding connecti
 |---|---|
 | Notification Hub | [Operations Guide](/rest/api/notificationhubs/) |
 
-## Next steps
+## Related content
 
-> [!div class="nextstepaction"]
-> [Learn more about Azure functions triggers and bindings](functions-triggers-bindings.md)
+* [Azure Functions triggers and bindings concepts](functions-triggers-bindings.md)
diff --git a/includes/functions-package.md b/includes/functions-package.md
@@ -2,15 +2,15 @@
 author: ggailey777
 ms.service: azure-functions
 ms.topic: include
-ms.date: 03/20/2022
+ms.date: 06/24/2024
 ms.author: glenga
 ms.custom: include file
 ---
 
-The following table tells how to add support for this binding in each development environment.
+The following table lists how to add support for output binding in each development environment.
 
-| Development environment               | To add support in <br>Functions 1.x  |
-|----------------------|----------------|
-|Local development - C# class library       | [Install the package](../articles/azure-functions/functions-develop-vs.md#add-bindings) | 
-|Local development - C# script, JavaScript, F# |Automatic         |
-|Portal development|  Automatic    |
+| Development environment | To add support in Functions 1.x |
+|-------------------------|----------------------------------|
+| Local development: C# class library | [Install the package](../articles/azure-functions/functions-develop-vs.md#add-bindings) |
+| Local development: C# script, JavaScript, F# | Automatic |
+| Portal development | Automatic |
