CreateOrUpdateInstallation metric count increasing when sending to an installation id

Question

This way of sending notifications seems to be burning through our 10m (Standard tier) quota for registrations. What is the reason for this as this seems very odd.

Answer 1

When sending notifications to an installation ID using Azure Notification Hubs, the CreateOrUpdateInstallation metric count may increase due to the way installations are managed. Each time a notification is sent to a specific installation ID, it may trigger an update to the installation object, especially if any properties of the installation are modified or if the notification is sent with different tags or templates. This behavior can lead to an increase in the registration count, as each update could be treated as a new registration depending on the changes made.

To manage this effectively and avoid hitting the quota limit, ensure that you are not unnecessarily updating the installation object with every notification. Consider using the partial update capability to modify only specific properties of the installation when necessary, which can help reduce the number of updates and, consequently, the metric count.

Additionally, it's important to monitor your usage and understand the limits associated with the Standard tier, as exceeding the quota can lead to issues with sending notifications.

---

References:

• How to use Notification Hubs from Java
• Registration management