🕓Initiatives history

How this log is built

This derived log compares consecutive catalogue snapshots. The refresh is scheduled daily at 06:00 UTC; weekly snapshot and manual runs can also refresh it. A scheduled collection is not a guarantee that Azure changed that day, nor a real-time feed. Event dates are detection times, not publication dates.

Added means present in the new scan but absent from the previous catalogue; Removed means the reverse. These observations do not establish Microsoft's exact publication or retirement date.

Modified distinguishes metadata (name, category and definition type), version and member composition. New comparisons record added/removed member references even when the total count is unchanged. Expand an event for the recorded members and before/after metadata.

A member is identified by its policy ID and reference ID. The same policy can appear under multiple references, so member counts are not counts of unique policies. Changing the policy behind a reference, or renaming the reference, is recorded as a removal and an addition. Reordering members is ignored.

Names are captured from the policy catalogues available during comparison: the previous catalogue for removals and the new one for additions. If a name was unavailable, the exact ID remains accessible instead of an invented label. Catalogue links show the current definitions; removed definitions may no longer exist there.

Older events may contain only a count change. A change from 20 to 29 is net +9 members, not proof that exactly nine were added: additions and removals could have happened together. Those missing identities are not reconstructed from today's catalogue. Missing or inconsistent member snapshots are explicitly marked unavailable.

The comparator does not detect parameter-value changes, group assignments, descriptions or rule-body edits unless tracked metadata or member identities also change. A version or composition change alone does not establish its impact on your Azure assignments.

Recording starts with the collector, without backfilling earlier Azure history. The first scan establishes a baseline. The retention limit is 180 days at each refresh; a shared limit of 3,000 policy and initiative events can shorten that window. No retained event is not evidence of no historical change, and untracked rule-only changes may not appear.

Counts and the displayed detection-date range describe the active filters across all matching events, not only the displayed batch. The total retained count covers initiative events only. Recent-period filters use UTC calendar days ending today; all retained events remain available regardless of the age of the last refresh.

Export includes every matching event with its recorded fields, active filters and source timestamp, not just the visible batch. It does not reconstruct missing values. Inspect the source log (policies and initiatives).