Unanswered

Issue with SharePoint Action Not Accepting ISO 8601 Date/Time Strings with Timezone Offset

(0) Share

Report

Posted on by Stand-wise

When trying to create a new item in a SharePoint list that contains a Date/Time column, the SharePoint action in Power Automate does not accept a date/time string in ISO 8601 format with a timezone offset — for example:

2025-03-24T21:48:00+08:00

This is unexpected, given that the underlying SharePoint Graph API does accept this format. Additionally, ISO 8601 with timezone offset is specified in the OpenAPI specification, which these connectors are based on.

I would consider this a bug — the connector’s behavior is inconsistent with both the API and the OpenAPI standard. Ideally, the connector should pass this value through as-is or handle it properly.

Here is a screen shot of the connector showing a validation error for what should be a valid input.

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Ellis Karim 11,681 Super User 2025 Season 2 on at

Like (0)

Report

Hi @Stand-wise

SharePoint stores all date time values as UTC.

I would suggest converting your date-time to UTC, in ISO 8601 format, using the following format for SharePoint: YYYY-MM-DDThh:mm:ssZ - the Z is UTC time zone indicator.

In the example below, entering 2024-12-20T22:50 for the EndDate, SharePoint will store this as 2024-12-20T22:50:00Z - with the Z indicating that the time zone is UTC.

See: Why Are My SharePoint Dates Wrong? Fix Them in Power Automate and Power Apps – Ellis Karim's Blog

Ellis Karim
Blog | LinkedIn | Bluesky

Was this reply helpful? Yes No
Chriddle 8,436 Super User 2025 Season 2 on at

Like (1)

Report
Use parseDateTime()

parseDateTime(outputs('Compose'))

Was this reply helpful? Yes No