locked
Registration expiry date RRS feed

  • Question

  • Just had a conversation on twitter with @azuresupport, and they recommended to check here to make sure:

    Questtion: Hi! I noticed that my newly created notification hub has no expiry on registrations. How do I enable that for my other hubs?

    Answer: This documentation might help you find out: ^FL

    Question: So can I assume that the expiry dat is not used anymore?Cause if I compare my old (top) and new(bottom) hub the dates differ. New hub has date 9999, and old hub has 2017 for new registrations.


    Answer: It seems so, but to be sure please create a thread. That way our engineers can check if it's correct.

    Question: So since new registrations on the old hub have a nearby expiry date, can I assume that the expiry date is ignored?

    Thursday, October 13, 2016 2:04 PM

All replies

  • You don't have to set an expiry, per what we updated: https://azure.microsoft.com/en-us/blog/push-notification-hub-telemetry-expiry-update/. That will default the TTL to infinity. But if needed for your scenario, you can set the time to live (TTL) at the notification hub level: https://msdn.microsoft.com/en-us/library/azure/dn223269.aspx. 
    • Proposed as answer by Mimi Xu Thursday, November 3, 2016 6:16 PM
    Thursday, October 13, 2016 3:39 PM
  • Thanks for the extensive answer. If I understand correctly, I don't need to update my existing notification hub to TTL infinity?
    Tuesday, October 18, 2016 9:02 AM
  • Bump
    Tuesday, October 25, 2016 7:47 AM
  • Hi, please see https://azure.microsoft.com/en-us/blog/push-notification-hub-telemetry-expiry-update/. The document notes that you DO need to update existing ones if you want infinite expiry and tells you how to do so.
    Thursday, November 3, 2016 6:16 PM