Power Automate convertTimeZone using an expression: Decoding the Mystery of Time Zone Names
Ever wrestled with time zone conversions in your Power Automate flows? You're not alone! Today, we're diving deep into the time zone parameters of the convertTimeZone expression , shedding light on a few nuances that might just save you some headaches. Like many of you, I recently stumbled upon a fascinating detail, courtesy of my insightful colleague Daniel Kerridge . Did you know that Australia has two seemingly similar time zone names: "E. Australia Standard Time" and "AUS Eastern Standard Time"? The difference? The former refers to Queensland, which happily skips daylight saving time, while the latter applies to other eastern states that do observe it. Mind. Blown. This revelation highlights a common challenge when working with the convertTimeZone function in Power Automate: figuring out the correct time zone names to populate the sourceTimeZone and destinationTimeZone parameters. The official Power Automate documentation often points to the Azure Logic...
