Skip to content

Commit c01c750

Browse files
committed
clarying who expired the handle
1 parent 97a4ce9 commit c01c750

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/notification-hubs/notification-hubs-push-notification-registration-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ An installation can contain the following properties. For a complete listing of
8686
8787
Registrations and installations must contain a valid PNS handle for each device/channel. Because PNS handles can only be obtained in a client app on the device, one pattern is to register directly on that device with the client app. On the other hand, security considerations and business logic related to tags might require you to manage device registration in the app back-end.
8888

89-
When the push is made to an expired handle, Azure Notification Hubs automatically cleans the associated installation/registration record based on the response received from the PNS server. To clean expired records from a secondary notification hub, add custom logic that processes feedback from each send. Then, expire installation/registration in the secondary notification hub.
89+
When the push is made to a handle that has been expired by the PNS, Azure Notification Hubs automatically cleans the associated installation/registration record based on the response received from the PNS server. To clean expired records from a secondary notification hub, add custom logic that processes feedback from each send. Then, expire installation/registration in the secondary notification hub.
9090

9191
> [!NOTE]
9292
> The Installations API does not support the Baidu service (although the Registrations API does).

0 commit comments

Comments
 (0)