Microsoft Security | Microsoft Graph
An API that connects multiple Microsoft services, enabling data access and automation across platforms
Is any deprecation planned for reading PidLidAppointmentSequence and PidLidOwnerCriticalChange via Graph extended properties?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 63%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKS%3C/text%3E%3C/svg%3E)
Kommalapati Shashank Chowdary
0
Reputation points
My service reads two Exchange properties from Outlook calendar events through Microsoft Graph singleValueExtendedProperties:
- PidLidAppointmentSequence: Integer {00062002-0000-0000-C000-000000000046} Id 0x8201
- PidLidOwnerCriticalChange: SystemTime {6ED8DA90-450B-101B-98DA-00AA003F1305} Id 0x001A
I use them to get the organizer's iCalendar SEQUENCE and DTSTAMP for ordering meeting updates. Has Microsoft announced any deprecation or planned change that would affect reading these properties through Graph extended properties, either in v1.0 or through rich change notifications?
Microsoft Security | Microsoft Graph
Sign in to answer