Announcements
The issue is that Power Automate uses Windows time zone IDs, and “Eastern Time” is not valid.
The correct ID is Eastern Standard Time, and it automatically adjusts for daylight saving time.
If you’re still seeing a 4-hour offset, it means your source time is in UTC and you’re not converting it properly.
convertTimeZone()
utcNow()
UTC
Eastern Standard Time
If you’re updating a Microsoft List column, use this expression in the Update item action for the date field.
Power Automate only accepts Windows time zone names. Full list: Windows Default Time Zones.
Run the flow and check the output of the Convert time zone action or Compose step. It should now show the correct local time with DST applied.
Source: Convert a time zone in Power Automate
Best regards, Valantis
✅ If this helped solve your issue, please Accept as Solution so others can find it quickly. ❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :). 🏷️ For follow-ups @Valantis. 📝 https://valantisond365.com/
formatDateTime( convertTimeZone(utcNow(), 'UTC', 'Eastern Standard Time'), 'yyyy-MM-ddTHH:mm:ss' )
convertTimeZone(utcNow(), 'UTC', 'Eastern Standard Time')
📩 Need more help? Just mention @Kalathiya and I’ll be happy to assist.
✔️ If this answer helped you, please tick “Does this answer your question?” so it can be marked as the Verified Answer.
💛 A Like always motivates me to keep contributing!
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Haque 333
David_MA 245 Super User 2026 Season 1
Expiscornovus 202 Most Valuable Professional