I have an odd use case for Power Automate, and I'm not sure if it can be done. I work with a team of people that spans US Pacific, Mountain, Central, and Eastern time zones. We work in a SharePoint list with many different date/time columns that represent due dates for specific projects. To make it even more confusing, the due date/times are often specific to the customer, who may also be in any time zone across the world.
This can be confusing enough, but the dates (and times) themselves need to be copied into other lists, emailed, etc. as dynamic fields in Power Automate. I've found that if I have a normal list field that says, say, 4/1/2025 5 pm (I am Pacific time zone), it will show up as 6 pm for Mountain users, 7 pm for Central, etc. However, if I have a power automate flow that updates another list with that date, it shows up as 4/1/2025 5 pm for everyone regardless of the viewer's actual time zone. If I have to copy that field into an email, that becomes an issue as well.
So far, we've just used date-only fields, with a simple text field for time/time-zone. This has also caused problems, though, because even the date field will be skewed if you don't account for UTC and calculate the date to shave off a few hours.
My brain is tired from thinking about it! Any brilliant ideas out there?