The current version of the Azure Monitor integration works best when the period and the timegrain are aligned (PT5M with a 300s period). That's why most Azure metrics integrations try to keep one timegrain when possible [1].
However, some integrations have multiple timegrains (PT1M and PT5M). When timegrains < period, the metricset may collecte values less frequently. Instead, when timegrains > period, the metricset may collect the same value more than once.
To avoid these problems, users can set up the generic Azure Monitor integration to use aligned timegrain and period, like AWS integration does.
We are also working on an enhanced version of Azure Metrics that avoids collecting metrics more than once for the timegrains > period. This change will probably ship on 8.12.
With the updated Azure Monitor, users can collect metrics without duplicates on integrations with PT1M, PT5M, and PT1H timegrains by setting the period to 60s.
The AWS integration applies this rule strictly, and "timegrain" and period are always perfectly aligned. ↩︎