# Separate delivery IDs from maintenance event IDs in the Scheduled Events preview

> Which identifier should suppress duplicate Event Grid delivery without losing a maintenance event's later state?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-079-separate-delivery-ids-from-maintenance-event-ids-in-the-scheduled-events-preview/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:30:37+00:00
- Modified: 2026-09-10T00:35:08+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

Which identifier should suppress duplicate Event Grid delivery without losing a maintenance event's later state?

## Potentially affected

Teams evaluating preview Scheduled Events delivery through Azure Event Grid in a nonproduction environment.

## DSE recommendation

Use the Event Grid delivery ID for duplicate detection and retain the Scheduled EventId for lifecycle correlation.

## Article

## Source facts

Scheduled Events delivery through Event Grid is a preview that Microsoft does not recommend for production workloads. Its wrapper ID differs from the scheduled event’s EventId, which stays constant as EventStatus changes. Rare duplicate deliveries carry the same wrapper ID and identical payload. Approving a scheduled event permits it to proceed for every VM listed in its Resources array. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/scheduled-events-event-grid).

## Applicability

Evaluate this design only in a preview-approved test environment with event delivery explicitly enabled. Identify the subscribing service, its duplicate-handling storage, and any separate authority to acknowledge maintenance. Keep message receipt distinct from a decision that the listed workloads are ready.

## DSE recommendation

Use the Event Grid delivery ID for duplicate detection and retain the Scheduled EventId for lifecycle correlation. Design processing so a repeated delivery does not repeat a disruptive action, while a legitimate later state remains visible. Before implementing acknowledgement, require the controller to resolve and prepare every resource named in the event rather than only the first VM encountered.

## Verification

Replay a captured nonsensitive test payload with the same delivery ID and confirm that it is handled as a duplicate. Then exercise later event states and confirm that the lifecycle record is updated rather than discarded. Inspect the entire Resources array in the approval path. Retain the tested identifiers and observed behavior, and do not equate a working preview consumer with approval to operate it in production.

## Official references

[Microsoft Learn: Scheduled Events in Event Grid](https://learn.microsoft.com/en-us/azure/virtual-machines/scheduled-events-event-grid). Source reviewed September 9, 2026.

## Primary reference

- Name: Scheduled Events - Event Grid - Azure Virtual Machines | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/virtual-machines/scheduled-events-event-grid
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Separate delivery IDs from maintenance event IDs in the Scheduled Events preview,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-079-separate-delivery-ids-from-maintenance-event-ids-in-the-scheduled-events-preview/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.