Do not read zero property changes as no Azure resource event

Source facts

Resource Graph change records can report zero in changesCount for both creation and deletion. Microsoft explains that creation would otherwise generate excessive property noise, while deletion leaves no remaining resource properties. Deleted-resource snapshots are not currently supported.

Newly introduced properties are not necessarily shown as changes either; the source gives new API-version properties and newly added empty tag keys as examples. Microsoft Learn.

Applicability

Review queries, dashboards, and exports that use resourcechanges or related change tables. Identify any filter that discards a record merely because it lacks a positive property-change count, and document what events the consumer is intended to retain.

DSE recommendation

DSE recommends treating event type, target resource identifier, time, and property details as separate fields. Make creation and deletion visible through their event type even when there is no property diff. State the snapshot and property-coverage limits in the consumer’s documentation so an operator does not mistake this feed for a complete recovery image.

Verification

In a disposable scope, create, update, and delete an approved test resource. Compare the resulting records with the known operations and check that zero-count events survive the consumer’s filters. Verify the report distinguishes absent property detail from an absent event, and retain the query and observed payloads as the test fixture.

Official references

Microsoft Learn: Get resource changes. Source retrieved September 9, 2026.