Skip to content

Commit 3cceed6

Browse files
committed
Revert "Update link."
This reverts commit 0f85e3c.
1 parent 0f85e3c commit 3cceed6

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/azure-functions/functions-bindings-notification-hubs.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -175,15 +175,15 @@ public static async Task Run(string myQueueItem, IAsyncCollector<Notification> n
175175
{
176176
log.Info($"C# Queue trigger function processed: {myQueueItem}");
177177

178-
// In this example, the queue item is a new user to be processed in the form of a JSON string with
178+
// In this example, the queue item is a new user to be processed in the form of a JSON string with
179179
// a "name" value.
180180
//
181181
// The JSON format for a native Apple Push Notification Service (APNS) notification is:
182182
// { "aps": { "alert": "notification message" }}
183183
184184
log.LogInformation($"Sending APNS notification of a new user");
185185
dynamic user = JsonConvert.DeserializeObject(myQueueItem);
186-
string apnsNotificationPayload = "{\"aps\": {\"alert\": \"A new user wants to be added (" +
186+
string apnsNotificationPayload = "{\"aps\": {\"alert\": \"A new user wants to be added (" +
187187
user.name + ")\" }}";
188188
log.LogInformation($"{apnsNotificationPayload}");
189189
await notification.AddAsync(new AppleNotification(apnsNotificationPayload));
@@ -206,7 +206,7 @@ public static async Task Run(string myQueueItem, IAsyncCollector<Notification> n
206206
{
207207
log.Info($"C# Queue trigger function processed: {myQueueItem}");
208208

209-
// In this example, the queue item is a new user to be processed in the form of a JSON string with
209+
// In this example, the queue item is a new user to be processed in the form of a JSON string with
210210
// a "name" value.
211211
//
212212
// The XML format for a native WNS toast notification is ...
@@ -223,8 +223,8 @@ public static async Task Run(string myQueueItem, IAsyncCollector<Notification> n
223223
dynamic user = JsonConvert.DeserializeObject(myQueueItem);
224224
string wnsNotificationPayload = "<?xml version=\"1.0\" encoding=\"utf-8\"?>" +
225225
"<toast><visual><binding template=\"ToastText01\">" +
226-
"<text id=\"1\">" +
227-
"A new user wants to be added (" + user.name + ")" +
226+
"<text id=\"1\">" +
227+
"A new user wants to be added (" + user.name + ")" +
228228
"</text>" +
229229
"</binding></visual></toast>";
230230

@@ -251,7 +251,7 @@ The following table lists the binding configuration properties that you set in t
251251
|**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). |
252252
|**hubName** | **HubName** | The name of the notification hub resource in the Azure portal. |
253253
|**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). |
254-
|**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 [Notification Hubs 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 .NET MAUI apps using Azure Notification Hubs via a backend service](/dotnet/maui/data-cloud/push-notifications).</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> |
254+
|**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 [Notification Hubs 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> |
255255

256256
[!INCLUDE [app settings to local.settings.json](../../includes/functions-app-settings-local.md)]
257257

@@ -278,10 +278,10 @@ Here's an example of a Notification Hubs binding in a *function.json* file:
278278

279279
### Connection string setup
280280

281-
To use a notification hub output binding, you must configure the connection string for the hub.
281+
To use a notification hub output binding, you must configure the connection string for the hub.
282282

283283
> [!IMPORTANT]
284-
> The Notification Hubs binding doesn't support Microsoft Entra authentication and managed identities. You can use Azure Key Vault to centrally manage your notification hub connection string and help with key rotation. To learn more, see [Manage Connections](./manage-connections.md).
284+
> The Notification Hubs binding doesn't support Microsoft Entra authentication and managed identities. You can use Azure Key Vault to centrally manage your notification hub connection string and help with key rotation. To learn more, see [Manage Connections](./manage-connections.md).
285285
286286
You can select an existing notification hub or create a new one from the **Integrate** tab in the Azure portal. You can also configure the connection string manually.
287287

0 commit comments

Comments
 (0)