Context
Log events from Azure usually respect the spec, and the time field comes as an ISO8601 string.
Unfortunately, some services sometimes use a different format. For example, the time value is sometimes 11/14/2025 1:48:53 AM instead of 2025-11-14T01:48:53.000Z, and the pipeline fails.
We recently updated the signin logs integration with #15976, but should review all Azure integrations to double-check all integrations have a fallback list of date formats.
Goal
- Review all existing integrations looking for date formats in use.
- Update the integrations with a list of existing formats, ordered from most to least frequently used.
Impact
Users may experience pipeline failures when an Azure service ships log events with off-spec values.
Context
Log events from Azure usually respect the spec, and the
timefield comes as an ISO8601 string.Unfortunately, some services sometimes use a different format. For example, the
timevalue is sometimes11/14/2025 1:48:53 AMinstead of2025-11-14T01:48:53.000Z, and the pipeline fails.We recently updated the signin logs integration with #15976, but should review all Azure integrations to double-check all integrations have a fallback list of date formats.
Goal
Impact
Users may experience pipeline failures when an Azure service ships log events with off-spec values.